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

The box 'hashicorp/precise32' could not be found #5016

Closed
ken-colvin opened this Issue Dec 17, 2014 · 74 comments

Comments

Projects
None yet
@ken-colvin

ken-colvin commented Dec 17, 2014

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 comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh Dec 17, 2014

Member

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.

Member

mitchellh commented Dec 17, 2014

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

This comment has been minimized.

Show comment
Hide comment
@ken-colvin

ken-colvin Dec 17, 2014

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

ken-colvin commented Dec 17, 2014

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

This comment has been minimized.

Show comment
Hide comment
@kikitux

kikitux Dec 18, 2014

Collaborator

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.

Collaborator

kikitux commented Dec 18, 2014

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

This comment has been minimized.

Show comment
Hide comment
@ken-colvin

ken-colvin Dec 18, 2014

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

ken-colvin commented Dec 18, 2014

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

This comment has been minimized.

Show comment
Hide comment
@kikitux

kikitux Dec 18, 2014

Collaborator

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..

Collaborator

kikitux commented Dec 18, 2014

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..

@ken-colvin

This comment has been minimized.

Show comment
Hide comment
@ken-colvin

ken-colvin Dec 18, 2014

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

ken-colvin commented Dec 18, 2014

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

@sethvargo

This comment has been minimized.

Show comment
Hide comment
@sethvargo

sethvargo Dec 18, 2014

Contributor

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

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

sethvargo commented Dec 18, 2014

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

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

This comment has been minimized.

Show comment
Hide comment
@kmseverin

kmseverin Dec 28, 2014

Did anyone find a solution for error:0307A071?

kmseverin commented Dec 28, 2014

Did anyone find a solution for error:0307A071?

@sethvargo

This comment has been minimized.

Show comment
Hide comment
@sethvargo

sethvargo Dec 28, 2014

Contributor

Are you running on an AMD processor?

Contributor

sethvargo commented Dec 28, 2014

Are you running on an AMD processor?

@kmseverin

This comment has been minimized.

Show comment
Hide comment
@kmseverin

kmseverin Dec 29, 2014

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

kmseverin commented Dec 29, 2014

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

@sethvargo

This comment has been minimized.

Show comment
Hide comment
@sethvargo
Contributor

sethvargo commented Dec 29, 2014

@sethvargo

This comment has been minimized.

Show comment
Hide comment
@sethvargo

sethvargo Dec 29, 2014

Contributor

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

Contributor

sethvargo commented Dec 29, 2014

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

@ken-colvin

This comment has been minimized.

Show comment
Hide comment
@ken-colvin

ken-colvin Dec 29, 2014

Yes it is AMD

ken-colvin commented Dec 29, 2014

Yes it is AMD

@sethvargo

This comment has been minimized.

Show comment
Hide comment
@sethvargo

sethvargo Dec 29, 2014

Contributor

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

Contributor

sethvargo commented Dec 29, 2014

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

@sethvargo sethvargo closed this Dec 29, 2014

@azzazzel

This comment has been minimized.

Show comment
Hide comment
@azzazzel

azzazzel Jan 14, 2015

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!

azzazzel commented Jan 14, 2015

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

This comment has been minimized.

Show comment
Hide comment
@benjick

benjick Jan 21, 2015

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

benjick commented Jan 21, 2015

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

This comment has been minimized.

Show comment
Hide comment
@sethvargo

sethvargo Jan 21, 2015

Contributor

@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.

Contributor

sethvargo commented Jan 21, 2015

@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

This comment has been minimized.

Show comment
Hide comment
@azzazzel

azzazzel Jan 21, 2015

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

azzazzel commented Jan 21, 2015

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

@AntonioCS

This comment has been minimized.

Show comment
Hide comment
@AntonioCS

AntonioCS Jan 30, 2015

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 commented Jan 30, 2015

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

This comment has been minimized.

Show comment
Hide comment
@AntonioCS

AntonioCS Jan 30, 2015

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 commented Jan 30, 2015

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

This comment has been minimized.

Show comment
Hide comment
@AntonioCS

AntonioCS Mar 20, 2015

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

AntonioCS commented Mar 20, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ntrepid8

ntrepid8 Mar 22, 2015

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:

ntrepid8 commented Mar 22, 2015

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 comment has been minimized.

Show comment
Hide comment
@conikeec

conikeec commented Mar 30, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ken-colvin

ken-colvin Apr 2, 2015

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?

ken-colvin commented Apr 2, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ashishbatra

ashishbatra Apr 4, 2015

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

ashishbatra commented Apr 4, 2015

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

@nek-v

This comment has been minimized.

Show comment
Hide comment
@nek-v

nek-v Feb 22, 2016

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

nek-v commented Feb 22, 2016

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

This comment has been minimized.

Show comment
Hide comment
@vjpr

vjpr Feb 29, 2016

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

vjpr commented Feb 29, 2016

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

This comment has been minimized.

Show comment
Hide comment
@foxlance

foxlance Mar 2, 2016

@cgons suggestion worked for me too!

foxlance commented Mar 2, 2016

@cgons suggestion worked for me too!

@boywondercreative

This comment has been minimized.

Show comment
Hide comment
@boywondercreative

boywondercreative commented Mar 31, 2016

danke @AntonioCS and @cgons

@newrulez

This comment has been minimized.

Show comment
Hide comment
@newrulez

newrulez Nov 11, 2016

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 :)

newrulez commented Nov 11, 2016

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

This comment has been minimized.

Show comment
Hide comment
@garciaae

garciaae Nov 12, 2016

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

garciaae commented Nov 12, 2016

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

This comment has been minimized.

Show comment
Hide comment
@msmollin

msmollin Nov 12, 2016

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.

msmollin commented Nov 12, 2016

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

This comment has been minimized.

Show comment
Hide comment
@newrulez

newrulez Nov 12, 2016

@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.

newrulez commented Nov 12, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@adis-io

adis-io Nov 13, 2016

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

adis-io commented Nov 13, 2016

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

This comment has been minimized.

Show comment
Hide comment
@nestorpina

nestorpina Nov 13, 2016

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

nestorpina commented Nov 13, 2016

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

This comment has been minimized.

Show comment
Hide comment
@nagmak

nagmak Nov 14, 2016

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

nagmak commented Nov 14, 2016

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

@stuzog

This comment has been minimized.

Show comment
Hide comment
@stuzog

stuzog Nov 15, 2016

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

stuzog commented Nov 15, 2016

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

@ninuxio

This comment has been minimized.

Show comment
Hide comment
@ninuxio

ninuxio commented Nov 15, 2016

@stuzog +1

@ismailakbudak

This comment has been minimized.

Show comment
Hide comment
@ismailakbudak

ismailakbudak Nov 16, 2016

+1 Mac OS X - El Capitan 10.11.6

ismailakbudak commented Nov 16, 2016

+1 Mac OS X - El Capitan 10.11.6

@benjaminhyw

This comment has been minimized.

Show comment
Hide comment
@benjaminhyw

benjaminhyw Nov 18, 2016

Thanks for the fix @nestorpina ! macOS Sierra 10.12.1

benjaminhyw commented Nov 18, 2016

Thanks for the fix @nestorpina ! macOS Sierra 10.12.1

@dantabel

This comment has been minimized.

Show comment
Hide comment
@dantabel

dantabel Nov 21, 2016

thank you @nestorpina, that worked for me too!

dantabel commented Nov 21, 2016

thank you @nestorpina, that worked for me too!

@biggiemac

This comment has been minimized.

Show comment
Hide comment
@biggiemac

biggiemac Nov 22, 2016

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

biggiemac commented Nov 22, 2016

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

@maxiaoxiong

This comment has been minimized.

Show comment
Hide comment
@maxiaoxiong

maxiaoxiong Nov 23, 2016

@newrulez you are right!!! Thank you!

maxiaoxiong commented Nov 23, 2016

@newrulez you are right!!! Thank you!

@advance512

This comment has been minimized.

Show comment
Hide comment
@advance512

advance512 Nov 25, 2016

Thanks @nestorpina. What a stupid issue. :/

advance512 commented Nov 25, 2016

Thanks @nestorpina. What a stupid issue. :/

@airbr

This comment has been minimized.

Show comment
Hide comment
@airbr

airbr Nov 26, 2016

Thank you @nestorpina ! Legend

airbr commented Nov 26, 2016

Thank you @nestorpina ! Legend

@conatus

This comment has been minimized.

Show comment
Hide comment
@conatus

conatus Nov 28, 2016

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

conatus commented Nov 28, 2016

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

@Japh

This comment has been minimized.

Show comment
Hide comment
@Japh

Japh Dec 11, 2016

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

Japh commented Dec 11, 2016

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

@alisade

This comment has been minimized.

Show comment
Hide comment
@alisade

alisade Dec 22, 2016

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)

alisade commented Dec 22, 2016

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

This comment has been minimized.

Show comment
Hide comment
@tin6150

tin6150 Sep 16, 2017

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.

tin6150 commented Sep 16, 2017

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

This comment has been minimized.

Show comment
Hide comment
@engmsaleh

engmsaleh May 19, 2018

Not working on High sierra :(

engmsaleh commented May 19, 2018

Not working on High sierra :(

@mattgilbertnet

This comment has been minimized.

Show comment
Hide comment
@mattgilbertnet

mattgilbertnet Sep 21, 2018

Also didn't work for me on High Sierra

mattgilbertnet commented Sep 21, 2018

Also didn't work for me on High Sierra

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