Hi, Thanks for your reply.
You're right i've forgotten my OS, i'm using Ubuntu 14.04. At home, no vpn nor proxy. At work, i'm not sure, but i don't think that we are using a proxy. But perhaps because i know that with have an internet box, which transfert connection to 3 routers. The hell is that i can ping, make apt-get from vagrant when i'm log in ^^ So Internet surely works =) My local seems to not understand what to reach when i up vagrant and ask to get localhost:4567 :/ Thanks a lot Nico Le jeudi 14 mai 2015 10:22:02 UTC+2, Nico a écrit : > > Hello all, > > I have a problem since yesterday that i'm not able to fix. > > I have installed Vagrant when i was at work. Everything was working > correctly for about a week. > > I have brought my computer at home (work is hard ^^), but even if i'm able > to up vagraht and to ssh it, i can't reach it through my local. > > When i try to get http://localhost:4567, it doesn't work, but when i'm at > work, there is no problem. > > It seems that vagrant has probably stuck to my work network and doesn't > allow a connection on another network. > > Anyway, when i try to get only localhost, i have the Apache2 Ubuntu > Default Page... > > Also, when i try to curl the localhost page (on port 4567) from my local, > i have an empty reply from server (error 52), and the same when i'm > connected to Vagrant. > > Well, everything else work, because i can make a "vagrant ssh", ifconfig > shows me that vagrant is well connected on network, i can also connect > vagrant through an ssh connection as root (ssh root@...). > > This is the content of my VagrantFile : > > > # -*- mode: ruby -*- >> # vi: set ft=ruby : >> >> # Vagrantfile API/syntax version. Don't touch unless you know what you're >> doing! >> VAGRANTFILE_API_VERSION = "2" >> >> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| >> # All Vagrant configuration is done here. The most common configuration >> # options are documented and commented below. For a complete reference, >> # please see the online documentation at vagrantup.com. >> >> # Every Vagrant virtual environment requires a box to build off of. >> config.vm.box = "lucid64" >> >> # The url from where the 'config.vm.box' box will be fetched if it >> # doesn't already exist on the user's system. >> # config.vm.box_url = "http://domain.com/path/to/above.box"; >> >> # 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 >> config.vm.network:forwarded_port, host:4567, guest:80 >> # 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 >> >> # If true, then any SSH connections made will enable agent forwarding. >> # Default value: false >> # config.ssh.forward_agent = true >> >> # 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 ".", "/vagrant", :group => "www-data", >> :mount_options => ['dmode=777','fmode=777'] >> >> # 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| >> # # Don't boot with headless mode >> # vb.gui = true >> # >> # # Use VBoxManage to customize the VM. For example to change memory: >> # vb.customize ["modifyvm", :id, "--memory", "1024"] >> # end >> # >> # View the documentation for the provider you're using for more >> # information on available options. >> >> # Enable provisioning with Puppet stand alone. Puppet manifests >> # are contained in a directory path relative to this Vagrantfile. >> # You will need to create the manifests directory and a manifest in >> # the file lucid64.pp in the manifests_path directory. >> # >> # An example Puppet manifest to provision the message of the day: >> # >> # # group { "puppet": >> # # ensure => "present", >> # # } >> # # >> # # File { owner => 0, group => 0, mode => 0644 } >> # # >> # # file { '/etc/motd': >> # # content => "Welcome to your Vagrant-built virtual machine! >> # # Managed by Puppet.\n" >> # # } >> # >> # config.vm.provision :puppet do |puppet| >> # puppet.manifests_path = "manifests" >> # puppet.manifest_file = "site.pp" >> # end >> >> # Enable provisioning with chef solo, specifying a cookbooks path, roles >> # path, and data_bags path (all relative to this Vagrantfile), and >> adding >> # some recipes and/or roles. >> # >> # config.vm.provision :chef_solo do |chef| >> # chef.cookbooks_path = "../my-recipes/cookbooks" >> # chef.roles_path = "../my-recipes/roles" >> # chef.data_bags_path = "../my-recipes/data_bags" >> # chef.add_recipe "mysql" >> # chef.add_role "web" >> # >> # # You may also specify custom JSON attributes: >> # chef.json = { :mysql_password => "foo" } >> # end >> >> # Enable provisioning with chef server, specifying the chef server URL, >> # and the path to the validation key (relative to this Vagrantfile). >> # >> # The Opscode Platform uses HTTPS. Substitute your organization for >> # ORGNAME in the URL and validation key. >> # >> # If you have your own Chef Server, use the appropriate URL, which may >> be >> # HTTP instead of HTTPS depending on your configuration. Also change the >> # validation key to validation.pem. >> # >> # config.vm.provision :chef_client do |chef| >> # chef.chef_server_url = " >> https://api.opscode.com/organizations/ORGNAME"; >> # chef.validation_key_path = "ORGNAME-validator.pem" >> # end >> # >> # If you're using the Opscode platform, your validator client is >> # ORGNAME-validator, replacing ORGNAME with your organization name. >> # >> # If you have your own Chef Server, the default validation client name >> is >> # chef-validator, unless you changed the configuration. >> # >> # chef.validation_client_name = "ORGNAME-validator" > > end >> > > I really hope that you will be able to help me, because i really don't > know what to do :) > > Thank you all for reading. > > Regards > > Nico > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
