Support the ongoing development of Laravel.io →
posted 10 years ago
Configuration

I'm having a weird issue I've only started to experience recently. When running vagrant up on Homestead it starts as expected but then dies out when trying to connect.

    ...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. 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.

The only way I have been able to get it through is to disable the wifi on my MacBook Air. Very odd.

It seems others have been experiencing this as well, but with no solid solutions:

I would go forward with the wifi off, but can't because the project depends on Google fonts and other CDN-based assets.

Current machine setup:

  • MacBook Air
  • OS X 10.9.4 (Mavericks)
  • Vagrant 1.6.3
  • VirtualBox 4.3.14 r95030

Anyone else experiencing this? Any solutions?

Last updated 3 years ago.
0

Similar setup. Similar problems. When I tried starting the homestead box with Virtual Box GUI running, it seems to get hung up on a homestead login.

Turning WIFI off did get homestead going but developing with WIFI off isn't exactly ideal.

I am currently on the road so it must have something to do with the unfamiliar WIFI connection I am using.

Last updated 3 years ago.
0

I have exactly the same issue, I've seen a lot of "fixes" by googling around, but none has solved my problem.

Last updated 3 years ago.
0

Were you guys able to solve this? I can't connect from my office's wifi, but if I connecto to my iPhone's hotspot everything works fine. I've been finding more and more people with this problem, but most of the fixes are related to PC's virtualization, and have nothing to do with mac. I have the same setup as gstjohn, except I'm on a MBP retina.

Last updated 3 years ago.
0

i have same problem

Last updated 3 years ago.
0

Make sure that there isn't an IP address confliction with your wifi and the VBox. I usually set mind to 10.8.0.23 to be sure its not conflicting with the local network.

Last updated 3 years ago.
0

I updated my homestead box to ver. 0.1.8 and it seems to be fixed now.

Last updated 3 years ago.
0

Sign in to participate in this thread!

PHPverse

Your banner here too?

gstjohn gstjohn Joined 21 May 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.

© 2025 Laravel.io - All rights reserved.