4xx Client error · unofficial (nginx)

499 Client Closed Request

The client closed the connection before the server responded (nginx).

What 499 means

Not a standard code: nginx logs it when the client (or an upstream load balancer) gives up waiting. The client never sees it; it shows in server logs.

Common causes

The client's timeout is shorter than the server's response time.
Users navigating away or cancelling requests.

How to fix it

If you're calling an API

Increase your client timeout if the operation is legitimately slow.

If you run the server

Speed up slow endpoints or make them asynchronous (202 + polling).

Should you retry?

Yes, with a longer timeout.

Example response

HTTP

HTTP/1.1 499 Client Closed Request
Content-Type: application/problem+json

{
  "type": "about:blank",
  "title": "Client Closed Request",
  "status": 499,
  "detail": "The client closed the connection before the server responded (nginx)."
}

Defined in: nginx (non-standard). 499 is a client error: change the request before retrying.

Debugging an API call? Convert your request with the cURL converter, check the response with the JSON formatter, or see whether the API is down on its status page.

HTTP 499 FAQ

What does HTTP 499 mean?

499 Client Closed Request: The client closed the connection before the server responded (nginx). Not a standard code: nginx logs it when the client (or an upstream load balancer) gives up waiting. The client never sees it; it shows in server logs.

Is 499 a client or server error?

It's a client error (4xx): something about the request needs to change before it can succeed.

How do I fix a 499 error?

Increase your client timeout if the operation is legitimately slow.

Should I retry after a 499?

Yes, with a longer timeout.

Other 4xx status codes

All HTTP status codes