408 HTTP Origin: Network Last updated 8 Oct 2026

HTTP 408 Request Timeout

The server closed the connection because the client took too long to send the complete request.

Exact message you may see request timeoutRequest Time-out
Explore the map of this error Full error map →
Seen on: Nginx Apache

Meaning

408 is about the client being slow to *send* the request (headers/body), not the server being slow to respond (that’s 504). It’s common on slow mobile networks, large uploads, or idle keep-alive connections.

Common causes

  • Slow or unstable client network during upload
  • Large request body with a short server body-read timeout
  • Idle keep-alive connection reused after the server closed it
  • Load balancer idle timeout shorter than the upload duration

⚡ Quick fix

  1. Retry the request (408 is generally safe to retry for idempotent requests)
  2. Increase body/header read timeouts on the server or load balancer
  3. Upload large files in chunks or via direct-to-storage (pre-signed URLs)

Detailed fix by platform

Nginx

  1. Raise read timeouts:
    nginx
    client_body_timeout 120s;
client_header_timeout 60s;

Apache

  1. Increase Timeout and check mod_reqtimeout (RequestReadTimeout header=20-40,MinRate=500 body=60,MinRate=500).

How to diagnose

  1. Payload — Is this a large upload or slow client?
  2. Timeouts — Which hop (LB, proxy, server) has the shortest read timeout?
  3. Retry — Does an immediate retry succeed?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

0x80070035 — 0x80070035: The network path was not found (System error 53) (Windows)0x800700350x80072EE7 — Error 0x80072EE7 (Windows Update / Microsoft Store: server name could not be resolved) (Windows)0x80072EE70x8024402C — Windows Update error 0x8024402C (cannot connect to update server) (Windows)0x8024402C14 UNAVAILABLE — gRPC Error: 14 UNAVAILABLE: No connection established / failed to connect to all addresses (API)14 UNAVAILABLE413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413499 — HTTP 499 Client Closed Request (Nginx) (HTTP)499504 — HTTP 504 Gateway Timeout (HTTP)504511 — HTTP 511 Network Authentication Required (HTTP)511408

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.