Can not login to vagrant cloud. What am I doing wrong?

I am do:
vagrant cloud auth login
then enter my login and password, like
here: vagrant package - Command-Line Interface | Vagrant by HashiCorp
but he suddenly starts asking something like “token description” (what does it mean?)
i enter it and then take Vagrant Cloud request failed

/opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:132:in `rescue in request': Vagrant Cloud request failed (VagrantCloud::Error::ClientError::RequestError)
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:129:in `request'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:192:in `authentication_token_create'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/client/client.rb:75:in `block in login'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/client/client.rb:167:in `with_error_handling'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/client/client.rb:74:in `login'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/util.rb:69:in `client_login'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/auth/login.rb:54:in `execute'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/lib/vagrant/cli.rb:67:in `execute'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/lib/vagrant/environment.rb:290:in `cli'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/bin/vagrant:231:in `<main>'
/opt/vagrant/embedded/gems/2.2.16/gems/excon-0.81.0/lib/excon/middlewares/expects.rb:13:in `response_call': Expected([200, 201, 204]) <=> Actual(403 Forbidden) (Excon::Error::Forbidden)
        from /opt/vagrant/embedded/gems/2.2.16/gems/excon-0.81.0/lib/excon/middlewares/response_parser.rb:12:in `response_call'
        from /opt/vagrant/embedded/gems/2.2.16/gems/excon-0.81.0/lib/excon/connection.rb:446:in `response'
        from /opt/vagrant/embedded/gems/2.2.16/gems/excon-0.81.0/lib/excon/connection.rb:277:in `request'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:130:in `block in request'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:84:in `block in with_connection'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:84:in `synchronize'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:84:in `with_connection'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:130:in `request'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant_cloud-3.0.4/lib/vagrant_cloud/client.rb:192:in `authentication_token_create'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/client/client.rb:75:in `block in login'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/client/client.rb:167:in `with_error_handling'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/client/client.rb:74:in `login'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/util.rb:69:in `client_login'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/plugins/commands/cloud/auth/login.rb:54:in `execute'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/lib/vagrant/cli.rb:67:in `execute'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/lib/vagrant/environment.rb:290:in `cli'
        from /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/bin/vagrant:231:in `<main>'

Hey there,
this is an open issue we are working to resolve. Vagrant cloud auth does not still work · Issue #12393 · hashicorp/vagrant · GitHub

Heya,

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!

1 Like

Thank you, all works now!