New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vagrant up fail in 1.9.3 on windows10 #8395

Closed
leoMeee opened this Issue Mar 22, 2017 · 30 comments

Comments

Projects
None yet
@leoMeee

leoMeee commented Mar 22, 2017

Vagrant version

1.9.3

Host operating system

windows10

Guest operating system

custom box base on ubuntu/trusty64

Vagrantfile

# -*- 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 = "wyzccloud/gxy"

  # 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 "../data", "/vagrant_data"
  config.vm.synced_folder "../", "/vagrant", owner: "www-data",group:"www-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

Debug output

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'wyzccloud/gxy'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'wyzccloud/gxy' is up to date...
==> default: Setting the name of the VM: common_default_1490158319530_15235
==> default: Destroying VM and associated drives...
F:/tool/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in initialize': The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 8080 (Errno::EADDRNOTAVAIL) from F:/tool/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:innew'
from F:/tool/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `block in is_port_open?'
..... more

Expected behavior

vagrant up successfully

Actual behavior

vagrant up fail

Steps to reproduce

vagrant up (first up)

@blasco991

This comment has been minimized.

Show comment
Hide comment
@blasco991

blasco991 Mar 22, 2017

Same problem here:
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in initialize': Indirizzo richiesto non valido nel proprio contesto. - connect(2) for "0.0.0.0" port 8000 (Errno::EADDRNOTAVAIL) from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in new' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in block in is_port_open?' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in block in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in block in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in timeout ...'

Same problem here:
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in initialize': Indirizzo richiesto non valido nel proprio contesto. - connect(2) for "0.0.0.0" port 8000 (Errno::EADDRNOTAVAIL) from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in new' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in block in is_port_open?' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in block in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in block in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in timeout ...'

@MetalArend

This comment has been minimized.

Show comment
Hide comment
@MetalArend

MetalArend Mar 22, 2017

My colleague has the same problem on Windows 8 with port 9000

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_o
pen.rb:21:in `initialize': The requested address is not valid in its context. -
connect(2) for "0.0.0.0" port 9000 (Errno::EADDRNOTAVAIL)

MetalArend commented Mar 22, 2017

My colleague has the same problem on Windows 8 with port 9000

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_o
pen.rb:21:in `initialize': The requested address is not valid in its context. -
connect(2) for "0.0.0.0" port 9000 (Errno::EADDRNOTAVAIL)

@Ericbla

This comment has been minimized.

Show comment
Hide comment
@Ericbla

Ericbla Mar 22, 2017

Had the same problem on Windows 7.
This problem seems to be caused by the new host_ip parameter for the port forwarding feature.
I suggest that for compatibility reason, the default host_ip parameter should be set to 127.0.0.1 instead of 0.0.0.0
I managed to make the 1.9.3 version working by rewritten all my Vagrantfile(s) and adding the host_id: "127.0.0.1" parameter for each of the "forwarded_port" network configuration.
E.g.:
config.vm.network "forwarded_port", guest: 22, host: 1022, host_ip: "127.0.0.1", id: 'ssh'

Ericbla commented Mar 22, 2017

Had the same problem on Windows 7.
This problem seems to be caused by the new host_ip parameter for the port forwarding feature.
I suggest that for compatibility reason, the default host_ip parameter should be set to 127.0.0.1 instead of 0.0.0.0
I managed to make the 1.9.3 version working by rewritten all my Vagrantfile(s) and adding the host_id: "127.0.0.1" parameter for each of the "forwarded_port" network configuration.
E.g.:
config.vm.network "forwarded_port", guest: 22, host: 1022, host_ip: "127.0.0.1", id: 'ssh'

@blasco991

This comment has been minimized.

Show comment
Hide comment
@blasco991

blasco991 Mar 22, 2017

@Ericbla thanks, it was driving me crazy
For anyone using Homestead the line to change is 90 at Homestead\scripts\homestead.rb

@Ericbla thanks, it was driving me crazy
For anyone using Homestead the line to change is 90 at Homestead\scripts\homestead.rb

@l00tr

This comment has been minimized.

Show comment
Hide comment
@l00tr

l00tr Mar 22, 2017

@Ericbla Thanks, had the same issue which is now solved.

l00tr commented Mar 22, 2017

@Ericbla Thanks, had the same issue which is now solved.

ferventcoder added a commit to chocolatey/chocolatey-test-environment that referenced this issue Mar 23, 2017

Note issues with Vagrant 1.9.3
You may run into `Errno::EADDRNOTAVAIL` when using Vagrant 1.9.3 when attempting to set up 
port forwarding. This is a known issue - hashicorp/vagrant#8395. There
is a workaround available, so document that in the file
@randelsr

This comment has been minimized.

Show comment
Hide comment
@randelsr

randelsr Mar 23, 2017

@blasco991 and @Ericbla thanks for this workaround.
To further elaborate... anybody running Homestead with Vagrant 1.9.3, change line 90 (file Homestead/scripts/homestead.rb) to read:
config.vm.network "forwarded_port", guest: guest, host: host, host_ip: "127.0.0.1", auto_correct: true

@blasco991 and @Ericbla thanks for this workaround.
To further elaborate... anybody running Homestead with Vagrant 1.9.3, change line 90 (file Homestead/scripts/homestead.rb) to read:
config.vm.network "forwarded_port", guest: guest, host: host, host_ip: "127.0.0.1", auto_correct: true

@khalilj

This comment has been minimized.

Show comment
Hide comment
@khalilj

khalilj Mar 25, 2017

Thanks fixed same issue i had.
Any plan to fix it?

khalilj commented Mar 25, 2017

Thanks fixed same issue i had.
Any plan to fix it?

@chrisroberts

This comment has been minimized.

Show comment
Hide comment
@chrisroberts

chrisroberts Mar 26, 2017

Collaborator

@khalilj Yes, fix was applied via #8399 and will be included in the next release.

Collaborator

chrisroberts commented Mar 26, 2017

@khalilj Yes, fix was applied via #8399 and will be included in the next release.

@cichondev

This comment has been minimized.

Show comment
Hide comment
@cichondev

cichondev Mar 27, 2017

@Ericbla thanks, solved my problem.

@Ericbla thanks, solved my problem.

@EstebanJesus

This comment has been minimized.

Show comment
Hide comment
@EstebanJesus

EstebanJesus Mar 27, 2017

Muchas gracias, ya pude desplegar vagrant

Muchas gracias, ya pude desplegar vagrant

@khalilj

This comment has been minimized.

Show comment
Hide comment
@khalilj

khalilj Mar 27, 2017

khalilj commented Mar 27, 2017

@binary1230

This comment has been minimized.

Show comment
Hide comment
@binary1230

binary1230 Mar 27, 2017

just ran into this, this is now a blocking issue for some of our users on 1.9.3. on win10.

thanks for the fix, any word when we can expect 1.9.4 to be released for the fix?

CC @RobRuana @kitsuta

just ran into this, this is now a blocking issue for some of our users on 1.9.3. on win10.

thanks for the fix, any word when we can expect 1.9.4 to be released for the fix?

CC @RobRuana @kitsuta

@sheelstera

This comment has been minimized.

Show comment
Hide comment
@sheelstera

sheelstera Mar 29, 2017

Thanks for this. Saved and made my day

sheelstera commented Mar 29, 2017

Thanks for this. Saved and made my day

@mlt

This comment has been minimized.

Show comment
Hide comment
@mlt

mlt Mar 29, 2017

Uhm... the explicit loopback workaround is nice, but how can I make port forwarding work for all interfaces/addresses? I guess it used to work with default 0.0.0.0. Why doesn't it work anymore?

mlt commented Mar 29, 2017

Uhm... the explicit loopback workaround is nice, but how can I make port forwarding work for all interfaces/addresses? I guess it used to work with default 0.0.0.0. Why doesn't it work anymore?

@Anon348923578

This comment has been minimized.

Show comment
Hide comment
@Anon348923578

Anon348923578 Mar 31, 2017

mlt

I ran into this problem today, and it seems that typing "localhost" instead of "0.0.0.0" for the host_ip will cause Vagrant to listen on all interfaces.

127.0.0.1 => Only listens on 127.0.0.1
0.0.0.0 => Error, does not work
localhost => Listens on all interfaces

This is on Win 7.

Anon348923578 commented Mar 31, 2017

mlt

I ran into this problem today, and it seems that typing "localhost" instead of "0.0.0.0" for the host_ip will cause Vagrant to listen on all interfaces.

127.0.0.1 => Only listens on 127.0.0.1
0.0.0.0 => Error, does not work
localhost => Listens on all interfaces

This is on Win 7.

@dogi

This comment has been minimized.

Show comment
Hide comment
@dogi

dogi Apr 1, 2017

@Anon348923578 are you saying localhost is a better replacement for 0.0.0.0 then 127.0.0.1

dogi commented Apr 1, 2017

@Anon348923578 are you saying localhost is a better replacement for 0.0.0.0 then 127.0.0.1

@amyhre16

This comment has been minimized.

Show comment
Hide comment
@amyhre16

amyhre16 Apr 1, 2017

I'm on Windows 10 using homestead. I changed my homestead/scripts/homestead.rb file to add host_id: "localhost" for both lines that forward the port (lines 90 and 98). I am still getting the same error:

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in 'initialize': The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 8000 (Errno::EADDRNOTAVAIL) from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in 'new' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in 'block in is_port_open?' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in 'block in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'block in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in 'timeout'

Any idea as to what I should do to fix this? @blasco991

amyhre16 commented Apr 1, 2017

I'm on Windows 10 using homestead. I changed my homestead/scripts/homestead.rb file to add host_id: "localhost" for both lines that forward the port (lines 90 and 98). I am still getting the same error:

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in 'initialize': The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 8000 (Errno::EADDRNOTAVAIL) from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in 'new' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in 'block in is_port_open?' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in 'block in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'block in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in 'catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in 'timeout'

Any idea as to what I should do to fix this? @blasco991

@dogi

This comment has been minimized.

Show comment
Hide comment
@dogi

dogi Apr 1, 2017

I'm on Windows 10 using homestead. I changed my homestead/scripts/homestead.rb file to add host_id: "localhost" for both lines that forward the port (lines 90 and 98). I am still getting the same error:

@amyhre16 think meant to say host_ip

dogi commented Apr 1, 2017

I'm on Windows 10 using homestead. I changed my homestead/scripts/homestead.rb file to add host_id: "localhost" for both lines that forward the port (lines 90 and 98). I am still getting the same error:

@amyhre16 think meant to say host_ip

@amyhre16

This comment has been minimized.

Show comment
Hide comment
@amyhre16

amyhre16 Apr 1, 2017

@dogi thanks! I should have figured that out lol

amyhre16 commented Apr 1, 2017

@dogi thanks! I should have figured that out lol

@khromov

This comment has been minimized.

Show comment
Hide comment
@khromov

khromov Apr 3, 2017

Fix not working when using vagrant-vmware-workstation (4.0.18). Anyone got the host_ip trick working with VMWare?

khromov commented Apr 3, 2017

Fix not working when using vagrant-vmware-workstation (4.0.18). Anyone got the host_ip trick working with VMWare?

@Anon348923578

This comment has been minimized.

Show comment
Hide comment
@Anon348923578

Anon348923578 Apr 4, 2017

@dogi
In my case yes it was, because I needed to connect to my VM from a different physical computer than the one on which it was running. If you will only ever connect to your VM locally then "127.0.0.1" would probably be preferred.
IMO the behavior seems backwards, it ought to treat "0.0.0.0" as "any IP" and "localhost" as "127.0.0.1 only".

@dogi
In my case yes it was, because I needed to connect to my VM from a different physical computer than the one on which it was running. If you will only ever connect to your VM locally then "127.0.0.1" would probably be preferred.
IMO the behavior seems backwards, it ought to treat "0.0.0.0" as "any IP" and "localhost" as "127.0.0.1 only".

@dogi

This comment has been minimized.

Show comment
Hide comment
@dogi

dogi Apr 4, 2017

@dogi
In my case yes it was, because I needed to connect to my VM from a different physical computer than the one on which it was running. If you will only ever connect to your VM locally then "127.0.0.1" would probably be preferred.
IMO the behavior seems backwards, it ought to treat "0.0.0.0" as "any IP" and "localhost" as "127.0.0.1 only".

@Anon348923578 it looks like you speak my language here - I also need to be able to connect from remote ;)

dogi commented Apr 4, 2017

@dogi
In my case yes it was, because I needed to connect to my VM from a different physical computer than the one on which it was running. If you will only ever connect to your VM locally then "127.0.0.1" would probably be preferred.
IMO the behavior seems backwards, it ought to treat "0.0.0.0" as "any IP" and "localhost" as "127.0.0.1 only".

@Anon348923578 it looks like you speak my language here - I also need to be able to connect from remote ;)

@theocodes

This comment has been minimized.

Show comment
Hide comment

Thanks @Ericbla

@prophet60091

This comment has been minimized.

Show comment
Hide comment
@prophet60091

prophet60091 Apr 6, 2017

I tried the fix as well, and after it initially hung up the first time I tried vagrant up, it BSOD. Tried again after reboot and got the same thing, but instead of hanging it happened shortly after it began forwarding ports.

Edit: Whoops. my bad still had HyperV running.

prophet60091 commented Apr 6, 2017

I tried the fix as well, and after it initially hung up the first time I tried vagrant up, it BSOD. Tried again after reboot and got the same thing, but instead of hanging it happened shortly after it began forwarding ports.

Edit: Whoops. my bad still had HyperV running.

rcxr added a commit to rcxr/deploy that referenced this issue Apr 7, 2017

Fix: vagrant up fails in Vagrant 1.9.3 for Windows 10
Implemented fix here:
hashicorp/vagrant#8395 (comment)
Fix will eventually get to the next version of Vagrant

lhchavez added a commit to omegaup/deploy that referenced this issue Apr 8, 2017

Fix: vagrant up fails in Vagrant 1.9.3 for Windows 10 (#9)
Implemented fix here:
hashicorp/vagrant#8395 (comment)
Fix will eventually get to the next version of Vagrant

mablae added a commit to mablae/proophessor-do that referenced this issue Apr 9, 2017

Some fixes to the vagrant config file:
- Fix the known bug with forwarded hosts by assigning a host ip: hashicorp/vagrant#8395 (comment)
- Run docker commands without tty to avoid error msgs
@blueoctopuswebdesigns

This comment has been minimized.

Show comment
Hide comment
@blueoctopuswebdesigns

blueoctopuswebdesigns Apr 13, 2017

For anyone using Ericbla's fix and getting error:
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

make sure VitualBox is up to date.

For anyone using Ericbla's fix and getting error:
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

make sure VitualBox is up to date.

paulgeneres added a commit to paulgeneres/homestead that referenced this issue Apr 14, 2017

jalessio added a commit to CalthorpeAnalytics/urbanfootprint that referenced this issue Apr 17, 2017

PoetikDragon added a commit to PoetikDragon/USCSS that referenced this issue Apr 18, 2017

clarencemorse pushed a commit to clarencemorse/vagrant-elk-box that referenced this issue Apr 18, 2017

Clay Morse Clay Morse
forwarded_port fix
Errors out due to new host_ip requirement.

hashicorp/vagrant#8395
@iramsejo

This comment has been minimized.

Show comment
Hide comment
@iramsejo

iramsejo Apr 20, 2017

@blasco991 Gracias , no entendia en que archivo iba a realizar la modificacion,ya estaba que me cambiaba a la version anterior de vagrant pero todo funciono bien :) . Thanks, I did not understand which file I was going to make the modification, I was already changing to the previous version of vagrant but everything worked fine :)

@blasco991 Gracias , no entendia en que archivo iba a realizar la modificacion,ya estaba que me cambiaba a la version anterior de vagrant pero todo funciono bien :) . Thanks, I did not understand which file I was going to make the modification, I was already changing to the previous version of vagrant but everything worked fine :)

DeeDeeG added a commit to DeeDeeG/refugerestrooms that referenced this issue Apr 21, 2017

DeeDeeG added a commit to DeeDeeG/refugerestrooms that referenced this issue Apr 24, 2017

Workaround for 'vagrant up' failure on Windows only
Makes sure port gets forwarded correctly,
to prevent "vagrant up" from erroring out.

see: hashicorp/vagrant#8395 (comment) for details

byzent added a commit to byzent/odoo-vagrant-dev that referenced this issue Apr 25, 2017

Update Vagrantfile for Vagrant 1.9.3
This Vagrantfile will cause errors as described here: hashicorp/vagrant#8395, adding the host_ip parameter will solve this.
@fancellu

This comment has been minimized.

Show comment
Hide comment
@fancellu

fancellu Apr 25, 2017

1.9.4 is out now, works fine.

1.9.4 is out now, works fine.

yoctozepto added a commit to yoctozepto/croit-vagrant-demo that referenced this issue Apr 28, 2017

yoctozepto added a commit to yoctozepto/croit-vagrant-demo that referenced this issue Apr 28, 2017

@eXist73

This comment has been minimized.

Show comment
Hide comment
@eXist73

eXist73 Jun 2, 2017

@Ericbla ty sir, solved my issue.

eXist73 commented Jun 2, 2017

@Ericbla ty sir, solved my issue.

rnkhouse pushed a commit to rnkhouse/ansible-prometheus that referenced this issue Jul 25, 2017

rnkhouse
Update Vagrantfile
There is an issue with the new vagrant 1.9.3 (see hashicorp/vagrant#8395). It can be solved by adding: host_ip: "127.0.0.1"

It will solve below error:
The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 9090 (Errno::EADDRNOTAVAIL)
@gpalazuelosg

This comment has been minimized.

Show comment
Hide comment
@gpalazuelosg

gpalazuelosg Aug 18, 2017

@blasco991 and @Ericbla thanks for this workaround.To further elaborate... anybody running Homestead with Vagrant 1.9.3, change line 90 (file Homestead/scripts/homestead.rb) to read:config.vm.network "forwarded_port", guest: guest, host: host, host_ip: "127.0.0.1", auto_correct: true

Thanks, this helped me on the issue. I'm on win10 Pro, I just installed Vagrant yesterday.
This was my error:
image

@blasco991 and @Ericbla thanks for this workaround.To further elaborate... anybody running Homestead with Vagrant 1.9.3, change line 90 (file Homestead/scripts/homestead.rb) to read:config.vm.network "forwarded_port", guest: guest, host: host, host_ip: "127.0.0.1", auto_correct: true

Thanks, this helped me on the issue. I'm on win10 Pro, I just installed Vagrant yesterday.
This was my error:
image

@aaroncalderon

This comment has been minimized.

Show comment
Hide comment
@aaroncalderon

aaroncalderon Oct 16, 2017

I Just updated to vagrant@1.9.8 and saw this same issue popup.

I replaced my host_ip to localhost. seems to work, just do not know if it will behave as expected.

Any word if this is not an issue on vagrant@2.0?

Thanks

I Just updated to vagrant@1.9.8 and saw this same issue popup.

I replaced my host_ip to localhost. seems to work, just do not know if it will behave as expected.

Any word if this is not an issue on vagrant@2.0?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment