Skip to content
This repository has been archived by the owner on Feb 5, 2019. It is now read-only.

Vagrant Box not Found Error #20

Open
gr8abbasi opened this issue Feb 16, 2018 · 2 comments
Open

Vagrant Box not Found Error #20

gr8abbasi opened this issue Feb 16, 2018 · 2 comments

Comments

@gr8abbasi
Copy link

I'm getting this error when I'm trying to run vagrant up. I'm using Ubuntu 16.04 and Vagrant 1.9.4

Error: The requested URL returned error: 404 Not Found
The box 'debian/jessie64' 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/debian/jessie64"]
Error: The requested URL returned error: 404 Not Found
 INFO interface: Machine: error-exit ["Vagrant::Errors::BoxAddShortNotFound", "The box 'debian/jessie64' could not be found or\ncould not be accessed in the remote catalog. If this is a private\nbox on HashiCorp's Atlas, please verify you're logged in via\n`vagrant login`. Also, please double-check the name. The expanded\nURL and error message are shown below:\n\nURL: [\"https://atlas.hashicorp.com/debian/jessie64\"]\nError: The requested URL returned error: 404 Not Found"]
@gr8abbasi
Copy link
Author

It looks like url issue, I fixed the issue by adding line sylius_config.vm.box_url = "https://app.vagrantup.com/debian/boxes/jessie64" after
sylius_config.vm.box = "debian/jessie64"

Looks like we need to change the url to the boxes.

@hectorj
Copy link

hectorj commented Apr 9, 2018

Upgrading to Vagrant >2 also fixes the issue (as stated here hashicorp/vagrant#9442 (comment))

If you already have one version of the box and it fails to update, you can use the sed command from there: hashicorp/vagrant#9442 (comment)

QuenanChever added a commit to QuenanChever/Vagrant that referenced this issue Apr 25, 2018
QuenanChever added a commit to QuenanChever/Vagrant that referenced this issue May 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants