Local doesn't work after update


#1

Local is not starting anymore. It’s hanging on “Starting Local Machine”. And I get the following error message: "Uh oh, we ran into a hiccup when trying to start the Local Machine.

It worked fine yesterday. Did the update today. Then started Local and on my site I got the message to update the environment. Which I did and cloned the site. Then I got the “502 bad gateway” error on both the original and the cloned site.

Then I reinstalled Virtual Box and tried again but now I’m stuck on “Starting Local Machine”.

This is the logfile from today: local-by-flywheel.log (28.7 KB)


Can't retrieve the requested docker image
#2

Hi @petervdeynde,

It looks like the drivers for VirtualBox may’ve been reset. Please try the steps here: How can I manually update VirtualBox?

If the issue persists, please see How can I forcefully restart the Local by Flywheel VM?


#3

Thanks for your reply @clay,

You can consider this solved. Got it working.


#4

What did you do to resolve the problem?! Mine broke 2-3 days ago and I am stuck at starting the local machine. I updated local to 2.4.0 then updated to the latest version of VirtualBox but no luck yet.


#5

Hey @ltbaxter,

I had to remove Virtual Box and then also manually remove the folders in Program Files. And then everything worked again.

But I’m allready having troubles again now. Getting the following error: “Local detected invalid Docker machine TLS certificates and is fxing them now”. And also : “uh oh , this site id was not found” or something like that.


#6

Hi @clay,

I’m back to where I was again.

Tried restarting the VM again. And tried reïnstalling everything again. It doesn’t work anymore.

Maybe the log file will be of any help: local-by-flywheel.log (686.9 KB)


#7

Been trying again this morning. I’ve restarted the VM a couple of times, reïnstalled the whole thing, Local and Virtual Box. Tried installing the latest update. Nothing works guys.

I would really like to get this working again, as I have sites that need to get finished.


#8

Am also in the same problem, I have tried directions given to petervdeynde but in vain. Also waiting to get the solution. I just installed and reinstalled the two yesterday and today respectively. Here is my log file local-by-flywheel.log (97.9 KB)


#9

Here is what FIXED the problem for me. Not sure if it will help others here, but I was facing a problem where the VM would never start. Everything worked fine the very first time I installed and launched, but after a system reboot the problem showed up and no amount of reinstalls or reboots helped. A lot of research showed the most common cause of this problem is that there is another process on my system that is trying to look inside and see what’s going on, and for security reasons Local doesn’t allow that.

Turned out that Trusteer Rapport was the culprit. I removed that and a Cisco VPN adapter, both of which I was no longer using. On reboot, all problems were gone. It’s frustrating that the log gave no indication of what the root problem was. The items reporting the error and/or the last successful entry in the log had nothing to do with Trusteer. But several other users I found on Google reported success upon removing it. Good luck all!


#10

Thank you! Rapport was the cause for me too.


#11

Thanks a lot !!! I was desperate. In fiirst I turn off Trusteer Rapport, but It was not enough.
I completely uninstalled it and my local came back to work.