Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
I was just trying to ensure there weren’t any conflicts there @BlackStar1991
The easiest way to get your sites working again is going to be to reimport them. I know you have quite a lot, but since a new, blank site is working normally you can use these steps to reimport and get them working again:
Locate the site files on your machine, and save a copy of them to your desktop. If you click Go to Site Folder under your site name it should take you right to where they are located.
Once you have those copied, completely delete the site from Local
Looking back at your original post, you mentioned deleting the AppData\Roaming\Local\run directory. I may have misunderstood if you deleted those files to try to solve the error, or if the error only occurred after deleting those files (which would be expected). You would have to restore that directory for those sites to run again, or reimport them. If you were seeing the error before deleting that directory, then reimporting would still be the best bet to get things working again.
Yes, problems starts after I remove files from AppData\Roaming\Local\run
Yes, restoring from the Servers version helped… but perhaps you have other suggestions? (A lot of projects in local PC)
If you’re still getting the same “Can’t Connect” error on start, then reimporting is going to be the fastest way to get things working again @BlackStar1991
This folder contains your database data for each site, not disposable cached data, which is why you see MySQL connection issues when trying to start your sites without it, @BlackStar1991. (It’s not safe just to delete it as you’ve been doing because it removes data your sites need to start.)
If you’re looking for a way to save space from having large numbers of sites, you could use Local’s export feature to ‘archive’ a site as a zip file, then store that somewhere else (those exports contain a database dump) and then delete the site in Local (which will remove the ‘run’ folder for just that site).
When you need to work on the site again, you could reimport it by dragging the zip into Local.
@BlackStar1991 If you have a backup of your system, you could find the AppData\Roaming\Local\run folder and restore it.
If you don’t have a system backup, then reimporting your content as @Nick-B described is the next step. This usually restores your site and database files to the state it was at the last time you stopped it.
