- Software and digital services
- HTTP service
408
HTTP 408 Request Timeout: the server did not receive the complete request in time
Risk level
Low
Usually safe to check without specialist tools.
Urgency
Medium
Quick answer
HTTP 408 means the server did not receive a complete request message within the time it was prepared to wait.
Safety first
Stop and check this first
- Do not automatically replay a timed-out payment, creation or other non-idempotent request. Confirm whether the first attempt was applied.
Safe checks you can perform
- Measure request upload and completion
- Retry only a safe operation on a new connection
- Compare request-read timeouts by layer
Leave these tasks to a qualified professional
- Do not attempt this professional task: Trace where request receipt stopped
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Trace where request receipt stopped
What they doCorrelate connection and byte-count telemetry across the client, edge and origin to identify the layer that timed out.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Measure request upload and completion
Record content size, connection timing and whether all request bytes left the client without retaining the sensitive body.
Do not automatically replay a timed-out payment, creation or other non-idempotent request. Confirm whether the first attempt was applied.
Evidence: RFC 9110 section 15.5.9 - 408 Request Timeout · IANA Hypertext Transfer Protocol Status Code Registry
Retry only a safe operation on a new connection
Repeat GET or another known-safe request once; verify idempotency before retrying writes or uploads.
Do not automatically replay a timed-out payment, creation or other non-idempotent request. Confirm whether the first attempt was applied.
Evidence: RFC 9110 section 15.5.9 - 408 Request Timeout · IANA Hypertext Transfer Protocol Status Code Registry
Compare request-read timeouts by layer
Check edge, proxy and origin limits for headers and body receipt instead of changing response or upstream timeouts.
Do not automatically replay a timed-out payment, creation or other non-idempotent request. Confirm whether the first attempt was applied.
Evidence: RFC 9110 section 15.5.9 - 408 Request Timeout · IANA Hypertext Transfer Protocol Status Code Registry
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- HTTP
- Product type
- HTTP service
Known code variants
- 408 Délai de requête dépassé
- 408 Request Timeout
- 408 Tiempo de solicitud agotado
- 408 Timeout della richiesta
- 408 Zeitüberschreitung der Anfrage
- código HTTP 408
- error HTTP 408
- événement Fronius 408
- evento Fronius 408
- Fronius Ereignis 408
- Fronius event 408
- Fronius inverter 408
- Fronius Symo / Eco 408
- Fronius Wechselrichter 408
- HTTP 408
- HTTP error 408
- HTTP status 408
- inversor Fronius 408
- inverter Fronius 408
- onduleur Fronius 408
- status code 408
What it means
The timeout concerns receiving the request, not waiting for the upstream response. A retry can use a new connection when the current one is unusable.
Warnings and stop conditions
- Higheditorial warning
Do not automatically replay a timed-out payment, creation or other non-idempotent request. Confirm whether the first attempt was applied.
Evidence: RFC 9110 section 15.5.9 - 408 Request Timeout · IANA Hypertext Transfer Protocol Status Code Registry
Symptoms and causes
Probable causes · in order
- The client sent the request too slowly or incompletelyConfirmed
An interrupted upload, stalled connection or slow sender can leave the server waiting for the remaining message.
Evidence: RFC 9110 section 15.5.9 - 408 Request Timeout · IANA Hypertext Transfer Protocol Status Code Registry
- An intermediary and origin use incompatible request timeoutsPossible
A proxy can keep a connection open longer than the next server is configured to wait for the full request.
Evidence: RFC 9110 section 15.5.9 - 408 Request Timeout · IANA Hypertext Transfer Protocol Status Code Registry
Virtual technician
Does 408 still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
RFC 9110 section 15.5.9 - 408 Request Timeout
Internet Engineering Task Force · 2022 · official_doc
- 2
IANA Hypertext Transfer Protocol Status Code Registry
Internet Assigned Numbers Authority · 2025 · official_doc
Was this entry useful?