Error guide / 502 Bad Gateway

502 Bad Gateway: The Server Got a Bad Response

502 Bad Gateway appears when the server that takes your request reaches out to another server and gets a broken response back. In plain terms, a middleman such as a proxy or CDN could not get through to the main server. The site is down, but the problem is often temporary.

What causes it

The usual culprit is an overloaded or crashed backend: a stuck PHP process, a glitch after an update, a short traffic spike, or misconfigured proxy or CDN settings.

How to fix it

1. Refresh the page after a minute or two; many 502s clear on their own after a brief glitch.
2. Open the site from another device or network to rule out your browser.
3. Clear your browser cache and the CDN cache (for example in Cloudflare) if one is enabled.
4. Check the error log; a 502 is often caused by a PHP process that crashed or timed out.
5. Restart the app or PHP pool if you have access, or ask support to do it.
6. If the error is constant, contact your host, as the server itself may be overloaded.

Related errors

• 403 Forbidden 403 Forbidden: Access to This Page Is Denied
• 404 Not Found 404 Error: The Page Could Not Be Found
• 500 Internal Server Error 500 Internal Server Error: Something Broke on the Server
• 503 Service Unavailable 503 Service Unavailable: The Site Is Temporarily Down