0 Best Reply Awards

  • Member Since 1 Year Ago
  • 60 Lessons Completed
  • 0 Favorites

5th December, 2016

scott0 started a new conversation Homestead Hangs At SSH Auth Method: Private Key • 1 year ago

I can't seem to get Homestead running. It hangs at SSH auth method: private key.

The Homestead VM starts. I can go to VirtualBox and open the terminal window and login with vagrant:vagrant.

I can't vagrant ssh, ssh [email protected]:2204 or ssh [email protected] -p 2204.

None of my folders show up in the VM, but the VirtualBox says they are mapped.

Every time I vagrant up, I get:

vagrant up Bringing machine 'homestead-7' up with 'virtualbox' provider... ==> homestead-7: Checking if box 'laravel/homestead' is up to date... ==> homestead-7: Clearing any previously set forwarded ports... ==> homestead-7: Fixed port collision for 80 => 8000. Now on port 2200. ==> homestead-7: Fixed port collision for 443 => 44300. Now on port 2201. ==> homestead-7: Fixed port collision for 3306 => 33060. Now on port 2202. ==> homestead-7: Fixed port collision for 5432 => 54320. Now on port 2203. ==> homestead-7: Fixed port collision for 22 => 2222. Now on port 2204. ==> homestead-7: Clearing any previously set network interfaces... ==> homestead-7: Preparing network interfaces based on configuration... homestead-7: Adapter 1: nat homestead-7: Adapter 2: hostonly ==> homestead-7: Forwarding ports... homestead-7: 80 (guest) => 2200 (host) (adapter 1) homestead-7: 443 (guest) => 2201 (host) (adapter 1) homestead-7: 3306 (guest) => 2202 (host) (adapter 1) homestead-7: 5432 (guest) => 2203 (host) (adapter 1) homestead-7: 22 (guest) => 2204 (host) (adapter 1) ==> homestead-7: Running 'pre-boot' VM customizations... ==> homestead-7: Booting VM... ==> homestead-7: Waiting for machine to boot. This may take a few minutes... homestead-7: SSH address: homestead-7: SSH username: vagrant homestead-7: 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.

I replaced the homestead insecure private key with my key on my box. I see a lot of people get Warning: Connection timeout. Retrying..., but I don't get that far.

I'm on a mac 10.11.6

Any help would be greatly appreciated!

Edit Your Profile

Want to change your profile photo? We pull from