What does HTTP 499 mean and how do you fix it?

HTTP 499 is a non-standard Nginx status code logged when the client closes the connection before the server finishes responding. The client almost always hangs up because the backend is too slow, or because a timeout upstream of Nginx (browser, mobile app, load balancer, CDN) is shorter than the server’s processing time.

A burst of 499s in your access log is almost always a backend latency problem, not a client bug. Work through these in order:

1. Profile the slow endpoint. Find the requests that are timing out and fix the underlying query, lock, or external call. Most 499s disappear once response time drops below the client’s patience.
2. Align timeouts across the stack so each layer waits longer than the one below it (client < load balancer < Nginx proxy_read_timeout < backend). Out-of-order timeouts make the upstream layer drop the connection while the backend is still working.
3. Set proxy_ignore_client_abort on for fire-and-forget endpoints like webhooks. Without it, Nginx kills the upstream request the moment the client disconnects and background work can be corrupted.
4. Move long jobs off the request path. Accept the request, return 202, and process asynchronously. The client never waits long enough to time out.