hashicorp / vagrant

Vagrant is a tool for building and distributing development environments.
https://www.vagrantup.com
Other
26.28k stars 4.43k forks source link

Vagrant networking CentOS6.5 #7807

Closed Nebojsaa closed 8 years ago

Nebojsaa commented 8 years ago

I am using Vagrant 1.9.5 with as my guest system CentOS6.5, as my host system Windows 7.

I tried this vagrant networking configurations: config.vm.network "forwarded_port", guest: 80, host: 8080 - unable to connect. config.vm.network :public_network - then I went to the Vagrant machine and see using ifconfig and see my public network IP and I still get a connection timeout, but I tried to ping 172.23.34.119 - which is the number of my guest machine and it works.

I also uninstalled antivirus program, because I thought that it is affecting my firewall, but it isn't that. I need to get connected to my nginx.conf - which is BTW started and running.

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 = "richdynamix/magestead-centos65-nginx-php56"

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.33.10"

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 "/server/www/cemcloud", "/srv/www/cemcloud"

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 "file", source: "/server/bin/nginx/conf/domains-enabled/cemcloud.conf1", destination: "~/cemcloud.conf" config.vm.provision "file", source: "/server/bin/nginx/conf/nginxLinux.conf", destination: "~/nginx.conf" config.vm.provision "file", source: "/server/certs/cacert.pem", destination: "~/cacert.pem" config.vm.provision "file", source: "/server/certs/privkey.pem", destination: "~/privkey.pem" config.vm.provision "shell", path: "script.sh"

apt-get update

apt-get install -y apache2

SHELL

end

Nebojsaa commented 8 years ago

This isn't either Vagrant nor CentOS issue. This is Nginx failure. I am closing this issue.

ghost commented 4 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.