What issue or error are you experiencing?
All sites say either site is not secure or page isn’t working (empty response). Checking keychain access and site are trusted.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
Simply trying to load any site via Local.
- Local Version:
- Operating System (OS) and OS version:
Mac, M1, Ventura 13.4.1(c)
Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
local-logs5.zip (2.9 MB)
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.
If you downgrade to a previous version are you able to access them?
Nope. Ugh, it was working yesterday. I’m at a total loss as to what it could be. I haven’t installed anything new or made any other changes. Any ideas as to what I could do to find the issue and resolve?
If you create a new, blank site in Local can you access that okay? If you can, then you may want to try reimporting the site getting the errors. The steps would look like this:
- 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
- Restart Local/your machine
- Reimport the site back into Local. You can refer here on how to Restore from only Local site files
That worked! Thank you!!
Any ideas what may have caused this? It seemed to affect all sites (at least all I tested, maybe 8 random sites). Just curious if it was something I may have done that I could avoid in the future.
We aren’t 100% certain as to the root cause. We’ve seen some similar behavior with updates but it hasn’t been unique to a specific OS or workflow. We’re doing some digging in our end to see how we might be able to prevent this for future releases. Sorry for the extra work around for now but keep us posted if you hit any other snags!