HTTP 502 Bad Gateway vs 507 Insufficient Storage
Both HTTP 502 (Bad Gateway) and 507 (Insufficient Storage) 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, 507 means that the server is unable to store the representation needed to complete the request (WebDAV).
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
The server is unable to store the representation needed to complete the request (WebDAV).
When You See It
When the server runs out of disk space during WebDAV operations.
How to Fix
Free up disk space on the server or increase storage capacity.
Key Differences
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
HTTP 507: The server is unable to store the representation needed to complete the request (WebDAV).
You encounter 502 when when Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
You encounter 507 when when the server runs out of disk space during WebDAV operations.
When to Use Which
For 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts. For 507 (Insufficient Storage): Free up disk space on the server or increase storage capacity.