Error: The requested URL returned error: 403

Vagrant
1

Hello,

I want to install generic/debian10 on MacOs 11.13.1 with Vagrant 2.2.16 and Virtualbox 6.1.22.

The error is:

vagrant up        
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'generic/debian10' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
The box 'generic/debian10' 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/generic/debian10"]
Error: The requested URL returned error: 403

Box is public: https://app.vagrantup.com/generic/boxes/debian10
Connectivity is OK.

Why ?
Thanks

2

Hi,
Temporary fix:

wget https://app.vagrantup.com/generic/boxes/debian10/versions/3.2.20/providers/virtualbox.box -O debian-buster10.box
vagrant box add generic/debian10 debian-buster10.box
cd ~/.vagrant.d/boxes/generic-VAGRANTSLASH-debian10
mv 0 3.2.20
echo -n “https://app.vagrantup.com/generic/boxes/debian10” > metadata_url

3

I have the same errror trying to install laravel/homestead on a windows 10…

1 Like
4

I have a terrible feeling that Vagrant Cloud is broken and that no one is bothering …
Disturbing …

5

Please, see this related topic at GitHUB any up and box add gives Error: The requested URL returned error: 403 · Issue #12390 · hashicorp/vagrant · GitHub

It is looking like a DNS replication issue.

Regards

6

Hi everyone,

My apologies for the errors that were encountered and any inconvenience it may have caused. It was a DNS related configuration update which caused some of the redirects to break. It has been fixed and Vagrant Cloud is working as normal again.

Cheers

1 Like
7

The login process is not still working

I’ve just open a new Github issue where you can see details about error Vagrant cloud auth does not still work · Issue #12393 · hashicorp/vagrant · GitHub

8

Hey folks,

Sorry about the inconvenience this has caused. The DNS configuration that has caused this issue has been updated. However, it may take some time before users will see that it is in fact resolved as the DNS changes propagate.

In the mean time, users can get around this issue by exporting the VAGRANT_SERVER_URL environment variable to https://app.vagrantup.com/.

Thanks!