Vagrant cannot find box

Question

I am on windows 10 and has VirtualBox 5.0.14 and vagrant 1.8.1 installed in it.

While i try to add a box it gives me this error:

Command: $ vagrant box add ubuntu/trusty64

Error:

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:

Any idea for this issue?

can you download the file directly : https://atlas.hashicorp.com/ubuntu/boxes/trusty64/versions/20160215.0.0/providers/virtualbox.box and then add a box from this downloaded file — Frederic Henri, Feb 22 '16 at 21:35
These are probably not the answers. What happened is that Hashicorp changed its download URL! Upgrade to Vagrant 2.x and you will not have this problem. — Oliver Williams, Feb 24 '18 at 11:44
Do you use a VPN? I had this issue when it was enabled, probably because the server was blacklisted. — IT-bob, May 25 '21 at 11:05
STOP your Antivirus! It'll work. Antivirus is blocking the request to download. — HumbleBee, Nov 19 '22 at 16:23

score 165 · Answer 1 · answered Nov 10 '16 at 06:45

165

Try this

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

https://github.com/Varying-Vagrant-Vagrants/VVV/issues/354

answered Nov 10 '16 at 06:45

imansyaefulloh

1,783
1
10
7

1

Thanks I wonder how you found this since even with --debug on it doesn't talk about curl. – Benoit Vanalderweireldt Nov 14 '16 at 05:29
3

This works and is still required in Vagrant 1.8.7 and virtual box 5.1.X on OSX. – bjw Nov 14 '16 at 12:20
As bjw stated, same issue happened here with Vagrant 1.8.7 and VB 5.1.x, this helps! thank you! – whalesingswee Nov 16 '16 at 03:11
hope thy fix this in the next vagrant release – PartySoft Nov 18 '16 at 15:25
Today, you are my hero. Thank you! – AngelGabriel Nov 23 '16 at 09:18
Worked for me on OSX – user2694306 Nov 23 '16 at 15:27
such an unacceptable issue. you'd think the vagrant devs would do some bare minimum testing. thanks for the fix. – Brade Nov 25 '16 at 02:16
1

Worked for OSX, Vagrant 1.8.7. Thank you! – vasya10 Nov 29 '16 at 03:32
Downvoted because the OP was asking about Windows. Please make a separate question for OSX. – tpartee Sep 21 '17 at 20:40
Confirm that this also works on Linux , distro is Oracle Linux 7 (Redhat 7) running Vagrant 2.0.2. I opted for a non-destructive `mv /opt/vagrant/embedded/bin/curl /opt/vagrant/embedded/bin/curl.bak` befroe deleting however! :) – The_Neo Oct 16 '18 at 10:40

score 52 · Answer 2 · answered Feb 17 '18 at 18:06

52

Potential TOP reason after 2018: Hashicorp has changed the download URL.

For a quick workaround add this to your Vagrantfile:

Vagrant::DEFAULT_SERVER_URL.replace('https://vagrantcloud.com')

and run vagrant up again.

or

Upgrade vagrant to v2.0+

More details: https://github.com/hashicorp/vagrant/issues/9442

answered Feb 17 '18 at 18:06

Attila Fulop

6,861
2
44
50

This works on Vagrant 1.9 also. By adding "Vagrant::DEFAULT_SERVER_URL.replace('vagrantcloud.com')"to my Vagrant file, I was able to dowload the ubuntu/xenial64 vbox. – Binita Bharati May 25 '18 at 08:15
I get the error `uninitialized constant Vagrant::DEFAULT_SERVER_URL (NameError)` on running `vagrant up` after making the change. – Barun Sharma Nov 21 '18 at 09:48
@BarunSharma What is your vagrant version? Use `vagrant -v` to get it. – Attila Fulop Nov 21 '18 at 10:06
@AttilaFulop - its 'Vagrant version 1.0.1' – Barun Sharma Nov 21 '18 at 19:47
@BarunSharma 1.0.1 is almost 7 years old. I couldn't find which version was the constant introduced, but looks 1.0.1 is way too old. – Attila Fulop Nov 22 '18 at 06:35
It doesn't work for me on vagrant 2.2.14 on Ubuntu 20.10. I get this error: `Message: FrozenError: can't modify frozen String` – rubo77 May 25 '21 at 16:10

score 4 · Answer 3 · answered May 18 '16 at 12:29

4

Installing Microsoft Visual C++ 2010 SP1 Redistributable Package (as mentioned in ticket #6745) solved the issue for me.

answered May 18 '16 at 12:29

Johan de Vries

175
1
9

I found that ticket before I found your answer, but your answer is definitely correct here. Right after installing that package, Vagrant is now working as expected. – Buttle Butkus Jun 14 '16 at 02:12

score 3 · Answer 4 · answered Mar 01 '16 at 22:13

There are issues with the new version 1.8.x of vagrant and Windows 10 as described in ticket #6745 and a string of related tickets. I tried some of the advice that people are giving, but the one thing that works straight away is to downgrade your vagrant to version 1.7.4.

To do that first uninstall your current version 1.8.x. Then go to the vagrant download page, and then select download older versions of Vagrant. There you can select vagrant_1.7.4.msi.

Install version 1.7.4, reboot your machine and you are ready to go (again) using the statement as per your question:

$ vagrant box add ubuntu/trusty64

It should start to download without further issue.

score 1 · Answer 5 · edited May 26 '21 at 20:36

1

I had this problem starting the vagrant box (Using git as Terminal, https://git-scm.com/download/win):

$ vagrant box add ubuntu/trusty64
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 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: schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.

The problem was my anti virus (Kaspersky) that was preventing me from adding the box. I deactivated the anti virus and the command worked:

$ vagrant box add ubuntu/trusty64
$ vagrant init ubuntu/trusty64
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.

NASA@DESKTOP-P6O3UKQ MINGW64 /d/Vagrant1
$ vagrant up

edited May 26 '21 at 20:36

IT-bob

316
1
2
8

answered Apr 19 '21 at 23:26

Adilson Santos

29
1

This question is very confusing due to the formatting. I think you are using `code blocks` to write down your experience and regular text to right down input/output from the terminal? That's like the opposite of what you should be doing. – Michael Hoobler Apr 20 '21 at 10:46
@MichaelHoobler But.. this is an Answer :) – Scratte May 26 '21 at 20:35
@Scratte You're right, this is an answer and not a question. Looks like someone went through and edited your post, but try to use the `code blocks` and other formatting tools correctly in your future questions/answers so that your posts end up being as helpful as possible. Your insight is appreciated and it'd be a shame if someone needed this answer and skipped it because the formatting was weird. :) – Michael Hoobler May 27 '21 at 14:03
1

@MichaelHoobler Thanks for the tip, but.. this isn't *my* Answer. – Scratte May 27 '21 at 15:18
Thanks for the tip, Kaspersky was the issue for me! – Ryhazerus Feb 26 '22 at 12:29

score -1 · Answer 6 · edited May 23 '17 at 11:54

I had the same issue on Windows 10 and Vagrant 1.9.1. I tried all the above tricks (installing VisualC++, downgrading Vagrant to 1.7, copy over curl from git bash, installing openssh) but finally I found the solution thus:

vagrant up --debug: it revealed that home dir for vagrant was my user homedir which was having non-latin symbols. When vagrant downloads box file from external url, it tries to save it in its home dir, which is ~/.vagrant.d (for Windows that means for example C:/Users/Ольга/.vagrant.d)
vagrant.d outside of the home folder - change file \HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.5.3\lib\vagrant\environment.rb on line 119 to @home_path = Util::Platform.fs_real_path("C:/vagrant/home/") - where C:/vagrant/home can be any dir without non-latin symbols, for example, c:/HashiCorp/Home.

score -2 · Answer 7 · edited May 04 '18 at 08:14

-2

It will fix your error:

vagrant destroy

Use version 5.18 of virtual box, then install version 1.9.2 of a vagrant. Restart your computer. Now go to the directory you want to work in.

vagrant init ubuntu/trusty64
vagrant up

edited May 04 '18 at 08:14

rollstuhlfahrer

3,988
9
25
38

answered May 04 '18 at 07:42

ayush didwaniya

484
6
4

Vagrant cannot find box

7 Answers7