You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 2001:420:2852:2011:3c93:dc10:a989:dd0a:22
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.
The text was updated successfully, but these errors were encountered:
RashmiRamanna
changed the title
Creation of vm is successful. but Vagrant up doesn't throws this timeout error. Increasing the timeout doesn't help
Creation of vm is successful. but Vagrant up throws this timeout error. Increasing the timeout doesn't help
Jul 22, 2018
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 2001:420:2852:2011:3c93:dc10:a989:dd0a:22
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.
The text was updated successfully, but these errors were encountered: