Just installed the Apple Silicon Local v6.5.1 and I’m getting a 502 error this is using both site domain and localhost. BTW, this works fine in the Local Beta v6.5.1
Neither the Local or Local Beta v6.5.1 can access the site shell. I get the following error.
Welcome to the club with Ventura problems! I have tried to dig into the site shell issue but without any success. There is a new extended attribute in macOS Ventura called com.apple.provenance but the info is limited. Looks like all apps installed on macOS Ventura gets this. If it’s a part of the Gatekeeper system or some other security measure. Anyway, I tried to delete the attribute from Local app and lightning-services folder but it didn’t help. I had a similar issue with another app in the past where the solution was to delete the com.apple.quarantine attribute because of some component in that app wasn’t signed correctly. This is the command I used but it didn’t help with any of my issues with the site shell and repeating dialog about the network connection. To be continued…
Local 6.5.1 Apple Silicon doesn’t give 502 errors when PHP is 8.0 or 8.0.22. Deleting 8.0.22 and allowing to re-downloading seems to work but naturally I did a few other drastic things and needed to re-import a site.
For clarification it was lightning-services in the Application Support folder. This allows a switch from darwin to darwin-arm64 for the PHP versions. I believe it was these previously installed Intel PHP versions that was/is the issue.
It may be safer to create a new site and use that as an opportunity to download the new PHP version.
I think the complete solution is to delete all the pre-existing PHP resources from the ~/Application Support/Local/lightning-services/php* and let Local re-download them as needed.
This is good to know that it worked, but Local should have done that for you - which is why I was confused originally. Good to know that it didn’t, that gives me a place to start.
Deleting those Intel services and redownloading the Silicon PHPs resolved the 502s for you?
I think the issue with Open Site Shell is that the OS considers the shell script to be an app that may require Full Disk Access or some additional access. If there’s a way to for the Terminal to open the script I think the issue may resolve as Terminal has those privileges.
Dropping the appropriate shell script from ~/Application Support/Local/ssh-entry onto the Terminal app results in the correct response.
Shouldn’t the path in the script now be to the built-in PHP 8.1.9 version? I tried to change the script and lock the file but then Open Shell in Local app didn’t work at all. The script in the ssh-entry folder is checked and re-written every time.