I’m having an issue where every time I try to pull from Kinsta to local with DevKinsta, it’s showing a 502 Bad Gateway error when I try to open the site. I’ve also noticed it’s not showing the screenshot of the site anymore in DevKinsta.
Can you please close both Docker and DevKinsta entirely, start DevKinsta again and then send me a copy of your main.log file via DM? You can find it by clicking on the question mark icon at the bottom left corner of DevKinsta and then on Reveal log file in File Manager.
We’d like to give a look at it and help you find the culprit.
Okay great, this means that PHP is working fine generally speaking. Let’s test some commands via WP CLI to see how your site responds, I feel there might be some syntax error somewhere.
Please follow the first and the second step of this guide.
Do not run the command used in step number 3, but instead use wp option get home
Does the terminal return any error or it only returns your site domain?
Thank you for your reply and updates!
As I can understand, your “sage” theme requires/uses “Advanced Custom Fields” plugin and, you didn’t get 502 error when you activated “twentytwentytwo” theme because this default WP theme does not use/require that plugin (even after the plugin has been re-activated).
So far we suspect this 502 error actually seems to be from that “Advanced Custom Fields pro” plugin alone (as all other plugins have been deactivated), and this does not seem to be DevKinsta application related issue either.
This plugin does not seem to be a free plugin but a paid/premium/licensed one. Did you buy/purchase it from the plugin’s author/developer perhaps?
If that so, you may want to reach out to that plugin’s support team and see if they know something about it and how to resolve that 502 bad gateway (cause without that plugin re-enabled, you didn’t get 502 error?), as you also previously mentioned:
Okay, after re-activating ACF Pro I’m seeing the 502 again.
Also, I would check what PHP version is currently used for this local site in DevKinsta?
I’m wondering if it will work fine with different PHP version (still unsure though if this is the case or if there’s something else from that plugin itself).
Let’s say if it’s set with PHP 8.0 or PHP 8.1, may want to try to switch the PHP version for this site to 7.4 (and see if that works?).
From your DevKinsta , click that Site name from the list, then click the wrench icon on the left. After that, on that “Site configurations” page, you can click on the “PHP Version” and click the pencil icon to switch the version, and re-check your site. If it’s still showing 502 error, then I would suggest to reach out to that plugin’s support team for further assistance.
So changing PHP back to 7.4 seems to have fixed it. But why? I had to update to 8 to push back to kinsta and it worked fine before the last update. Also, how can I push back to Kinsta if I can’t update to PHP 8?