502 Bad Gateway, 503 Service Unavailable Errors Galore
-
(BACKGROUND: I launched a website for a client late spring. I went in two days ago to update plugins, WooCommerce to latest version, and to install additional plugins to enhance their WooCommerce reporting capabilities.
Everything went fine after updating. All pages were clickable, and the shop carried an order all the way through purchase.
Yesterday, approximately 27 hours after updating, I received a call from my client saying “The site is down.”
I checked, and when accessing the site’s front or backend, I’d either get 502 Bad Gateway, 503 Service Errors, or the browser would hang waiting for a response.
I called GoDaddy. It’s not them. They did however deactivate all active plugins (except for WooCommerce). The site then could load again. We then reactivated the deactivated ones, and the site is now back up.)So now I’m faced with the task of figuring out which of the few dozen, active plugin(s) the site contains is the offender. I’m told the issue is likely that the offending plugin(s), while creating a connection to another plugin (such as WooCommerce) is not closing the connection when the communication is over with.
Note: I have deactivated (for now) the new plugins that may or may not have been the cause of this issue. I notified the developer, and they have replied strongly suggesting theirs are not the reason this is happening.
How do I move forward? Do I wait for the site to bog down and ultimately crash again to find the culprit(s)? And if that’s the case, where do I start? Do I start with the plugins that have to deal with WooCommerce?
This wasn’t an issue at all before the WooCommerce update. I can’t escape the thought that it’s tied to it in some fashion.
Advice?!
Thanks!
- The topic ‘502 Bad Gateway, 503 Service Unavailable Errors Galore’ is closed to new replies.