Local by Flywheel updated automatically this morning and now all of my local sites are inaccessible, they say “Error!
Container is missing. You will need to restore this site from a backup or previous export.”
From searching here I think I need to follow the steps outlined here:
So I went through the steps described with one site and got up to this point:
Rename all of the folders in your Local Sites folder to something like SITE-backup
If the site still exists in Local with a “Container Missing” error, delete it.
Create new sites for each using the existing domains and paths. So, if it was site before, you’ll use site again
Browse back to the Local Sites folder and delete the newly created site folder and rename SITE-backup back to site. This is done because you can’t create sites over site folders that already exist.
For step 4, I had to Stop the site in Local before I coudl delete all the files as Windows gave me an error message saying error.log was in use so it couldn’t remove the directory. So I stopped the site, removed it, renamed the -backup to the original site name, then tried to Start the site but the site just spins forever and never loads.
I’ve tried restarting the local machine but this doesn’t help.
Is there a way to disable auto updates? I don’t have the time to go through 15 sites today, so I’m thinking of doing an entire System Restore to yesterday when everything worked fine.
@clay there are some sites that I haven’t worked on in a while which are refusing to start. When I click Start it just says “Starting…” forever. This is happening to 16 out of 19 sites!!! Only 3 work. Is there a forced “Restore site” option I can enable somehow?
I’ve tried updating to 2.2.4 and rebooting multiple times but I still have the same issue.
I’ve been through the steps here - How can I restore a site from a Local site folder? even though there was no container missing message. It didn’t work, I got a bad gateway error. In the end I’ve had to create a new site, resync the database and then replace all the files with the live site files. This is quite time consuming and its the second time this bug has happened. If it happens again I’ll have to switch back to XAMPP or Desktop Server.