Smart Home & Tech
HTTP 408 Request Timeout: What It Means and How to Fix It
Retry once. If only a large upload fails, try a smaller file you already have. Do not pause antivirus or invent a timeout number.
Quick meaning
The server closed the connection because it did not receive the complete request within its allowed wait time.
| Error | HTTP 408 |
|---|---|
| Family | HTTP |
Safe first actions
- Refresh the page once
- Try a different browser or incognito window
- Check internet connection stability and upload speed
- Disable VPN or proxy temporarily
- Reduce request payload size if uploading
What not to do
- Assume the site is down for everyone
- Repeatedly hammer refresh
- Ignore upload speed limitations
- Change DNS providers as a first step
- Blame the browser without evidence
When the website or provider must fix it
If the error persists after client-side checks (different browser, different network, small payload, no VPN, extensions disabled), the website or service provider must increase request timeout settings on web servers, application servers, load balancers, and API gateways; ensure consistent timeouts across the request path; implement streaming or chunked upload handling for large payloads; and provide clear client-side guidance on maximum file sizes and recommended upload methods.
HTTP 408 means the server timed out waiting for your request to finish arriving. It closed the connection. You may retry the same request. This is not a missing page, and it is not the server crashing. A missing page is 404. A gateway that got tired of waiting for a different server is 504. A gateway that received a bad reply from that other server is 502. Write down whether 408 appeared while a page was simply opening, or only while a file was uploading.
There is no standard number of seconds for this. The limit belongs to that server or to a proxy in front of it. This guide will not tell you to set it to 30, 60, or 120.
Step 1: Retry once, then split the cases
- Send the request one more time. A short blip can produce a single 408.
- If an ordinary page returns 408 on that second try, open a different site you use every day. If every site stalls, leave this article and use the Wi-Fi guide or Chrome not loading pages. A 408 on one site while others load is that site or the path to it.
- If 408 appears only when you upload or submit a large form, stay on this page for the next step. Do not keep submitting the large file in a loop.
Step 2: A smaller file you already trust
Pick a smaller file from the same folder, one you already meant to send. If the smaller file goes through, file size, upload duration, or a site-specific rule may be involved; the 408 alone does not prove which limit fired. Compressing with the tool you already have, or sending fewer files, is the test. Do not download an “upload accelerator.” Tell the site the time, the fact that a small file worked, and that the large one returned 408. They choose whether their limit can change. You cannot raise it from the browser.
Step 3: A private window, not a protection pause
Open a private window and repeat the action once. If it succeeds there, an extension, saved site data, or sign-in state in the normal window may differ. Turn extensions off one at a time. Leave antivirus and real-time protection on. Do not pause them to see if the upload gets through. A security product that quarantines a download is a different problem, and it stays on while you read its own history.
A personal VPN can add delay. Disconnect it, try once, and turn it back on. A work VPN the job requires stays connected. Do not switch VPN regions to slip past the timeout.
Step 4: One other network, then stop
Try the same small action on a phone using mobile data. If the phone succeeds and the PC still gets 408 on ordinary pages, this PC’s path is the suspect. If the phone fails on the same upload, the site’s limit is the story. Stop. Do not edit proxy timeouts, and do not install server software because the error mentioned a gateway. If you operate the site, ask the host to read the timeout that fired. Do not paste a configuration snippet from a forum into a live server.
What you should be able to point at
- Page load versus upload, written down.
- One retry. Other sites checked if ordinary pages fail.
- A smaller file you already had, if the failure was an upload.
- Private window tested. Protection left on. Personal VPN restored if you turned it off.
- No timeout number changed on a server you do not run.
Example: the large photo, not the connection
A photo site returns 408 when a large picture is uploaded. Other websites open. A smaller picture from the same folder uploads. They send the site a note that the small file worked and the large one timed out. They do not pause antivirus, and they do not change DNS. A 408 on every website, including a simple home page, would have left this article for the Wi-Fi or browser guide instead of an upload test.
Related guides
Last updated: October 28, 2026
Last reviewed October 22, 2026. Suggest a correction
Questions readers ask
Is 408 the same as 504?
No. 408 means this server waited for your request to finish arriving. 504 means a gateway waited for some other server and gave up. The retry you can do is the same shape: once, then stop if nothing changed.
Should I turn antivirus off?
No. Use a private window to test extensions. Leave real-time protection on.
How long is the timeout supposed to be?
This page will not name one. The operator chose a limit. Your evidence is whether a smaller file succeeded.
The browser shows “failed” and no status.
That may be a dropped connection rather than a real 408. Read the status in the browser’s network list if you already know how. If you do not, the phone test is enough. A dropped connection on every site is the Wi-Fi guide.
I run the website. Can I raise the limit?
Only with the host’s current documentation for the proxy you actually use. Do not apply a snippet written for a different product. Raising a limit without watching load can make an outage worse.
Sources and methodology
Claims that depend on an outside authority are tied to the references below. Product details change. Confirm the current specification sheet before you buy or install anything.
- RFC 9110: 408 Request Timeout — RFC Editor (standard), accessed October 28, 2026. Primary HTTP or DNS specification for the status or response behavior discussed in this article.
- MDN: 408 Request Timeout — Mozilla Developer Network (documentation), accessed October 28, 2026. Technical explanation of this HTTP response status and its normal meaning.
Information on this site is for general educational purposes and is not professional advice.
Parent topic: Smart Home & Tech