408 is about the request arriving; 504 is often waiting on upstream response.

Mobile networks only?

Packet loss and backgrounding can stall uploads—retry with smaller payloads.

HTTP keep-alive timeouts may need alignment with long uploads.

Error fix

How to fix “408 Request Timeout”

The server gave up waiting for the full request—slow uploads or idle connections.

Start here first. Step 1 fixes most cases—then work down the list.

Why this works

These steps work because it removes the most common source of mid-request resets: VPN/proxy interference.

408 is returned when the server closes an idle connection or times out reading the request body.

Speed up or extend
1. Compress uploads or split files; verify client keeps sending data.
2. Tune proxy and server read timeouts coherently.
3. Use resumable upload APIs where available.

Also see: 408 — browse the HTTP status hub.

408 vs 504?: 408 is about the request arriving; 504 is often waiting on upstream response.
Mobile networks only?: Packet loss and backgrounding can stall uploads—retry with smaller payloads.
Load balancer idle?: HTTP keep-alive timeouts may need alignment with long uploads.

Still stuck? Try these related fixes next.

Tweak the message and run again—we'll match an existing fix or generate a new page.

Original error message

408 Request Timeout