Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Hello,
I’ve been using this awesome plugin for about 7 months now, and until recently had no issues. Ever since I updated to the latest version of WordPress, however, I am getting “502 Bad Gateway Error” every other time I try to update a page or post that uses this plugin (in combination with Site Origin widgets). It’s especially prevalent when I make more than 2-3 changes at a time. I’ve checked with my hosting service (GoDaddy), disabled or deleted new plugins that might be causing the issue, and deactivated/reactivated both Page Builder and the Site Origin widgets bundle. Is there any way to fix whatever is causing these errors?
Hi Grace,
This error typically is an issue with your service provider. To clarify, is this issue only present when SiteOrigin Page Builder is enabled? Have you tried a full plugin conflict test? If not;
Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Hi Alex,
Thank you for the tips! I spent several hours on the phone with my hosting service, so I’m pretty sure it’s not on their end (that’s where I started). I took your advice for testing all of the other plugins, and it appears that the conflict is with JetPack by WordPress. The error only occurred after re-activating that plugin (and configuring it). I know that there are a number of other plugins I can use to try to recreate some of the functionality of that plugin, but is it possible to find out what the conflict is and fix it? I also purchased SiteOrigin Premium yesterday and installed it in hopes that it might iron out some of the problems, so please let me know if I need to change how I’m communicating with the support team.
Thank you!
Hi Grace,
Ideally, we would prefer if this thread was moved over to email as it’ll allow us to respond quicker. Please email us at [email protected]. Please reference this thread with a link for future reference.
Please note that SiteOrigin Premium is required to use Premium support. If you do not have SiteOrigin Premium we won’t be able to help you through this email. :( (this message isn’t intended for you Grace)
Please enable WP_DEBUG as that will allow us to (hopefully) see an error message. This will require that you edit wp-config.php over FTP. This can be quite tricky so you may need to ask your hosting provider how to set up FTP with your website if you’re not sure how. Once you’ve enabled WP_DEBUG, please try replicating it. If it worked you should see an error message. Please send me that.
If no error shows, please try enabling WP_DEBUG_LOG. Then try replicating the issue again, then check the log (it’ll be inside your wp-content directory). If the file is there, please send me the contents.
Thank you, Alex!! I will switch over and very much appreciate your help!