A 408 Request Timeout error means the web server closed the connection because the client took too long to send a complete request. The server itself is up; it simply stopped waiting. This is different from a 504, where the server is the slow side. Most 408 errors come from the visitor's connection or from large uploads.
Before you start
- Note when the 408 error appears: on every page, or only when uploading or submitting a form.
- A second network (for example mobile data) to compare with.
Common causes of a 408 Request Timeout
- A slow or unstable internet connection, so the request body arrives too slowly.
- Large uploads over a weak uplink, such as media files or backups through a web form.
- VPNs, proxies or security software that buffer or slow outgoing traffic.
- Browser extensions holding requests open.
- Short server timeouts set by a custom configuration on a VPS.
How to fix a 408 error
- Reload the page. A one-off 408 is often a network blip.
- Test another network. If the page works over mobile data, the issue is your local connection or router.
- Turn off VPN and proxy software temporarily and retry.
- Disable browser extensions or use a private window.
- Upload big files another way. Use FTP or cPanel → Files → File Manager instead of a slow web form, or split the upload. See upload size limit errors.
- Check the logs. In cPanel → Metrics → Raw Access 408 lines show which URLs time out and for which IPs. If many visitors see it, contact support.
- On your own VPS, review the client body timeout:
client_body_timeoutandclient_header_timeoutin Nginx, orRequestReadTimeoutin Apache. Raise them only moderately, because very long timeouts make slow-request attacks easier.
Note: A burst of 408 lines from the same IP in your access log can be a slow-request attack or a monitoring bot, not real visitors. Blocking that IP is often the right fix.
What to check afterwards
Repeat the action that failed. If it was an upload, confirm the file arrived complete. Watch the access log for new 408 entries over the next hour.
FAQ
Is a 408 error the website's fault?
Usually not. It most often means the request reached the server too slowly from the visitor's side.
What is the difference between 408 and 504?
408: the server waited for the client. 504: a proxy waited for the backend server. See fixing 504 Gateway Timeout.
Can a 408 error affect SEO?
Occasional 408s do not. If Googlebot sees them often, crawl rate may drop, so investigate repeated ones.