HTTP 502 Bad Gateway vs 530 Site Frozen
Both HTTP 502 (Bad Gateway) and 530 (Site Frozen) belong to the 5xx Server Error category. 502 indicates that the server, acting as a gateway or proxy, received an invalid response from the upstream server. Meanwhile, 530 means that cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
Description
The server, acting as a gateway or proxy, received an invalid response from the upstream server.
When You See It
When Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
How to Fix
Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.
Description
Cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
When You See It
When a site on Pantheon hosting has been frozen due to inactivity.
How to Fix
Reactivate the site on the hosting platform.
Key Differences
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
HTTP 530: Cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
You encounter 502 when when Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
You encounter 530 when when a site on Pantheon hosting has been frozen due to inactivity.
When to Use Which
For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts. For 530 (Site Frozen): Reactivate the site on the hosting platform.