Description
Attempts to download the hashicorp/precise64 box fails on windows 7 running vagrant 1.5.4 with the following error:
C:\Users\xxxx\Documents\GitHub\opg-backoffice-deploy>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise64' could not be found. Attempting to find an
d install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'hashicorp/precise64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on Vagrant Cloud, please verify you're logged in via
vagrant login
. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://vagrantcloud.com/hashicorp/precise64"]
Error: Failed connect to vagrantcloud.com:443; No error
This works fine on on Ubuntu 12.04 and Mac OSX 10.9.2
To reproduce on a windows system, run the following 2 commands in an empty directory:
vagrant init hashicorp/precise64
vagrant up
Thanks
Activity
mitchellh commentedon Apr 30, 2014
I actually work on Windows and don't have this issue. Also, I click that link and it works just fine. Please check your firewall and network settings to make sure you can access the website.
steveo250k commentedon Sep 3, 2014
I'm having the same problem. I can reach the URL via web browser. Vagrant cannot. I am behind a corporate firewall. I'm having trouble finding a solution for setting Vagrant to work with our firewall.
kikitux commentedon Sep 4, 2014
@steveo250k did you try to setup the proxy on the command line ?
steveo250k commentedon Sep 4, 2014
I don't think so, but you gave me some more keywords to search on. I found this:
c:\Applications\Vagrant\precise64>vagrant plugin list
vagrant-login (1.0.1, system)
vagrant-share (1.1.0, system)
and notice there is no vagrant-proxyconf plugin which I assume I need.
So I ran:
c:\Applications\Vagrant\precise64>vagrant plugin install vagrant-proxyconf
Installing the 'vagrant-proxyconf' plugin. This can take a few minutes...
C:/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http/response.rb:119:in
error!': 405 "Method Not Allowed" (Net::HTTPServerException) from C:/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http/response.rb:128:in
value'from C:/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:913:in
connect' from C:/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:862:in
do_start'from C:/Applications/Vagrant/embedded/lib/ruby/2.0.0/net/http.rb:857:in
start' from C:/Applications/Vagrant/embedded/lib/ruby/2.0.0/rubygems/remote_fetcher.rb:415:in
connection_for'So now the question is why can't I install vagrant-proxyconf?
steveo250k commentedon Sep 4, 2014
Update:
I had HTTP_PROXY and HTTPS_PROXY configured wrong. With the correct configuration I am able to install the vagrant-proxyconf
c:\Applications\Vagrant>vagrant plugin list
vagrant-login (1.0.1, system)
vagrant-proxyconf (1.3.2)
vagrant-share (1.1.1, system)
This also means I'm able to connect to the internet via vagrant. But I'm still getting this error:
c:\Applications\Vagrant>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise32' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'hashicorp/precise32' could not be found or
could not be accessed in the remote catalog. If this is a private
box on Vagrant Cloud, please verify you're logged in via
vagrant login
. Also, please double-check the name. The expandedURL and error message are shown below:
URL: ["https://vagrantcloud.com/hashicorp/precise32"]
Error: Could not resolve host: (nil); Host not found
kikitux commentedon Sep 5, 2014
if those are environment variable can you try to set:
export http_proxy=
export https_proxy=
export HTTP_PROXY=
export HTTPS_PROXY=
and also try
vagrant box add hashicorp/precise32
On Fri, Sep 5, 2014 at 12:44 AM, steveo250k notifications@github.com
wrote:
stevebutler-hsdg commentedon Apr 15, 2015
Running vagrant in a CMD terminal on Windows 7, I had the same problem with a corporate proxy. I set both HTTP_PROXY and HTTPS_PROXY, and then "vagrant box add ubuntu/trusty64" was successful.
kaushalsingh861 commentedon Jun 26, 2015
i had also this error
Error: Failed connect to atlas.hashicorp.com:443; No error
I just ran the CMD as administrator after setting HTTP proxy and it worked for me
sundarsrd commentedon Sep 19, 2015
Had the same issue;
figured out the exact issue (in correct proxy) by using --debug option.
in my case adding the port explicitly to the HTTP_PROXY/HTTPS_PROXY worked.
ex: set http_proxy=http://192.168.x.x:80
rajagopalan commentedon Nov 27, 2015
i am having the same issue. I was able to download the precise64,box from my corporate desktop, but my vagrant comand fails. i had setup the http_proxy as HTTP_PROXY'"http://hproxy.hh.local:3128" in system variables in a windows 7 machine.
ghost commentedon Dec 4, 2015
I was facing the same issue in Windows 8.
C:\Users\workspace\bosh-lite>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'cloudfoundry/bosh-lite' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: 9000.69.0
The box 'cloudfoundry/bosh-lite' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
vagrant login
. Also, please double-check the name. The expandedURL and error message are shown below:
URL: ["https://atlas.hashicorp.com/cloudfoundry/bosh-lite"]
Error: Failed connect to atlas.hashicorp.com:443; No error
setting the http_proxy and https_proxy from command line fixed the issue.
C:\Users\workspace\bosh-lite>set http_proxy=http://[corporate proxy]:8080
C:\Users\workspace\bosh-lite>set https_proxy=http://[corporate proxy]:8080
pssayi commentedon Feb 18, 2016
Same case for me , the HTTP / HTTPS proxy setting worked.
From the command line do set HTTP_PROXY= and set HTTPS_PROXY=
MartinGacheru commentedon Jul 25, 2016
how do you set port? via command git
thesamarkand commentedon Apr 16, 2017
SOLUTION FOR USERS WITH DIRECT CONNECTION TO INTERNET:
Go to Mu$tdie firewall settings, add allowing rules for:
C:\HashiCorp\Vagrant\embedded\bin\curl.exe
C:\HashiCorp\Vagrant\bin\vagrant.exe
9 remaining items