-
Notifications
You must be signed in to change notification settings - Fork 26
Open
Description
Hi, tried vagrant up on mac, it' didn't come up.
Vagrant version : Vagrant 2.1.1
Virtualbox version: 5.2.12 r122591
node1: SSH address: 127.0.0.1:2222
node1: SSH username: vagrant
node1: SSH auth method: private key
node1: Warning: Connection reset. Retrying...
node1: Warning: Remote connection disconnect. Retrying...
node1: Warning: Connection reset. Retrying...
node1: Warning: Remote connection disconnect. Retrying...
node1: Warning: Connection reset. Retrying...
node1: Warning: Remote connection disconnect. Retrying...
node1: Warning: Connection reset. Retrying...
node1: Warning: Remote connection disconnect. Retrying...
node1: Warning: Connection reset. Retrying...
node1: Warning: Remote connection disconnect. Retrying...
node1: Warning: Connection reset. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying..
...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
node1: Warning: Authentication failure. Retrying...
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.`
It fails with authentication failure.
I'm able to create vagrant box and do vagrant ssh without explicit giving ssh keys.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels