HTTP 408 Request Timeout

Status code 408 · Class 4xx

HTTP

Request Timeout

Also searched as: error 408, HTTP 408, 408 request timeout

HTTP request chain from browser through CDN and proxy to the origin server
HTTP errors: find which hop in the request chain failed and read its logs.

What it means

The server closed the connection because it did not receive the complete request in the time it was willing to wait. It usually means a slow or interrupted upload or a stalled connection between you and the server, not a slow server response.

Applies to: All browsers, nginx, Apache, IIS

How to fix HTTP 408 Request Timeout

  1. Reload the page or retry the upload
  2. Use a more stable connection and avoid uploading on weak mobile signal
  3. Disable VPN or proxy that may slow the upload
  4. Split very large uploads or use the site's resumable uploader
  5. If you own the site: raise client body/header timeouts if legitimate clients are slow (nginx 'client_body_timeout' and 'client_header_timeout', Apache 'RequestReadTimeout' in mod_reqtimeout)
  6. If you own the site: check load balancer idle timeouts, which may be shorter than your web server's

Why it happens

RFC 9110 defines 408 as the server not receiving a complete request message within its waiting time. Slow uplinks, idle keep-alive connections and aggressive anti-slowloris timeouts cause it.

FAQ

Is 408 the same as 504?

No. 408 means the server waited too long for your request. 504 means a gateway waited too long for an upstream server's response.

Related errors

ERR_TIMED_OUTERR_CONNECTION_TIMED_OUTHTTP 409 ConflictHTTP 410 GoneHTTP 405 Method Not AllowedHTTP 413 Content Too LargeHTTP 422 Unprocessable ContentHTTP 429 Too Many Requests

Source: IANA HTTP Status Code Registry · fixes written and reviewed by the editors (see our editorial policy)

Last updated: