Vagrant: 1.9.1 default: Warning: Authentication failure. Retrying...

[nootfly]

Vagrant version

Vagrant 1.9.1

Host operating system

macOs 10.12.2

Guest operating system

ubuntu/trusty64

Vagrantfile

Vagrant.configure("2") do |config|

  config.vm.box = "ubuntu/trusty64"

  config.vm.synced_folder "myFiles/", "/home/vagrant/shared"

end

Debug output

==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...

Expected behavior

I should login the VM.

Actual behavior

I cannot login.

Steps to reproduce

1. I switch to another network
2. vagrant up

[FibreFoX]

Maybe related to https://github.com/mitchellh/vagrant/issues/8157

[nootfly]

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.

~/vagrant/myVM
☺ vagrant ssh (ruby-2.3.0)
[email protected]'s password:

it requires a password.

[kikitux]

@nootfly can you test with box hashicorp/precise64 ?

We only provide the boxes under hashicorp org in atlas.

If this is an issue with the box, you should try to reach canonical

[lsoumille]

Same issue here on Ubuntu 16.04 host, after I've tried to launch a packaged ubuntu/trusty64 box. I think the problem isn't box related because every other packaged boxes doesn't work.

[FibreFoX]

I suspect something is up with virtualbox ... similar problems on https://github.com/mitchellh/vagrant/issues/8157 just with windows host. Seems not box related :(

[mauricioabreu]

I don't think it is related to the box as @FibreFoX said above.
I use centos/7 box and it happens to me. After fixing this (restarting network, restarting macOS and other random attempts to fix this) it returns to happen.

[kikitux]

Hi, if you can share a debug log when this happens, that will help to move this faster

[sully7]

Same problem on Windows 10 as well.

[richard-scott]

I get this on an Ubuntu 16.04 host starting a bento/debian VM in VirtualBox... Funny thing is that if I open a new terminal session while the main one is not connecting I can run 'vagrant ssh' and get I to the VM.

[rubenmeza]

Solved http://www.gisremotesensing.com/2016/06/solution-vagrant-box-authentication.html

[FibreFoX]

@rmezar You mean the used box is the culprit? I personally had a different source of problem, but I am surprised that the authorized_keys of the BOX should be responsible for this ...

[richard-scott]

My problems were fixed by running this before "vagrant up":

export SSH_AUTH_SOCK=""

For some reason the ssh-agent was causing a conflict.

[chrisroberts]

Hey there,

I am going to close this due to lack of response. If this is still occurring, please open a _new issue_ and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks! 😄

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.