Local UI shows cloned sites as running even when stopped

Bugs
,
22

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
23

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

24

… what is ASZ-EF?

25

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
26

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

27

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
28

I recently experienced the same problem on Local where the state continues to be a green-dot (site running) when the site was stopped and any other instances that I subsequently opened did not show the green-dot state.

I received guidance from this post as to where to look for the problem, but it appears that the .json files have changed and the site state is no longer held in sites.json. Fortunately @burt put me on the right track. I resolved my problem as follows:

  1. Close Local App;
  2. Go to the Username\AppData\Roaming\Local\ (on Windows);
  3. Find the file site-statuses.json and back this up;
  4. Edit this file and make sure that all sites are in the ‘halted’ state (which they should be if the Local App is shut down);
  5. Save the file and restart the Local App.

In my case, I found that one of the site instances was not in the halted state, so I changed the state to “halted” and this fixed my problem.

3 Likes
29

Thank you for sharing @Clinton!