Can confirm that this worked and I was able to push to WP Engine!
2 Likes
Attempting to do this now.
…hanging on “Starting up Site Services” for several minutes.
Scrapped it and started over.
I’m on the site dashboard, and the WordPress Version is showing the spinner nonstop.
Quit and relaunched Local. WordPress Version is still showing the spinner.
Started the site, tried navigating to WP Admin, page shows “502 Bad Gateway.”
Tried uninstalling Local Beta and starting over completely. Everything seems to work correctly, but the WordPress Version on the site dashboard perpetually shows a spinner. When I navigate to WP Admin, I get “502 Bad Gateway.”
I tried to Trust the SSL certificate and I get the message, “Heads up, we ran into a problem trusting the local ssl certificate.” Updated my keychain, now SSL shows trusted. Still getting “502 Bad Gateway.”
Tried downgrading php version from 8.2.8 => 8.1.9. Not getting 502 anymore. Am able to navigate to WP Admin. Note: I had recently noticed a message on WP Engine Site Overview page recommending to upgrade to php 8.2. In Local, the closest option was 8.2.8.
This seems to have fixed my problem.
I was able to push to WP Engine!
Question: I don’t have a pressing need to push to WP Engine right now, so should I continue to use Local 7.1.0 +6396 for now? Or is it okay to begin using Local Beta 7.1.1?
Using the Local Beta 7.1.1 solved my issue “Local couldn’t load the file list!”.
Thanks
2 Likes
Thanks to everyone for confirming the fix! Glad to hear it is working. We will work on getting this (and one more Connect fix for file permissions on private folders, like .git) out to stable ASAP.
@wpxdm if you don’t have an urgent need to push, I’d recommend using stable Local v7.1.0. The upgrade to the newer Local with the fix will be out soon.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.