Vagrant: The box 'hashicorp/precise32' could not be found

[ken-colvin]

I followed the instructions on vagrantup.com but a box is not being downloaded.
On Windows 8.1

This is driving me nuts, please help.

see https://docs.vagrantup.com/v2/getting-started/index.html

I run the commands:
$ vagrant init hashicorp/precise32
$ vagrant up
I then get the following error:

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 HashiCorp's Atlas, 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://atlas.hashicorp.com/hashicorp/precise32"]
Error: error:0307A071:bignum routines:BN_rand_range:too many iterations

[mitchellh]

This is a weidr error that looks like it is coming from curl (which ships with Vagrant):

"Error: error:0307A071:bignum routines:BN_rand_range:too many iterations"

I tried it myself and I'm not getting this error. Without a reproduction case we're not going to be able to fix this? I hope someone can come in and provide more input.

This also might be related to #5001. We'll change the certs for 1.7.2 and see what happens. Otherwise, I don't think this can be fixed... we need more info.

[ken-colvin]

Thanks for the quick reply. That customer satisfaction is what makes you rise above the rest :)

As a work around I can do a "vagrant box add name URL". What is the URL to download the box? For example, what is the full URL for the boxes in https://atlas.hashicorp.com/boxes/search, if I want to use https://atlas.hashicorp.com/ubuntu/boxes/trusty64 then what is the full domain so I can add the box?

vagrant box add trusty64 http://{URL}/ubuntu/trusty64.box

Likewise,
vagrant box add name http://{URL.com}/hashicorp/precise32.box

[kikitux]

The url to add is

vagrant box add precise32 https://vagrantcloud.com/hashicorp/boxes/precise32/versions/1.0.0/providers/virtualbox.box

all that in one line.

however, curl will be the same, so you should hit the same issue.

[ken-colvin]

Thanks. Can you please post url for ubuntu/trusty64.
Also, is there a list of URL's for these vagrant boxes so one can do a vagrant box add "name" URL

[kikitux]

Hello, try to troubleshoot first, useful to get a clear idea what is wrong..you need adjust the path to the Windows .. find the curl binary somewhere in c:\hashicorp\vagrant

Command will be something like this:

c:\hashicorp\vagrant\embedded\bincurl -o virtualbox.box -L https://vagrantcloud.com/hashicorp/boxes/precise32/versions/1.0.0/prov
iders/virtualbox.box

if you get an error by certificate.. try add -k but paste all the output..

[kikitux]

url for precise 64 are these:

{"name":"hyperv","url":"https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/hyperv.box"},

{"name":"vmware_fusion","url":"https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/vmware_fusion.box"},

{"name":"virtualbox","url":"https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/virtualbox.box"}

[ken-colvin]

I appreciate you trying to help here. Do you have the URL's for ubuntu/trusty64 box

[sethvargo]

@devalphabeta the box URLs are predictable - they are just:

https://vagrantcloud.com/USERNAME/boxes/BOXNAME/versions/VERSION/providers/PROVIDER.box

[kmseverin]

Did anyone find a solution for error:0307A071?

[sethvargo]

Are you running on an AMD processor?

[kmseverin]

Yes, I'm running AMD A8-6410 APU processor

[sethvargo]

@kmseverin it's actually a Kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=85911

[sethvargo]

@devalphabeta can you confirm you are running AMD as well?

[ken-colvin]

Yes it is AMD

[sethvargo]

@devalphabeta okay. This is a kernel bug, and unfortunately there is nothing we can do to fix it /cc @mitchellh

[azzazzel]

I'm getting similar error on Linux Mint 17 Qiana! Providing explicit URL works but just name doesn't:

$ vagrant init hashicorp/precise32
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'hashicorp/precise32' could not be found.

The CPU is Intel Core i7! I suspected some network errors but ngrep did not catch any request!

[benjick]

Getting a similar error on Windows 10 (tech preview), Intel i7 cpu

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
The box 'ubuntu/trusty64' 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/ubuntu/trusty64"]
Error: SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

[sethvargo]

@azzazzel the error you are getting is different than the one in this issue. The key phrase is Error: error:0307A071:bignum routines:BN_rand_range:too many iterations and I do not see that in your output. Could you please open a new issue and include the Vagrant debug output

@benjick your issue seems related to CA certificates. Please make sure you are running the latest version of Vagrant for Windows. You may also be encountering an installer bug.

[azzazzel]

Thanks @sethvargo!
As per your request I created #5231

[AntonioCS]

Has a solution been found?
I am getting this error : error:0307A071:bignum routines:BN_rand_range:too many iterations

On a machine running win 7 I have no problems but on another one that is running windows 8 with vagrant 1.7.2 I can't get any boxes.
Even if I try do add the box it doesn't work.

The box url is: https://vagrantcloud.com/janschumann/boxes/debian-7/versions/7.8.0.0/providers/virtualbox.box

This is perfectly accessible and valid url but I still get the error

[AntonioCS]

So I tried to get hashicorp/precise64 with --debug. This is what I got (just pasting what I assume are the more important parts):

INFO downloader: HEAD: https://vagrantcloud.com/hashicorp/precise64
 INFO subprocess: Starting process: ["C:\\HashiCorp\\Vagrant\\embedded\\bin/curl
.EXE", "-I", "-q", "--fail", "--location", "--max-redirs", "10", "--user-agent",
 "Vagrant/1.6.5", "--continue-at", "-", "-H", "Accept: application/json", "https
://vagrantcloud.com/hashicorp/precise64"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:   % Total    % Received % Xferd  Average Speed   Time
   Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) error:0307A071:bignum routines:BN_rand_range:too many iterations
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 35
 WARN downloader: Downloader exit code: 35
ERROR warden: Error occurred: The box 'hashicorp/precise64' could not be found o
r

There seems to be an issue with curl but I am not using the latest version. I have downgraded to 1.6.5. So I assume there is something wrong with curl on win 8.

Is there a way to bypass this problem?? I am unable to use vagrant.

Help????

[AntonioCS]

I fixed this issue by replacing the curl.exe in the folder C:\HashiCorp\Vagrant\embedded\bin.
I got curl (for win64 with ssl) from:
http://curl.haxx.se/latest.cgi?curl=win64-ssl-sspi

[ntrepid8]

I'm also seeing this error. I just installed vagrant on OS X for the first time today and copy/pasted the command out of the docs:

$ vagrant box add hashicorp/precise64
The box 'hashicorp/precise64' 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 expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/hashicorp/precise64"]
Error:

[conikeec]

This should do it (all in one line)

vagrant box add precise64 https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/virtualbox.box

[ken-colvin]

Does someone have a solution or workaround for the "Error: error:0307A071:bignum routines:BN_rand_range:too many iterations" problem?

I purchased a new laptop and getting this same damn error.

Does anyone know how to manually download the box https://atlas.hashicorp.com/laravel/boxes/homestead (using ftp, curl, wget, ...) and setup the Vagrantfile to use the local copy?

[ashishbatra]

Thanks AntonioCS
I also fixed this issue by replacing the curl.exe in the folder C:\HashiCorp\Vagrant\embedded\bin.
I got curl (for win64 with ssl) from:
http://curl.haxx.se/latest.cgi?curl=win64-ssl-sspi

I am on AMD64 processor

[ken-colvin]

Thanks ashishbatra that totally worked. Wish Vagrant would write down this solution so everyone who has an AMD will not got through this time consuming process.

[ramblescout]

The way conikeec works for me on a Mac OS:
vagrant box add precise64 https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/virtualbox.box

[mykeylynx]

The machine with the name 'hashicorp/precise32' was not found configured for
this Vagrant environment.

:neckbeard:
I solved this by:
vagrant up
vagrant global-status
vagrant up bc7940e

[Subby]

Thank you AntonioCS and ashishbatra, replacing the curl executable worked for me too.

[ghost]

Thanks Antonio and ashishbatra! You saved me a lot of headache!

[scholarly]

The curl from msys Git-1.9.5-preview20150319 also works.

$ /C/HashiCorp/Vagrant/embedded/bin/badcurl.exe -V
curl 7.29.0 (i386-pc-win32) libcurl/7.29.0 OpenSSL/1.0.1c zlib/1.2.7
Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile NTLM SSL libz

$ curl -V
curl 7.41.0 (i386-pc-win32) libcurl/7.41.0 OpenSSL/0.9.8zf zlib/1.2.8
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile SSPI Kerberos SPNEGO NTLM SSL libz

[stevek-pro]

On OSX Yosemite do a brew install curl. Then vagrant up should work again.

If not, then make sure to clear or set these environment variables as well: http_proxy, https_proxy, ALL_PROXY, HTTP_PROXY, HTTPS_PROXY, VAGRANT_HTTP_PROXY.

If still no progress you could fiddle around with the vagrant-proxyconf plugin. All three issues I did experience.

[saurabh-agrawal83]

Following commands fixed the problem with vagrant 1.7.2

brew install curl
export DYLD_INSERT_LIBRARIES=

[CarlOlivotto]

I've placed the curl file in the embedded/bin folder and it didn't work for me. I've also reset all the env vars that @nottinhill has recommended.

Currently on Windows 8.1. PC is a 64 bit machine running on Intel i3.

[joelfrens]

Thank you AntonioCS and ashishbatra. The curl replace fixed the issue

[vishk]

I'm on Windows 10 and ran into the same error. I had to update the curl.exe like AntonioCS said. Also, I had to get msvcs100.dll from http://www.microsoft.com/en-us/download/details.aspx?id=13523 (for 64 bit).Then I was able to verify that the curl.exe works by trying
curl.exe -I -s http://www.google.com
after which vagrant up also worked.

[iboxgithub]

Same error on Ubuntu, I did

vagrant init hashicorp/precise32

vagrant up

--> and this is what I have...

Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'hashicorp/precise32' could not be found.

[gbroques]

@AntonioCS Thank you, your solution work for me!

I fixed this issue by replacing the curl.exe in the folder C:\HashiCorp\Vagrant\embedded\bin.
I got curl (for win64 with ssl) from:
http://curl.haxx.se/latest.cgi?curl=win64-ssl-sspi

[ShaikAsifullah]

@AntonioCS Thank you, your solution was awesome. It worked great!!!

[dobando-dev]

@AntonioCS Thank you, your solution work for me!

I fixed this issue by replacing the curl.exe in the folder C:\HashiCorp\Vagrant\embedded\bin.
I got curl (for win64 with ssl) from:
http://curl.haxx.se/latest.cgi?curl=win64-ssl-sspi

[cgons]

For anyone else having an issue adding a box. It's possible that there's nothing wrong with the curl.exe provided by Vagrant, but rather, you do not have the Visual C++ 2010 Redistributable installed on your system.

I had this same issue after installing Vagrant on a fresh Windows 10 x64 machine.

You can download the Visual C++ 2010 Redistributable (x86 version) directly from MS here:
https://www.microsoft.com/en-us/download/details.aspx?id=26999

After installing that, I was successfully able to add vagrant boxes.

[iboxgithub]

For Ubuntu people : fixed using last version (1.8.1)
Download the Debian package (64 bits in my case) and use 'dpkg'

[yaahor]

cgons, you are right. Thank you!

[MickaelSalmon]

Same here, replacing curl.exe works fine ( running on Windows 10, Proc I7)

[youhubs]

@cgons, Thank you! You helped me solve the problem. I am running on Windows 7.

[rtspeaks360]

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/trusty32' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'ubuntu/trusty32' 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 expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/ubuntu/trusty32"]
Error:

(Getting this error while running vagrant on a windows 10 machine.)

[santibayo]

if you are using windows 10 , go to embeded/bin and type curl
in my case the error shown was: MSvcr100.dll is missing .
in order to fix it I downloaded curl with SSL support from the official website and copied the binary to the folder embeded/bin.
It worked like a charm
Regards

[nek-v]

I solved this problem by downloading Curl here http://www.paehl.com/open_source/?download=curl_747_1_ssl.zip (Win 7 x86)
extract in C:\HashiCorp\Vagrant\embedded\bin

[vjpr]

I can confirm that @cgons's solution works.

I had this same issue after installing Vagrant on a fresh Windows 10 x64 machine.

You can download the Visual C++ 2010 Redistributable (x86 version) directly from MS here:
https://www.microsoft.com/en-us/download/details.aspx?id=26999

[foxlance]

@cgons suggestion worked for me too!

[boywondercreative]

danke @AntonioCS and @cgons

[newrulez]

i didn't find a solution so i helped myself.
for mac os x sierra with newest vagrant 1.8.7 i fixed like following.

THATS the problem

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'ubuntu/trusty64' 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 expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/ubuntu/trusty64"]
Error:

the problem is the provided curl from vagrant

following error in crash report

Dyld Error Message:
Library not loaded: @rpath/libcurl.4.dylib
Referenced from: /opt/vagrant/*/curl
Reason: Incompatible library version: curl requires version 9.0.0 or later, but libcurl.4.dylib provides version 7.0.0

The Curl from brew is ok so I did following:

THATS my Solution

as root with sudo (deactivated to bad ones provided with vagrant)
sudo mv /opt/vagrant/embedded/bin/curl /opt/vagrant/embedded/bin/curl_orig
sudo mv /opt/vagrant/embedded/bin/curl-config /opt/vagrant/embedded/bin/curl-config_orig

symlink the good one from brew
sudo ln -s /usr/bin/curl /opt/vagrant/embedded/bin/curl
sudo ln -s /usr/bin/curl-config /opt/vagrant/embedded/bin/curl-config

Now the magic :)

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'ubuntu/trusty64'
default: URL: https://atlas.hashicorp.com/ubuntu/trusty64
==> default: Adding box 'ubuntu/trusty64' (v20161109.0.0) for provider: virtualbox
default: Downloading: https://atlas.hashicorp.com/ubuntu/boxes/trusty64/versions/20161109.0.0/providers/virtualbox.box
==> default: Successfully added box 'ubuntu/trusty64' (v20161109.0.0) for 'virtualbox'!
==> default: Importing base box 'ubuntu/trusty64'... and so on :)

[garciaae]

My config:
Mac OS Sierra + curl 7.32.0

curl location:

which curl
/opt/local/bin/curl

So my commands were:

sudo mv /opt/vagrant/embedded/bin/curl /opt/vagrant/embedded/bin/curl_orig
sudo mv /opt/vagrant/embedded/bin/curl-config /opt/vagrant/embedded/bin/curl-config_orig
sudo ln -s /opt/local/bin/curl /opt/vagrant/embedded/bin/curl
sudo ln -s /opt/local/bin/curl-config /opt/vagrant/embedded/bin/curl-config

[msmollin]

To clarify for anyone coming across this and running macOS 10.12 (Sierra), @newrulez's answer actually symlinks (by default) to Apple's version of curl, _not_ Homebrew's version. That's because, by default, the newest versions of Homebrew will not attempt to override anything provided by the OS. Note: This is fine and their answer works great (I'm using it now myself).

If you really want to use the Homebrew version, on my machine Homebrew places its version of curl at /usr/local/opt/curl/binbecause this avoids macOS's Rootless security system, as /usr/local/ is ignored by it.

[newrulez]

@msmollin: I didn't know this since yet that homebrow doesn't affect the original files anymore. good development. thx for info. but also remember that you have to change it any time you update the vagrant base system if they don't fix this. but easy. it works very well so. with the original curl is even more better. -> less packages less attack surface.

[adis-io]

My config:
OSX El Capitan + curl 7.43.0

curl location:

which curl
/opt/local/bin/curl

sudo mv /opt/vagrant/embedded/bin/curl /opt/vagrant/embedded/bin/curl_orig
sudo mv /opt/vagrant/embedded/bin/curl-config /opt/vagrant/embedded/bin/curl-config_orig
sudo ln -s /usr/bin/curl /opt/vagrant/embedded/bin/curl
sudo ln -s /usr/bin/curl-config /opt/vagrant/embedded/bin/curl-config

[nestorpina]

For me linking to osx or homebrew versions didn't work. What did the trick was just simply removing the included vagrant curl

sudo rm /opt/vagrant/embedded/bin/curl

[nagmak]

I'm on osx yosemite, and this worked well for me =) Thanks @nestorpina!

[stuzog]

@nestorpina Your solution also worked on El Capitan 10.11.6 -- thanks!

[ninuxio]

@stuzog +1

[ismailakbudak]

+1 Mac OS X - El Capitan 10.11.6

[benjaminhyw]

Thanks for the fix @nestorpina ! macOS Sierra 10.12.1

[dantabel]

thank you @nestorpina, that worked for me too!

[biggiemac]

Thanks for the fix @nestorpina ! macOS Sierra 10.12.1 - worked like a charm!

[maxiaoxiong]

@newrulez you are right!!! Thank you!

[advance512]

Thanks @nestorpina. What a stupid issue. :/

[airbr]

Thank you @nestorpina ! Legend

[conatus]

@nestorpina - this also worked for me. Thanks a lot.

[Japh]

@nestorpina Thanks! Your suggestion of removing the embedded version worked for me too.
macOS Sierra 10.12.1 and Vagrant 1.8.7

[alisade]

thanks @nestorpina, same solution worked for me
Virtualbox: 5.1.8 r111374 (Qt5.5.1)
Vagrant: Vagrant 1.8.7
OSX El Capitan 10.11.6 (15G1212)

[tin6150]

FWIW, I needed to run
vagrant box add centos/7 https://vagrantcloud.com/centos/boxes/7/versions/1708.01/providers/virtualbox.box
on mint 17.2 in order to obtain a centos 7.3 box.

[engmsaleh]

Not working on High sierra :(

[mattgilbertnet]

Also didn't work for me on High Sierra

[ramprsad1433]

Hi Team,

I'm unable to install ubuntu OS 32 & 64 bit, i tried multiple OS's ,Still Frequently getting 404 Not Found,Please check and reply immediate action,it's very ugent.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise64' could not be found. Attempting to find and 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 HashiCorp's Atlas, 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://atlas.hashicorp.com/hashicorp/precise64"]
Error: The requested URL returned error: 404 Not Found

[ramprsad1433]

@Seth Vargo sethvargo,
@Collaborator
kikitu

I'm unable to install ubuntu OS 32 & 64 bit, i tried multiple OS's ,Still Frequently getting 404 Not Found,Please check and reply immediate action,it's very ugent.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise64' could not be found. Attempting to find and 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 HashiCorp's Atlas, 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://atlas.hashicorp.com/hashicorp/precise64"]
Error: The requested URL returned error: 404 Not Found

[briancain]

@ramprsad1433 - Please upgrade your version of Vagrant. That should fix the broken URL. Thanks!

[hashibot[bot]]

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.