-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
vagrant provision crashes in the middle of many Sites (vhosts) because Apache can't bind to port 80 #1948
Comments
I'm encountering the same issue on an Intel Mac using the VirtualBox provider. |
I'm also having the same issue on an Intel Windows using the VirtualBox provider. |
I am only using Apache for all my websites. Here's a workaround that seems to be working, in case anyone else needs it:
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Versions
6c474ca51c6c8662c71c10cec11a6f1dd7a7fb3c
(v15.0.2)Host operating system
MacOS 14.3 (23D56) on Apple M2 Pro
Expected behavior
I have more than 100 vhosts on my Homestead.yaml.
After upgrading to the new box homestead (not -arm), did a full provision and expected the provision to end.
Actual behavior
The
vagrant provision
fails in different places after consecutive runs.After provisioning the last "Site" before crashing, the
vagrant provision
outputs:I then login via ssh with
vagrant ssh
and runjournalctl -xeu apache2.service
outputing (in the end):It seems the problem lies in the ipv4 (or ipv6) version:
Where Apache tries to bind to port 80 but fails.
My suspicion is the fact that on each Site provisioning, Nginx is disabled and then Apache is enabled. But sometimes, Nginx didn't yet release it's port 80 (socket) and Apache fails to bind.
There's not a clear pattern on which Site (vhost) it fails when provisioning. Almost always a different one.
Would it be possible to add an X seconds sleep in between Nginx disable and Apache enable commands while provisioning?
Better yet, is it possible to completely disable Nginx as an installed service as we only use Apache?
Although this is on Mac M2 (Arm), I have colleagues on Intel machines with the same problem.
Our workaround is to place the vhost we need to work on, on top of the Sites list on Homestead.yaml and provision again, hoping it goes past the first one.
The text was updated successfully, but these errors were encountered: