Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to Authenticate with vagrant cloud auth login - “Method Not Allowed” Error #13574

Open
warnyul opened this issue Jan 13, 2025 · 0 comments · May be fixed by #13580
Open

Unable to Authenticate with vagrant cloud auth login - “Method Not Allowed” Error #13574

warnyul opened this issue Jan 13, 2025 · 0 comments · May be fixed by #13580
Labels
waiting-intake

Comments

@warnyul
Copy link

warnyul commented Jan 13, 2025 •
edited
Loading

I am unable to authenticate with Vagrant Cloud using the vagrant cloud auth login command. I tried the following methods:

  1. Default command:
vagrant cloud auth login
  1. Explicitly specifying the server URL:
VAGRANT_SERVER_URL=https://app.vagrantup.com vagrant cloud auth login

In both cases, the command fails with the following error:

An unexpected error occurred: Vagrant Cloud request failed - Method Not Allowed

Debug output

debug.txt

Expected behavior

The command should authenticate successfully with Vagrant Cloud.

Actual behavior

The command fails with the “Method Not Allowed” error.

Reproduction information

Vagrant version

Vagrant 2.4.3

Host operating system

MacOS Sequoia 15.0.1
Chip: Apple M1 Pro

or

MacOS Sonoma 14.7
Intel Core i9

Guest operating system

Windows 11 arm64

Steps to reproduce

  1. Run vagrant cloud auth login in the terminal.
  2. Enter the credentials.
  3. Answer the token description question with default option.
  4. Observe the “Method Not Allowed” error.
@lnussbaum lnussbaum mentioned this issue Jan 13, 2025
Open
hswong3i added a commit to alvistack/hashicorp-vagrant that referenced this issue Jan 18, 2025
@hswong3i
Update from app.vagrantup.com to vagrantcloud.com
cfe1707 
As <hashicorp#13571 (comment)>
mentioned:

> After further debug, this looks like a change introduced in HCP
> Vagrant Registry after 2025-01-09, that broke Vagrant versions before
> 2.4.0. I could confirm that everything works fine with Vagrant 2.4.0
> (and later), but fails to work with Vagrant 2.3.7 (and earlier). The
> root cause is that Vagrant 2.3.7 uses the equivalent of curl
> --location --verbose -H "Accept: application/json"
> <https://vagrantcloud.com/debian/bookworm64> to fetch the box
> metadata, but this no longer returns a JSON document. Vagrant 2.4.0
> uses <https://vagrantcloud.com/api/v2/vagrant/debian/bookworm64>
> instead.

This PR replace most
<https://developer.hashicorp.com/vagrant/vagrant-cloud/api/v2> URL from
existing <https://app.vagrantup.com> to <https://vagrantcloud.com>.

Fixes <hashicorp#13571>
Fixes <hashicorp#13574>
Fixes <hashicorp#13575>

Signed-off-by: Wong Hoi Sing Edison <[email protected]>
@hswong3i hswong3i linked a pull request Jan 18, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
waiting-intake
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update from app.vagrantup.com to vagrantcloud.com alvistack/hashicorp-vagrant
1 participant
@warnyul