@Tommy999 – I’ve merged your topic into this one since it seems like the same issue.
Having the four sites active is likely not an issue since they aren’t all receiving requests at the same time. Additionally, I guessing that these other sites aren’t actually started – they just appear to be within the Local UI.
I was able to sort of replicate (ie, I broke Local, but I don’t know exactly what I did to break it ). I’ll keep tinkering to find reliable reproduction steps and file a bug with the Local team!
@burt I looked in my local sites json file (of the affected site(s) ) and don’t see any of those settings? Is there another json file that I may be missing??
@fourwhitesocks The file that I referred to is (on Windows) %AppData%\Roaming\Local\sites.json
Make sure that you’ve closed Local, and made a backup as well before doing anything with that file. You’ll want to have an editor that can prettify the JSON to help identify anything that doesn’t look like it belongs in the settings for the site experiencing the incorrect status.
Of course, the safest thing is to wait and see if the developers can identify and fix the issue, hopefully cleaning up any existing config problems.
I know that this was reported a while ago and a fix still isn’t here. In terms of streamlining communication, I’ve moved this topic from the “support” category to the actual “bug” category so that it can be up-voted.
Thanks for testing out Local v6.3.0 so quickly! We believe the cloned site bug (this topic) is resolved for newly cloned sites, but there might be some lingering data on your Local machine causing this to still be an issue.
Couple of questions:
I’m assuming your site ASZ-EF was cloned prior to v6.3.0?
If you open %APPDATA%/Roaming/Local/sites.json on your machine and Ctrl+F for “ASZ-EF”, do you see a line under the site that looks like this?
status:“running”
I was able to resolve the issue on an old site on my machine by deleting that line (and the comma on the line above it) and restarting Local. Hope this helps!