Hi there, @ll_kyle - welcome to the Local community! 
Have you reviewed this thread?
It sounds like there is a known fix - the bug is due to erroneous data in your sites.json file.
You can follow along in this thread on how to fix it.
It involves opening that file, and deleting the “status: running” line for the sites affected.
The Local engineering team is reviewing this! 
Sam