Port conflict error #1
Comments
|
Hi Devi, You won't actually be able to RDP is I don't have I didn't set the packer image for Remote Desktop, and the currently setup that that is using is based off of server core so there is no GUI. As for your port forwarding issue I would recommend taking a look at my demonstration repo here - |
|
Hi Joe,
Thank you so much for your quick response.
I was able to fix the port conflict issue and run Octopus.Server run successfully.
Please find the screenshot below,
[cid:[email protected]]
However when I try to access the portal using http://192.168.56.100:80/octopus
I get the http 404 error.
192.168.56.100 is my octopus deploy server ip address.
Can you please help me with it?
Thanks,
Nagadevi
From: Joe Beaudry [mailto:[email protected]]
Sent: Wednesday, January 24, 2018 8:35 PM
To: beaudryj/octo-box <[email protected]>
Cc: Nagadevi Machi (BAS) <[email protected]>; Author <[email protected]>
Subject: Re: [beaudryj/octo-box] Port conflict error (#1)
** This mail has been sent from an external source. Treat hyperlinks and attachments in this email with caution**
Hi Devi,
You won't actually be able to RDP is I don't have I didn't set the packer image for Remote Desktop, and the currently setup that that is using is based off of server core so there is no GUI.
As for your port forwarding issue I would recommend taking a look at my demonstration repo here -
https://github.com/beaudryj/BosPSUGOctoDemo<https://clicktime.symantec.com/a/1/sT1wnqsJB7fBGeEcGaENCK_SLZ3-7spdoiuP0fJvsWk=?d=FbjwS5qSke1DWBasFlf9TpG_RMln7eJdGMUJJfCS6EbZMpP6KlPBrAj55OV8PT23otiM-hrS3eOIPtY98JuBvn3Wb5ML4fMRwsLx-uy1xVv-leAh0YrF2zKaRNQ4J7qWcMbzos05ilpC5bUY4FaTmMcDNbR2zvhdcTnyWZHq74pAjopnINRXiYwbYudFPxT0eyxlaMEws3WYVZ2MLtUhhz5K4agNFpg2CshMmKrqeYDN0w72XMLpsfdDJyy43U__uIcX-cLNlkP-zijKRiKsTPN6cZcD54G8anwaHrT-8ROeyZOIqanOrWO84ZzF3ME2DrL7VZxYcD-DG19Ph9IWh5YCCFfHelwcFx0nSkzApBmA4fPdfUM3h2Qm6GF1oi98Uqfsx3RjsW-7yBj95foOUH1CBjREi8ga0J3-Gm2JrNRDHvUSRCPkEUK6I-EtAxiGzUpkuiSPo49b&u=https%3A%2F%2Fgithub.com%2Fbeaudryj%2FBosPSUGOctoDemo>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://clicktime.symantec.com/a/1/7AM95uJOASOK7lbV087MM8zuDPTm04cM57KuNYVLZmU=?d=FbjwS5qSke1DWBasFlf9TpG_RMln7eJdGMUJJfCS6EbZMpP6KlPBrAj55OV8PT23otiM-hrS3eOIPtY98JuBvn3Wb5ML4fMRwsLx-uy1xVv-leAh0YrF2zKaRNQ4J7qWcMbzos05ilpC5bUY4FaTmMcDNbR2zvhdcTnyWZHq74pAjopnINRXiYwbYudFPxT0eyxlaMEws3WYVZ2MLtUhhz5K4agNFpg2CshMmKrqeYDN0w72XMLpsfdDJyy43U__uIcX-cLNlkP-zijKRiKsTPN6cZcD54G8anwaHrT-8ROeyZOIqanOrWO84ZzF3ME2DrL7VZxYcD-DG19Ph9IWh5YCCFfHelwcFx0nSkzApBmA4fPdfUM3h2Qm6GF1oi98Uqfsx3RjsW-7yBj95foOUH1CBjREi8ga0J3-Gm2JrNRDHvUSRCPkEUK6I-EtAxiGzUpkuiSPo49b&u=https%3A%2F%2Fgithub.com%2Fbeaudryj%2Focto-box%2Fissues%2F1%23issuecomment-360163430>, or mute the thread<https://clicktime.symantec.com/a/1/vEl2MW0NedVeXllHtvbH6jEAWopL2SZlu9WDhLxTWSY=?d=FbjwS5qSke1DWBasFlf9TpG_RMln7eJdGMUJJfCS6EbZMpP6KlPBrAj55OV8PT23otiM-hrS3eOIPtY98JuBvn3Wb5ML4fMRwsLx-uy1xVv-leAh0YrF2zKaRNQ4J7qWcMbzos05ilpC5bUY4FaTmMcDNbR2zvhdcTnyWZHq74pAjopnINRXiYwbYudFPxT0eyxlaMEws3WYVZ2MLtUhhz5K4agNFpg2CshMmKrqeYDN0w72XMLpsfdDJyy43U__uIcX-cLNlkP-zijKRiKsTPN6cZcD54G8anwaHrT-8ROeyZOIqanOrWO84ZzF3ME2DrL7VZxYcD-DG19Ph9IWh5YCCFfHelwcFx0nSkzApBmA4fPdfUM3h2Qm6GF1oi98Uqfsx3RjsW-7yBj95foOUH1CBjREi8ga0J3-Gm2JrNRDHvUSRCPkEUK6I-EtAxiGzUpkuiSPo49b&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWkI9ifzY94uLi_UPkqAtd1BShRsRoFvks5tN0aOgaJpZM4RrPXB>.
…______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
|
|
Can you please host your image on imgur as I can't see yours and can you please post a copy of your vagrant file? |
|
Hi Joe,
Please find my vagrant file below,
Please check and let me know if it needs any change to make it work.
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "jbeaudry/Octobox"
config.vm.box_version = "2.1.0"
config.vm.box_url="https://atlas.hashicorp.com/jbeaudry/boxes/Octobox2012"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
#config.vm.network "private_network", ip: "192.168.56.100"
#config.vm.network :forwarded_port, guest: 3389, host: 3389, id: 'rdp', auto_correct: true
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
vb.gui = true
#
# # Customize the amount of memory on the VM:
vb.memory = "1024"
end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# apt-get update
# apt-get install -y apache2
# SHELL
end
Thanks,
Nagadevi
From: Joe Beaudry [mailto:[email protected]]
Sent: Thursday, January 25, 2018 12:14 AM
To: beaudryj/octo-box <[email protected]>
Cc: Nagadevi Machi (BAS) <[email protected]>; Author <[email protected]>
Subject: Re: [beaudryj/octo-box] Port conflict error (#1)
** This mail has been sent from an external source. Treat hyperlinks and attachments in this email with caution**
Can you please host your image on imgur as I can't see yours and can you please post a copy of your vagrant file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://clicktime.symantec.com/a/1/-A7EIsOttNrkFpDk2BqAk_VkUoDFLzjPGp66yDvh0ik=?d=ztPY2fkPackAzYgxLSEuQXkKFZIgE_RTbPVYtaaKm4_xNhTjlqi8UYOkUhHrDYbRwIhDBtTAlHLHssc1RPHlkXcU48a4CcX151sc-vYCfCoy6M6160LhtywGzMlz0T9koFZM6fCToLlbrJDGcrwz0fF2eFA0yGWBsCqF1MAljqC8DMRjiLvLrrmtOV_E2_-TSY0_XfbfxW02ATv-bnKHp6KyrndcSW_nwm3SeMcQxG2Z_L1phIesdblK-ssr_fJdPj3dVO5oVctgdoqO7Ox9hP6Re0FB08_QzgSr9mmb8vZ4WQn2hSTnt65WU6VJAm1X9nT40JnFcdpFnMgwXuzgt9n5bgpVkPwplM8bZqlUEfqqG_wK319D5xAyUaBYzkMS05gg3qnTqjy1rdSiZ_xyt2kChVFcGmaeuPbqsHruv_ClEbhCiQItSa_e8xQ_2_MgK86UJGZf&u=https%3A%2F%2Fgithub.com%2Fbeaudryj%2Focto-box%2Fissues%2F1%23issuecomment-360233250>, or mute the thread<https://clicktime.symantec.com/a/1/egdXXeRnUYl-EX309OPGxp2k6qThy1-Ce-JgkaG3zlo=?d=ztPY2fkPackAzYgxLSEuQXkKFZIgE_RTbPVYtaaKm4_xNhTjlqi8UYOkUhHrDYbRwIhDBtTAlHLHssc1RPHlkXcU48a4CcX151sc-vYCfCoy6M6160LhtywGzMlz0T9koFZM6fCToLlbrJDGcrwz0fF2eFA0yGWBsCqF1MAljqC8DMRjiLvLrrmtOV_E2_-TSY0_XfbfxW02ATv-bnKHp6KyrndcSW_nwm3SeMcQxG2Z_L1phIesdblK-ssr_fJdPj3dVO5oVctgdoqO7Ox9hP6Re0FB08_QzgSr9mmb8vZ4WQn2hSTnt65WU6VJAm1X9nT40JnFcdpFnMgwXuzgt9n5bgpVkPwplM8bZqlUEfqqG_wK319D5xAyUaBYzkMS05gg3qnTqjy1rdSiZ_xyt2kChVFcGmaeuPbqsHruv_ClEbhCiQItSa_e8xQ_2_MgK86UJGZf&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWkI9tS5ktd-s_Y9U2k2VSX3ZPaMwu_iks5tN3nwgaJpZM4RrPXB>.
…______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
|
|
Hi Joe,
Please ignore my previous mail.
I’m able to access the portal successfully now.
Thanks,
Nagadevi
From: Nagadevi Machi (BAS)
Sent: Thursday, January 25, 2018 5:26 PM
To: 'beaudryj/octo-box' <[email protected]>; beaudryj/octo-box <[email protected]>
Cc: Author <[email protected]>
Subject: RE: [beaudryj/octo-box] Port conflict error (#1)
Hi Joe,
Please find my vagrant file below,
Please check and let me know if it needs any change to make it work.
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "jbeaudry/Octobox"
config.vm.box_version = "2.1.0"
config.vm.box_url="https://atlas.hashicorp.com/jbeaudry/boxes/Octobox2012"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
#config.vm.network "private_network", ip: "192.168.56.100"
#config.vm.network :forwarded_port, guest: 3389, host: 3389, id: 'rdp', auto_correct: true
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
vb.gui = true
#
# # Customize the amount of memory on the VM:
vb.memory = "1024"
end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# apt-get update
# apt-get install -y apache2
# SHELL
end
Thanks,
Nagadevi
From: Joe Beaudry [mailto:[email protected]]
Sent: Thursday, January 25, 2018 12:14 AM
To: beaudryj/octo-box <[email protected]<mailto:[email protected]>>
Cc: Nagadevi Machi (BAS) <[email protected]<mailto:[email protected]>>; Author <[email protected]<mailto:[email protected]>>
Subject: Re: [beaudryj/octo-box] Port conflict error (#1)
** This mail has been sent from an external source. Treat hyperlinks and attachments in this email with caution**
Can you please host your image on imgur as I can't see yours and can you please post a copy of your vagrant file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://clicktime.symantec.com/a/1/-A7EIsOttNrkFpDk2BqAk_VkUoDFLzjPGp66yDvh0ik=?d=ztPY2fkPackAzYgxLSEuQXkKFZIgE_RTbPVYtaaKm4_xNhTjlqi8UYOkUhHrDYbRwIhDBtTAlHLHssc1RPHlkXcU48a4CcX151sc-vYCfCoy6M6160LhtywGzMlz0T9koFZM6fCToLlbrJDGcrwz0fF2eFA0yGWBsCqF1MAljqC8DMRjiLvLrrmtOV_E2_-TSY0_XfbfxW02ATv-bnKHp6KyrndcSW_nwm3SeMcQxG2Z_L1phIesdblK-ssr_fJdPj3dVO5oVctgdoqO7Ox9hP6Re0FB08_QzgSr9mmb8vZ4WQn2hSTnt65WU6VJAm1X9nT40JnFcdpFnMgwXuzgt9n5bgpVkPwplM8bZqlUEfqqG_wK319D5xAyUaBYzkMS05gg3qnTqjy1rdSiZ_xyt2kChVFcGmaeuPbqsHruv_ClEbhCiQItSa_e8xQ_2_MgK86UJGZf&u=https%3A%2F%2Fgithub.com%2Fbeaudryj%2Focto-box%2Fissues%2F1%23issuecomment-360233250>, or mute the thread<https://clicktime.symantec.com/a/1/egdXXeRnUYl-EX309OPGxp2k6qThy1-Ce-JgkaG3zlo=?d=ztPY2fkPackAzYgxLSEuQXkKFZIgE_RTbPVYtaaKm4_xNhTjlqi8UYOkUhHrDYbRwIhDBtTAlHLHssc1RPHlkXcU48a4CcX151sc-vYCfCoy6M6160LhtywGzMlz0T9koFZM6fCToLlbrJDGcrwz0fF2eFA0yGWBsCqF1MAljqC8DMRjiLvLrrmtOV_E2_-TSY0_XfbfxW02ATv-bnKHp6KyrndcSW_nwm3SeMcQxG2Z_L1phIesdblK-ssr_fJdPj3dVO5oVctgdoqO7Ox9hP6Re0FB08_QzgSr9mmb8vZ4WQn2hSTnt65WU6VJAm1X9nT40JnFcdpFnMgwXuzgt9n5bgpVkPwplM8bZqlUEfqqG_wK319D5xAyUaBYzkMS05gg3qnTqjy1rdSiZ_xyt2kChVFcGmaeuPbqsHruv_ClEbhCiQItSa_e8xQ_2_MgK86UJGZf&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWkI9tS5ktd-s_Y9U2k2VSX3ZPaMwu_iks5tN3nwgaJpZM4RrPXB>.
…______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I downloaded the octobox https://app.vagrantup.com/jbeaudry/boxes/Octobox
and the instance is up and running.
but octopus run fails with port conflict error.
Can anyone help with how to allow forwarding on port 80?
Also I'm not able to run windows in GUI mode , Remote desktop connection is also failing
The text was updated successfully, but these errors were encountered: