[Vagrant] When vagrant up, it stops at “SSH auth method: private key” and times out.

vagrant upDid not start properly

The vagrant upfollowing error occurs when trying to start the VM environment for the first time in a long time

C:\work\centos>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'centos/7' version '2004.01' is up to date...
    default: SSH username: vagrant
==> default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

There seems to be an error in SSH authentication

the reason

It was because I was trying to boot with Hyper-V on.
It was caused by temporarily switching Hyper-V to use Docker, so when I turned it off and restarted, vagrant upit started as if nothing had happened.


Another common cause of the same error seems to be a misconfigured VM network (although I was different).

Read More:

Leave a Reply

Your email address will not be published. Required fields are marked *