Support the ongoing development of Laravel.io →
Installation Configuration Architecture
Last updated 2 years ago.
0

No one??

Last updated 2 years ago.
0

Mine also does this but after so long it does then boot and connect, I would suggest reboot your machine then give it a few minutes to load everything then try vagrant up again.

Last updated 2 years ago.
0

Been struggling for hours on this one as well. Eventually got it working by turning off my wifi (WTF!?!). This thread helped http://laravel.io/forum/05-27-2014-laravel-homestead-not-connecting-when-wifi-is-enabled. Seems like a hack though, anyone know if there is going to be a proper fix to homestead/vagrant rather than messing with my network settings?

Last updated 2 years ago.
0

I had this problem only today on a brand new computer.

I found that I had to enable Virtualization Technology in the bios.

Last updated 2 years ago.
0

I had the same problem and the solution was to enable Virtualization in the bios like sitesense suggested.

Last updated 2 years ago.
0

I had exact same issues. Well, I get the same issue time to time even now.

Try enabling GUI mode and see what's going on yourself.

config.vm.provider :virtualbox do |vb|
  vb.gui = true
end

mine was somehow staying on the boot loader selection.

Last updated 2 years ago.
0

I experienced a similar issue. Here is what I did.

  • Enabled virtualization in BIOS
  • Ran ssh-add ~/.vagrant.d/insecure_private_key
  • Added config.vm.boot_timeout = 600 to my ~/Homestead/Vagrantfile

It's working fine now.

0

Sign in to participate in this thread!

Eventy

Your banner here too?

tzookb tzookb Joined 9 Feb 2014

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.