Treat the response as a symptom
A 502 response indicates a gateway-related failure path, but the visible status alone does not identify the root cause. Cloudways provides troubleshooting guidance that should be applied to the actual application and configuration. Record the affected URL, time and whether the problem is consistent or intermittent. Avoid jumping directly to a server upgrade or broad restart because those actions can change evidence without explaining why the failure occurred.
Diagnose the scope of the error
Check whether the issue affects one application, one function or several applications sharing infrastructure, using bounded read-only observations. A fictional agency may find that public pages work while a resource-heavy administrative action fails. That distinction is useful for diagnosis. Keep private request data and credentials out of the report, and do not repeatedly trigger a costly or state-changing operation merely to reproduce an error that is already documented.
Connect the timing to recent changes
Review the last accepted state and any deployment, import, configuration or traffic change around the incident. Correlation is a lead, not proof. Use available resource and application evidence to narrow the next supported check. If the result of an earlier operation is unknown, reconcile its identity and receipt before initiating a replacement. A chain of blind retries can create additional problems while leaving the original failure unexplained.
Escalate with an actionable brief
Provide support with the exact symptom, relevant timestamps, affected scope and safe checks already performed. State what remains unknown instead of claiming that the host or a plugin is definitely at fault. Keep any authorized recovery step tied to its verified target and data consequences. The aim is to restore the required service with an understood cause or bounded uncertainty, not to make a status code disappear through unrelated changes.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Cloudways 502 diagnosis — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- Cloudways support tiers and explicit exclusions — Merchant documentation · cloudways.com · Merchant-controlled · checked 2026-09-21