Local UI shows cloned sites as running even when stopped

@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.

Nice work zeroing in on this issue @burt !

I was able to sort of replicate (ie, I broke Local, but I don’t know exactly what I did to break it :smiley: ). I’ll keep tinkering to find reliable reproduction steps and file a bug with the Local team!

Happy to help! Glad that you’ve been able to narrow things down a little for the devs.

1 Like

I second that too!

@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??

This is the json file I’m looking in: http://prntscr.com/14rf520

Thank you!

@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.

1 Like

@burt thank you very much; I think I will take your advice and wait; it doesn’t seem to hurt anything it just kinda bugs me :wink: !

1 Like

I wanted to chip in by saying I’m experiencing this issue, too, on mac. Updating to the latest Local version does not resolve the issue.

Gosh I hope they get it on the next update then :slight_smile:

Local 6.1.0 + 5452 has this issue. I included a screenshot in this thread: Local 6.1.0 defect: Site shows green “running” state when the site is not actually running

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

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.

3 Likes

Local version: 6.3.0+5756
OS: Windows 10 Pro

The cloned sites still shows as active.

Hi Chris,

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:

  1. I’m assuming your site ASZ-EF was cloned prior to v6.3.0?
  2. 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!

Thanks,
Austin

2 Likes

Hi Austin,

1, Yes, I did before v6.3.0.
2, I found the status:“running” text in the document.
After delete that parameter the problem has been solved.

Thanks,
Chris

… what is ASZ-EF?

That is the name of @chrisdark86’s site having the issue, @fourwhitesocks. Just replace “ASZ-EF” with the site that is impacted in your environment.

1 Like

Oh ok gosh; guess I should have known that no wonder I didn’t recognize it … lol :confused:
Thank you!

Mac Fix

  1. Close Local App
  2. Open ~/Library/Application Support/Local/sites.json with text editor (take backup!)
  3. Remove strings with text editors search and replace tool: “status”:“running”,
  4. Save file
  5. Open Local and now you have 0 sites running
  6. Enjoy :slight_smile:
1 Like