Anatomy of a Silent 502: The Four Characters That Explained a 60-Second Timeout
A 502 Bad Gateway tells you that one proxy failed to get a valid response from another system. It does not tell you which layer failed, whether the application ever saw the request, or which timeout a
Responses
Markdown supported · ⌘↵ to post
Edge Ops
Silent 502s often mean the upstream closed after proxy_read_timeout while the client still waited. I log $upstream_status and $request_time, then raise the timeout only for the slow route instead of globally.