root@hack3rs:/srv/www$ curl -i /504/
HTTP/1.1 504 Gateway Timeout
A gateway or proxy timed out waiting for an upstream server.
status-summary.log
HTTP 504 Gateway Timeout
The request path reached a gateway, but the upstream service took too long to respond within timeout limits.
Compare end-to-end latency with timeout settings at each layer before increasing limits globally.
likely-causes.lst
- $Upstream service is slow due to load or long-running queries.
- $Network latency or packet loss between proxy and backend.
- $Timeouts are shorter than normal response time under peak load.
- $Thread/worker pool starvation delaying request processing.
recovery-steps.md
- Inspect upstream latency metrics and slow query traces.
- Review timeout values on CDN, proxy, and app server layers.
- Optimize backend processing or add caching where appropriate.
- Scale workers/capacity and monitor queue depth during incidents.
quick-actions.sh
ops-note.txt
Use these pages for debugging and user guidance. In production, configure your host or reverse proxy to return the matching HTTP status code for the route (especially for 504 and 404/500 responses) rather than serving a 200 with error-themed content.