Skip to the content

499 Client Closed Request

An entry in the nginx access log: the client closed the connection before nginx could send its response. Nobody ever receives a 499.

Class
Unofficial codes. Not in the IANA registry. These are made up by one piece of software and mean nothing outside it, but they turn up in logs and on error pages often enough.
Used by
nginx

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When the other side gives up while nginx is still waiting for the application behind it: a visitor closes the tab or clicks on, an app is put in the background, or a load balancer or script in front has a shorter timeout than the request takes.

What to do about it

A few are normal on any busy site.

A lot of them for the same address point at a slow backend: people or programs stopped waiting. Compare the request time in the log with the timeouts of whatever calls nginx. If a load balancer in front gives up after 60 seconds, a request that takes 61 is a 499 here and a 504 there. Speed the request up, or raise the timeout of the caller.

Not to be confused with

504 Gateway TimeoutHere it is nginx that gave up waiting, for the backend.
408 Request TimeoutThe server gave up waiting for the request of the client.
444 No ResponseHere nginx closed the connection itself, on purpose.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12