HTTP 408: how to fix the timeout error

When you visit websites on the internet, you access them through your web browser. The basis for this trans­mis­sion, which is handled by default through TCP, is the stateless protocol HTTP (“Hypertext Transfer Protocol”), which describes the initial exchange of messages between web server and browser. According to the classic client-server principle, the browser issues an HTTP request, after which the server sends back a response which includes a status code.

Whilst you don’t notice most of this com­mu­nic­a­tion as a user, the situation is usually different when it comes to HTTP error codes: if a problem occurs during the exchange, the browser often presents cor­res­pond­ing code in the 4xx and 5xx series, which stand for various client or server-side error sources. For example, the HTTP 408 message tells you that the client request timed out. How, exactly, this timeout occurs and how you can solve the problem will be explained in this guide.

The HTTP error code 408 – like all members of the 4xx error series – is one of the messages that indicate a client-side problem. When you go into the back­ground of this error message in more detail, however, it becomes clear that it does not ne­ces­sar­ily have to be a browser mal­func­tion: Error 408 is linked to “Request Timeout” in­form­a­tion, which simply means that the request sent from the client to the web server took more time than the web server allows for. As a result, the browser receives the HTTP 408 message instead of the actual response. Of course, this may be due to problems with your internet con­nec­tion, but it cannot be ruled out that the timeout is the result of an overload or incorrect con­fig­ur­a­tion of the web server.

Although there are over 50 different  HTTP status codes, more than half of which are error messages, these messages often only prove to be a rough guideline for the following problem solution. This also applies to error code 408, which basically just says that too much time has passed in a pre­scribed time interval after es­tab­lish­ing at TCP/IP con­nec­tion without data trans­fer­ring through the con­nec­tion. However, there are several possible causes for this delay, and for the sub­sequent error messages, for example:

• Bandwidth problems and dis­con­nec­tions: HTTP 408 messages often result from problems with your internet con­nec­tion. For example, the bandwidth may be so low that the HTTP request fails due to the defined time interval. It is also possible that the internet con­nec­tion to the server was tem­por­ar­ily in­ter­rup­ted after the TCP/IP con­nec­tion was es­tab­lished, so the request data might not have been com­pletely sent.
   
• Trying to access incorrect or in­ac­cess­ible URLs: Not every website URL is available to visitors without en­cryp­tion. If you in­ad­vert­ently try to access a page that you have no au­thor­isa­tion for, or you try to access an HTTPS page that doesn’t have an SSL/TLS activated, a 408 timeout could certainly occur. In addition, many URLs have re­stric­tions regarding the permitted HTTP request methods (GET, POST, HEAD, PUT, and so on), so the timeout can also be the result of an in­cor­rectly applied method. In both cases, however, there are also standard messages that indicate the problem (“403: Forbidden“ for un­au­thor­ised access attempts and “405: Method Not Allowed” for un­avail­able HTTP methods).
   
• Incorrect web server con­fig­ur­a­tion: Re­gard­less of the web server software used, the website runner specifies how many seconds an HTTP request should be rejected in the re­spect­ive con­fig­ur­a­tion file. There are separate values for the header and the body of the HTTP messages. If the server chooses too short a time interval for pro­cessing one or both package com­pon­ents, this may well be the reason for the 408 error on user pages.
   
• Plugins, ex­ten­sions, modules, etc.: A problem that can be both a client-side and a server-side problem is the use of faulty or outdated ex­ten­sions. Therefore, both the browser plugins used by the website visitor and the CMS modules used by the operator could be re­spons­ible for the HTTP timeout and cause the HTTP 408 error.

If you are con­fron­ted with a “408: Request Timeout” message when visiting a website, you are naturally in­ter­ested in the quickest possible solution to the problem. However, you cannot always fix the problem on your own. If the error is ex­clus­ively on the client side, chances are good that you can correct the 408 error using one of the following ap­proaches.

Before you go on more intensive troubleshoot­ing, your very first look should be at the URL you entered. The URL you have chosen might no longer be ac­cess­ible to you. This happens in par­tic­u­lar if you try to access the targeted website using old bookmarks. If the website in question has made changes to per­mis­sions or permitted request methods in the interim, or has switched to HTTPS, it is very likely that the saved link will no longer lead to the website, but instead the HTTP-408 or com­par­able error messages. So make sure that the URL you entered is correct and up to date to avoid this error source.

Problems with an internet con­nec­tion are always a nerve-racking affair. Sometimes, the con­nec­tion no longer works at all, so access to the web remains com­pletely closed. While you will in­ev­it­ably notice these complete failures, in most cases you won’t notice any temporary fluc­tu­ations or con­nec­tion in­ter­rup­tions. So, the cause for slow loading times and error messages during loading – like the 408 error – should be quick to find on the visited website. For this reason, it is re­com­men­ded that you check your own network con­nec­tion by visiting other websites or per­form­ing a DSL speed test, for example.

If you find that there are technical dif­fi­culties with your access, you should reboot your router. If the con­nec­tion problem persists, you should contact your internet provider.

With plugins, addons, or ex­ten­sions, web browser functions can be extended with just a few clicks. However, the practical ex­ten­sions do not always work as desired – in the worst case, they make the surfing ex­per­i­ence worse and cause error messages like HTTP-408, often because the ex­ten­sions are outdated and/or no longer com­pat­ible with the current browser version, since they are no longer actively developed. To test whether the timeout error is due to one or more included ex­ten­sions, tem­por­ar­ily de­ac­tiv­ate them com­pletely. Once the problem is resolved, you can turn on the plugins one by one to find out which was re­spons­ible for the HTTP error message.

The “408: Request Timeout” error cannot always be corrected using the sug­ges­tions listed above – e.g. if it is due to prolonged problems with your network con­nec­tion. In this case, it is advisable that you wait and try again at a later date. If the HTTP exchange still fails, it is highly likely that the cause of the error lies in the web server. If the re­spons­ible website has provided ap­pro­pri­ate contact data, you can find out whether they are aware of the problem and when the page will be available as usual again.

Whilst the HTTP timeout problem is primarily annoying for visitors because the target page cannot be opened, its impact on website operators can be much bigger. If many users are con­fron­ted with the error message over a longer time, this not only has a negative effect on traffic, but also on the website’s repu­ta­tion. In addition, there is also the threat of pun­ish­ment by search engines if HTTP 408 errors occur more fre­quently of if a cor­rec­tion takes too long. If you are re­spons­ible for a website, you should take immediate action once you discover the issue.

Incorrect settings are amongst the most common server-side HTTP error code causes (like “408: Request Timeout”). You should check the re­spect­ive file first, either on Apache (httpd.conf; apache2.conf), NGINX (nginx.conf), or others. In Apache web server settings, for example, the dir­ect­ives “KeepAliv­e­Timeout” and “Re­questRead­Timeout” deserve special attention. Both specify a time interval for incoming HTTP requests, which may be too low (15 or even 30 seconds is re­com­men­ded). If your website runs on an NGINX server, the dir­ect­ives are “keepalive_timeout,” “client_body_timeout,” and “client_header_timeout.” Do not forget to save the changes to the re­spect­ive con­fig­ur­a­tion file before starting the web server to finally resolve the HTTP 408 problem.

As mentioned above, HTTP error 408 only occurs on one page or in­di­vidu­al pages on a website because those pages have con­fig­ur­a­tion errors with their action rights and permitted HTTP methods. So if you discover a timeout problem, it is re­com­men­ded to check which URL(s) are causing the HTTP error. To avoid having to access each page manually, just take a look at your web server’s error log file, where all the HTTP errors are auto­mat­ic­ally archived. Once you have iden­ti­fied the prob­lem­at­ic pages, you can search for specific causes for the timeout and, if necessary, make changes to the access rights and methods.

Content man­age­ment systems are in high demand as a basis for websites. A major advantage of these platforms is their high degree of ex­tens­ib­il­ity through modules, templates, and plugins, which provide ad­di­tion­al functions, layouts, and designs. These ex­ten­sions, like their client-side coun­ter­parts, can also be re­spons­ible for the 408 request timeout. In the abundance of ad­di­tion­al modules and plugins, there are always rep­res­ent­at­ives who promise a huge added value for their own product, but in the end they don’t work the way they should or stop being developed at a certain point. This is es­pe­cially true for ex­ten­sions from third-party vendors, where there may be problems with every new CMS version. The simple solution is to disable plugins (and modules if necessary).

Of course, the error does not always have to be traced back to an external source, but can just as easily be hidden in your own code. If you are dealing with error code 408 and have not yet found a solution, either during the web server con­fig­ur­a­tion file in­spec­tion or during the content man­age­ment system check, it is advisable to look at the HTML framework, as well as the built-in CSS snippets and scripts (JavaS­cript, PHP, etc.). Do not hesitate to perform a complete debugging process with the ap­pro­pri­ate software if the timeout problem cannot be solved any other way. This allows you to ef­fi­ciently locate and repair faulty code.

The more HTTP requests reach the web server, the more resources it needs for pro­cessing. If the available computing power is not suf­fi­cient to handle the incoming traffic, error messages like “408: Request Timeout” are not uncommon. If your budget allows, you should consider in­creas­ing processor per­form­ance and memory.