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\bin\curl -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

[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!

[ghost]

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.