I just updated local to 2.4.1 but since doing that Local won’t start. It just stops at ‘Starting Local Machine…’ and does nothing. I’ve attached my log file, running MacOS High Sierra
I’ve tried opening Virtual Box and shutting off the local machine, have restarted my computer, but nothing seems to work. When I check the log the last line says ‘waiting for an IP’.
Any help would be greatly appreciated!
local-by-flywheel.log (167.9 KB)
Running High Sierra also and am getting a different error/loop after the 2.4.1 update.
Local will start up then will get in a loop “Checking System” and “Regenerating Docker Machine TLS Certificates”
If you try to select a site between loops I get a “The requested site ID does not exist in Local” error.
I have the exact same problem now.
Same here. Everything was fine until the 2.4.1 update. Now Local is completely dead.
Dark mode was nice, but someone seems to have turned ALL the lights off.
If you’re experiencing this issue, please try the steps here: How can I forcefully restart the Local by Flywheel VM?
Thanks for the reply! As mentioned initially I have restarted the Local by Flywheel VM a couple of times now and still with no luck. The ACPI Shutdown command doesn’t work so I have to select Power Off to get it to shutdown properly.
When I start Local I just see this:
Note that my log file is attached in the original post.
Got it, thanks for the clarification!
Please try the following:
- Quit Local if it’s running
- Open Terminal (or your terminal of choice such as iTerm)
- Run the following command:
"/Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine" -D start local-by-flywheel
- Copy and paste the output in your reply here
Thanks for that, please find attached the full output.
flywheel-output.log (23.1 KB)
Just an update, have updated Local to 2.4.2 and the issue is still there unfortunately.
Hey guys any update here? It’s been almost a week that I’ve been unable to work on local sites.
After update to 2.4.2 on Windows 10, Local is starting only the first time (although much slower than before). If I turn it off, it doesn’t start again at all until I reboot the computer.
If I open virtualbox, it says that Local is not running, so I can’t restart it, and if I only start it I get some shell window, but no matter on or off, Local doesn’t start again until I reboot the computer.
Another thing that is changed with update is that no sites are running on Local start. Before update, what was running when turned off, was started when Local started. Now all sites are off on start. Why?