Hi - I've worked with Vagrant before successfully but on this new box it doesn't want to go...
3 thoughts on “Can’t get Vagrant to ssh on new laptop”
Here’s the output in the terminal window
C:\Users\User\Dropbox\My Work\Vagrant\Omlya>vagrant up
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Checking if box ‘jadesystems/rails-5-2’ is up to date…
==> default: Clearing any previously set forwarded ports…
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 3000 (guest) => 3000 (host) (adapter 1)
default: 4000 (guest) => 4000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running ‘pre-boot’ VM customizations…
==> 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: password
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.
C:\Users\User\Dropbox\My Work\Vagrant\Omlya>vagrant status
Current machine states:
default running (virtualbox)
The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.
C:\Users\User\Dropbox\My Work\Vagrant\Omlya>vagrant ssh
==> default: The machine you’re attempting to SSH into is configured to use
==> default: password-based authentication. Vagrant can’t script entering the
==> default: password for you. If you’re prompted for a password, please enter
==> default: the same password you have configured in the Vagrantfile.
ssh_exchange_identification: read: Connection reset by peer
Here’s the output in the terminal window
C:\Users\User\Dropbox\My Work\Vagrant\Omlya>vagrant up
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Checking if box ‘jadesystems/rails-5-2’ is up to date…
==> default: Clearing any previously set forwarded ports…
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 3000 (guest) => 3000 (host) (adapter 1)
default: 4000 (guest) => 4000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running ‘pre-boot’ VM customizations…
==> 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: password
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.
C:\Users\User\Dropbox\My Work\Vagrant\Omlya>vagrant status
Current machine states:
default running (virtualbox)
The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.
C:\Users\User\Dropbox\My Work\Vagrant\Omlya>vagrant ssh
==> default: The machine you’re attempting to SSH into is configured to use
==> default: password-based authentication. Vagrant can’t script entering the
==> default: password for you. If you’re prompted for a password, please enter
==> default: the same password you have configured in the Vagrantfile.
ssh_exchange_identification: read: Connection reset by peer
The computer is an hp EliteBook 8440p – windows 7 sp1 64 bit – 4 GB ram – cpu is an Intel Core I7 M 640 @ 2.80 ghz
What were you using previously?