Hi @royby (and @lolobomac if this applies to you) - there are two separate issues at play here, and I want to make sure I explain them appropriately.
With the update to Local v6.5.1, we updated our PHP versions and recompiled them on the latest MacOS. This caused users to see a 502 error on their existing sites due to a configuration mismatch. Deleting the
lightning-services directory was a temporary workaround, and the core issue has been patched and released in Local v6.5.2.
Users on macOS Mojave or lower continued to see issues with Local sites on the latest build, v6.5.2. This is because the PHP versions compiled and released in the latest version are no longer compatible with these older versions of macOS. This is somewhat expected but was not found during QA as we don’t have the capacity to test on these older versions.
In order to keep Local secure and continue to prioritize new features, we are unable to continue supporting Local for operating systems that are no longer supported by their creators. After Local v6.5, we cannot ensure compatibility below macOS Catalina.
Unfortunately, Apple stopped active support for macOS Mojave in 2019 outside of minor security updates. We’d strongly encourage you to update to a newer version of macOS to ensure security on your machine and to maintain compatibility with modern applications and technologies.
Users who must remain on macOS Mojave or lower can install Local v6.4.3 from our releases page.
More for our team to continue learning - based on the data we have, a very small portion of the Local user base is still running on Mojave. Is there a reason you’re unable to update to a newer version?