Ошибка 408 peer is not answering

Encountering HTTP status code errors can be frustrating and stressful. This is especially true when you don’t know what the message means or what’s causing it. One of the errors you might be dealing with is HTTP 408 Request Timeout.

Fortunately, you can take a handful of steps to troubleshoot and resolve this issue. You’ll simply need a basic understanding of what could be causing the HTTP 408 error, then implement solutions to fix it.

In this post, we’ll explain the HTTP 408 status code and some common causes of the error. Then we’ll walk you through eight potential solutions for resolving it. Let’s jump in!

Check Out Our Video Guide to Fixing the HTTP 408 Error

What the HTTP 408 Status Code Is

HTTP status codes indicate the status of a client’s request. They can also redirect clients to different resources, depending on their requests.

The most common HTTP status code is 404, which indicates that the requested resource could not be found. Other common status codes include 200 (OK), 400 (Bad Request), and 500 (Internal Server Error).

Status codes are divided into five categories:

1. Informational: The server is still processing the request.
2. Successful: The request was completed successfully.
3. Redirects: The client should be redirected to a different resource.
4. Client Errors: There was an error with the request.
5. Server Errors: There was an error with the server.

HTTP 408 falls into the category of client errors. The status code communicates that the server did not receive a timely response from the client and that the server timed out waiting for the request. This can happen if the client takes too long to send the request or the server is too busy to process it.

The HTTP 408 error is similar to the 504 Gateway Timeout status code. However, the former doesn’t come from a gateway or proxy server. Instead, it comes directly from the web server the client is connected to.

Encountering HTTP status code errors can be frustrating and stressful. 😰 This guide can help. 🛠Click to Tweet

Common Causes of the HTTP 408 Request Timeout Error

There are a handful of potential reasons behind the HTTP 408 request timeout error. These causes include:

• Network latency
• Clients timing out
• Servers being too busy to handle the request

The 408 Request Timeout error means the request you sent to the website server took longer than the server was prepared to wait. It can happen due to heavy traffic on the internet or a slow connection on your side.

The problem with this status code is that it can occur for both client-side and server-side-related reasons. In other words, although the 408 error is categorized as a client error, this doesn’t necessarily mean the issue stems from the browser or device. It’s possible that the server is misconfigured or isn’t handling requests correctly.

How To Fix the HTTP 408 Error (8 Solutions)

Now that we understand more about the HTTP 408 status code, let’s discuss how you can resolve it. Below are eight potential solutions you can use, separated into two categories: client-side and server-side.

Client-Side

Below are some client-side solutions you can use to resolve the HTTP 408 error!

1. Back Up Your Site

The first thing you should do before troubleshooting the HTTP 408 error is back up your website. Then, if anything goes wrong while trying to fix the issue, you will have a full, updated version of your files and database to restore.

There are several methods you can use to back up your site. One is the manual approach. This method involves using a Secure File Transfer Protocol (SFTP) client, such as FileZilla. After receiving your SFTP credentials from your host and connecting to the server, you can download your files from the root directory (public_html folder).

Next, you’ll need to download your database via phpMyAdmin. If you’re a Kinsta user, you can access this through MyKinsta > Sites > Info:

Then select Open phpMyAdmin to launch the database manager. Select your site’s database from the menu:

Next, click on Export at the top of the screen. Make sure to select SQL under Format, then click on Go. Your database file should begin downloading.

You can also use a backup plugin such as UpdraftPlus. After installing and activating the plugin, navigate to Settings > UpdraftPlus Backups in your WordPress dashboard, then click on Backup Now:

A third option is to back up your site through your web host. At Kinsta, you can view your existing backups by logging into MyKinsta and then navigating to the Backups tab:

You can create up to five manual backups, which are automatically stored for two weeks. We also offer DevKinsta, a free local WordPress development tool you can use for staging and backing up your site to a local environment.

You can do this by going to DevKinsta and selecting the Import from Kinsta option. You may need to verify your hosting credentials. Once you choose your site, DevKinsta handles the rest.

2. Check the URL

One of the reasons you may be seeing the HTTP 408 status code error is that you simply typed the wrong URL into the browser. Therefore, you should now double-check the URL to ensure you didn’t make any typos.

Pay close attention to the domain name, especially if there are slashes or hyphens. Try re-entering the URL and then reloading the page. If the timeout request error is still present, you can move on to the next solution.

3. Review Recent Database Changes

If you’ve made any recent changes to your database, they may be causing the HTTP 408 error. You’ll need to revert any changes you’ve made to fix the issue.

Recently installed extensions or updates to your database may have altered database records that are causing problems. To see if this is the case, we recommend opening your database (phpMyAdmin) and manually going through to check any tables or records that have been recently modified. If you find any, revert them to their original states.

4. Uninstall Extensions and Plugins

Adding extensions and plugins to your site can cause various incompatibility issues and errors, including the HTTP 408 status code. One of the easiest ways to see whether this is the case is to deactivate all of the plugins on your site.

If you have access to your WordPress dashboard, you can do this by navigating to Plugins from the admin area, selecting all of the installed plugins, then selecting Deactivate from the Bulk actions dropdown menu. Now click on Apply:

If you don’t have access to your dashboard, you can bulk deactivate your extensions by connecting to your site via SFTP, then renaming the plugins folder to something like “plugins_old”.

Revisit your site. You can assume a plugin was to blame if you no longer see the error message.

You’ll need to reactivate each plugin one by one, checking the site in between. Once you see the error message again, you’ll have to uninstall that extension and find a replacement (or contact the developer for more information).

5. Roll Back Recent Changes

If you’ve recently made any changes to your WordPress site, such as installing a new plugin or updating the WordPress software, you might be seeing the HTTP 408 error. New tools can sometimes lead to configuration problems. You can roll back recent changes by restoring your site to a previous version.

If you’re a Kinsta user, open your MyKinsta dashboard, then navigate to Sites and select your site. Next, click on Backups.

From the list of backups, find the version you want to restore, click on Restore to, then select Staging or Live:

Next, you can confirm the backup restoration and click on Restore backup. Once the backup is complete, you can check to see whether the error message is still displaying.

Server-Side

If none of the above solutions worked, the HTTP 408 error might be caused by a server-side issue. Let’s look at potential solutions you can use to resolve it.

6. Check Server Config Files

One of the ways you can determine the cause of the HTTP 408 error is to check your server configuration files via SFTP. The process for doing so will depend on your server software.

Chances are that your server is either running on Apache or Nginx. If you’re a Kinsta user, we use Nginx.

If you’re using Apache, you can look for the .htaccess file within your site’s root directory. When you locate the file, open it and look for the following lines:

• KeepAliveTimeout
• RequestReadTimeout

If you find these directives, you can comment them out by using the # symbol prefix before the line. Then you can save the file and reload the page in your browser.

If you’re a Kinsta user, you can check your .htaccess file by opening your MyKinsta dashboard and navigating to your website under Sites. Locate the SFTP/SSH section to get your credentials, then use them to connect to your site via an FTP client.

Next, navigate to the public_html folder, then locate and open the .htaccess file:

Look for either of the directives listed above. If you see any of these rules, comment them out and save your changes.

7. Review Application Logs

Your server-side logs can be invaluable for providing information about your applications, including what they did, the pages requested, the servers connected to, and more. If you’re a Kinsta user, you can check your error logs using the log viewer in MyKinsta.

If you’re not using a Kinsta hosting plan or your host doesn’t provide a logging tool, you can insert the following code into your wp-config.php file:

define( 'WP_DEBUG', true );

define( 'WP_DEBUG_LOG', true );

define( 'WP_DEBUG_DISPLAY', false );

This will enable WordPress debugging mode.

From MyKinsta, navigate to Sites > Logs:

Here, you’ll find the Log viewer that displays your error logs. You can click on access.log from the dropdown menu. This is where you can find all the HTTP requests from your website. You can also look for any HTTP 408 requests using the search bar.

If you locate any errors, you can use the information to pinpoint which web page is causing the issue. This can help you narrow down the source of the problem.

8. Debug Apps or Scripts

At this point, if you’re still seeing the HTTP 408 error, it’s time to debug your site. There are a handful of options you can use for this process.

One is to use a plugin such as Query Monitor:

This free plugin debugs your website’s performance and development. It enables you to check database queries, scripts, timing, and more.

Another option is using an Application Performance Monitoring (APM) tool. This software helps you monitor and optimize the performance of your website or application.

Using an APM tool can help you debug your site by giving insight into its performance and the location of any bottlenecks. This information can help you identify and fix any issues causing your website to run slowly or have other performance problems.

You can use our Kinsta APM Tool. It’s a custom-designed performance monitoring tool for WordPress sites that helps you identify performance issues. It’s also free for all sites hosted with us.

You can access the Kinsta AMP via your MyKinsta dashboard by navigating to Sites > Kinsta APM:

Once you enable the APM, you can use a variety of tools and features. These include diagnosing performance issues and monitoring results.

 It’s easier than you may think to fix this pesky issue. 😌 Here’s how to get started… ✅Click to Tweet

Summary

HTTP status codes can provide a wide range of information about client and server requests. However, some of these messages indicate problems, such as the HTTP 408 Request Timeout error.

As we discussed in this post, the source of the issue may be either client- or server-side. To troubleshoot and resolve the status code error, you should review and roll back recent changes, check your server configuration file and application logs, and debug your apps and scripts.

Do you want to switch to hosting that provides easy access to software for identifying, testing, and fixing issues on your site? Check out our Kinsta hosting plans to learn more about our APM and development tools!

Do you often find yourself running into issues when trying to access certain websites? One of the most common errors that can occur during web communication is HTTP 408. This http error is commonplace and can cause a lot of frustration for users who are just trying to browse online. If you’ve been struggling with this issue, don’t worry! In this blog post, we’ll explain what an HTTP 408 status code is, as well as how to fix it.

What does HTTP 408 status code mean

The HTTP 408 status code, also known as a request timeout error, is an error response of Hypertext Transfer Protocol given by a web server when it has been waiting too long for a client’s request. This indicates that the request has been cancelled not because of any gateway or proxy server but due to the server not receiving any information from the client on time. In general, if an internet connection remains idle for more than 15-20 seconds, the request is likely to be terminated by the web server.

Server Side or Client Side problem

When it comes to diagnosing problems with HTTP requests, determining whether the issue is on the web servers side or the client side can be tricky. The 408 HTTP status code is an indication that a request has timed out. This request timeout HTTP error can be caused either by a long-running process on the server side or an imprecise configuration of network parameters on the client side. To figure out which one is at fault, administrators must carry out a root cause analysis looking at both of these possibilities. Ultimately, since the 408 error by definition pertains to timeouts, it could be argued that this error code is always a result of either server-side or client-side issues, rather than just one side or the other exclusively.

Causes of HTTP 408 Request Timeout

1. Slow Server Response: Slow response times from the server hosting the website can cause the HTTP 408 Request Timeout error. This can be caused by a variety of factors, including inadequate server resources, hardware or software issues, or overloaded servers.
2. Network Congestion: Network congestion can slow down the connection between the client and the server and cause the 408 Request Timeout error.
3. Incomplete Requests: If the request sent to the server is incomplete or contains invalid data, it can cause the server to timeout and return the 408 Request Timeout error.
4. Proxy or Firewall Block: If the request is being made through a proxy or firewall, it can be blocked due to security settings, resulting in the 408 Request Timeout error.
5. Misconfigured Web Server: If the web server is improperly configured, such as when the server is unable to process requests, it can cause the 408 Request Timeout error. Note that configuration differs on different web server software (Apache, nginx).
6. DNS Issues: If the DNS lookup for the requested domain fails, the 408 Request Timeout error can be triggered.

How To Fix the HTTP 408 Error

1. Check your internet connection

If you’re receiving an HTTP 408 Error while trying to browse the internet, the first step to correcting the problem should be to check your internet connection. Often times this type of error is due to a weak connection or an interruption in your internet service. Checking it could require anything from restarting your modem or router and verifying the cables are securely connected, or simply waiting for your service provider to resolve any connection issues. This is easily done by going into the settings of your devices and checking their status. With clear and stable access to the internet, you can get back to browsing right away and avoid further errors like these.

2. Check the URL

Because of the relationship between the client and server connections, resolving the error starts with checking if that URL is wrong. If there is an incorrect character or the address was written incorrectly, this might be the source of the problem. It can become very frustrating trying to debug something like this until you check the obvious first. Luckily almost anyone can use their own logic to identify if there might be something wrong with the URL and make sure its correct; if it is not, they can fix it and get back to browsing immediately!

3. Clear your browser cache

One of the most frustrating experiences while browsing the internet is receiving an HTTP 408 Error from your browser, as this can render your web page inaccessible and delayed. Fortunately, clearing your cache might be just the solution you need to get it fixed up! By clearing out old files, data and history stored within a web browser, one’s computer can free itself of extra latency which might be causing the issue. As a result, this could help to alleviate whatever HTTP error you are seeing and allow you to carry on with your browsing as normal.

4. Try a different browser

Fortunately, the problem may not actually lie with you and your work, but instead the browser you are using. If you are constantly running into this error, it could be a good idea to try a different browser. Different browsers can take you in different directions, which can lead to entirely new perspectives. If your current web browser isn’t cutting it, why not try another option? It could solve the issue of the recurrent error and help move your project forward without further problems.

5. Check for browser extensions or plugins

It is possible for browser extensions or plugins to cause an HTTP 408 Error. This error can present itself when there is a timeout waiting for the server to respond. Typically, this happens when http requests are blocked by an extension or plugin because it does not recognize the server. There are a few techniques users can try if they encounter this issue. Disabling the extensions and plugins, attempting again over a secure (SSL) connection, or refreshing their browser.

6. Disable firewall or antivirus software temporarily

If you’re dealing with an HTTP 408 error, one suggestion that can help you fix the issue is to temporarily disable your firewall or anti-virus software. This can be done quickly and easily, though it should be done carefully to prevent potential intrusions and other problems. Keep in mind, before turning off your firewall or anti-virus protection software. Make back up of your information to a secure source – just in case there’s a problem. After temporarily disabling the software, see if the HTTP 408 error is resolved; if it is not still present, then you know you have something else at hand causing the issue. In that case, consider consulting other sources for assistance in resolving the error.

7. Contact your ISP

If you have followed all of the steps above and are still seeing a 408 error messages, it is possible that your ISP is blocking access to the website in question. Contact your ISP and inquire about this possibility. They should be able to help you resolve the issue.

8. Check for server-side issues

It could be caused by a misconfigured system, too many requests on the server or incorrect response from third party services. If you see this error message, try sending a smaller request or waiting for the server to cool off before attempting access again. You can also ask your site administrator to check if there are any issues with the system or encounter proxies and firewalls that are blocking connection requests or data packets. The developers of the site can easily see any issues on the server logs or on the .htaccess file.

9. Wait and try again later

It is also possible that the 408 error is simply due to high traffic on the website in question. In this case, waiting a few minutes and trying again later should fix the issue

Similar http status codes

There are a few other HTTP status codes with similar meaning which are also very easily encountered. These include code 409 Conflict, 411 Length Required, 413 Request Entity too Large and many more. All these codes have something in common. They point out to a server/client communication failure which requires further debugging in order to determine the exact cause of the problem. Therefore, even if you don’t come across an explicit HTTP 408 error, consider looking out for similar codes as well before taking corrective action.

All HTTP status codes by categories

В Keenetic OS 3.7 добавлена поддержка DNS SRV, которая, к сожалению, пока работает некорректно и приводит к ошибке 408 в вашем случае. Мы работаем над исправлением этой проблемы.

В список провайдеров добавлены два новых профиля для OnLime: OnLime (tel.moscow.rt.ru) и OnLime (tel2.moscow.rt.ru). С этими профилями доменные имена tel.moscow.rt.ru и tel2.moscow.rt.ru резолвятся в DNS только из A record, а SRV record не запрашивается. Попробуйте выбрать профиль OnLime (tel2.moscow.rt.ru). С ним линия должна зарегистрироваться и работать. В Keenetic OS 3.7 профили провайдеров IP-телефонии подгружаются из облака, поэтому, чтобы загрузить новые профили OnLime обновлять прошивку роутера не нужно.

Если с профилем OnLime (tel2.moscow.rt.ru), будут по-прежнему проблемы с регистрацией линии Onlime, пришлите, пожалуйста self-test.

Signalling protocols are essential to some of the most commonly used applications on the internet. For example, they’re integral to real-time voice, video, and text-based messaging services.

But if you’re using some of these services, you might run into problems from time to time. For example, you might get a SIP Error 408 message.

If you get a SIP Error 408, it means that the request timed out before it could find the user. That could’ve happened for a few reasons. There might be an issue with your internet connection. Or maybe a network provider is blocking the app that you’re trying to use. You may also want to try reconfiguring your firewall to fix the issue.

What is SIP?

First, let’s make sure we’re all starting on the same page. SIP is an acronym that stands for Session Initiation Protocol. This is a signaling protocol that’s used for initiating, maintaining, and termination real-time sessions. SIP is used for voice, video, and messaging applications, among other purposes.

SIP works in combination with other tools to specify and carry the session media. It was designed to act as the underlying transport layer protocol and to be used with User Datagram Protocol (UDP).

If you’re not a technical person, don’t worry. You don’t need to know all of this to fix a SIP Error message. It’s just worth having the background so that you know why you need SIP to use some of your applications.

What are the major types of SIP codes?

There are quite a few different types of SIP codes that you may see while using various real-time messaging applications. These are split into categories based on the first number in the code.

For example, a code that starts with 1 conveys a provisional response. This is used to show that an attempt is being made to form a connection. For example, code 100 means “Trying” while code 180 means “Ringing”.

Codes beginning with a 2 indicate a successful response while codes beginning with a 3 show a redirection response. This means that the connection isn’t being serviced through your intended channel. This could be happening for a few different reasons, such as a temporary move or a proxy requirement.

SIP codes that begin with 4 indicate a client failure response. So you know that if you see a 4 at the start of your code, something went wrong. The numbers that follow the 4 will tell you the specific reason why your request failed.

Codes that begin with 5 and 6 also indicate connection failures. Codes starting with 5 are for server failure responses. Codes beginning with 6 are for global failure responses.

What is a SIP error 408?

SIP Error 408 stands for Request Timeout. This means that the application couldn’t find the user in time. There could be a few different reasons for this. Here are some of the main causes of a SIP Error 408 message:

• Address entered incorrectly
• Your internet isn’t working properly
• Your network provider is blocking the application you want to use
• There’s a firewall on your device that’s blocking the connection
• The application that you’re using is currently experiencing technical difficulties

The fix for your SIP error 408 will depend on what’s causing the problem. For example, if you’ve entered the address incorrectly, you’ll need to correct the mistake to resolve the error.

Alternatively, it’s possible that your internet is causing the problem. In that scenario, you would need to repair your general internet connection to fix the error message.

It’s also possible that the problem is stemming from your network provider blocking the connection. If this is happening, you may want to try using a VPN. VPNs will disguise your internet activity, which can often get you around problems like these.

You might also want to try reconfiguring your device’s firewall. Sometimes this will block the connection from taking place, causing a SIP Error 408. You may need to create an exception in your firewall for the service you’re using.

Finally, it’s also possible that the problem isn’t on your end at all. If you’ve tried all of these solutions and none work, it might just be the application’s fault. In that case, you might want to reach out to them to see when they will fix the issue.

What is a provisional response in SIP?

A provisional response is one of the main messages that you can see while using SIP. The concept of a provisional response is pretty straightforward.

Essentially, this just means that the application you’re using is trying to form the connection. There are several different specific SIP messages that you might see here. Here’s what might be happening when you see a provisional response:

• SIP Code 100 – Trying
• SIP Code 180 – Ringing
• SIP 181 – Call is Being Forwarded
• SIP Code 182 – Queued
• SIP Code 183 – Session Progress
• SIP Code 190 – Early Dialog Terminated

What is SIP call flow?

SIP call flow is what happens to connect two SIP devices or applications. For example, you might be using an internet phone service to contact a friend. When you call them, your phone needs to connect to the other phone before you can speak with your friend.

This is what’s known as SIP call flow. It’s the communication between two SIP devices that lets you connect with someone on the other end. It’s a technical communication that occurs between two devices. One device sends out a SIP request and the other one responds to it.

What is a prack in SIP?

PRACK might sound pretty complicated if you’re not familiar with the term. But it’s actually just an acronym that sounds for Provisional Response Acknowledgement.

This fits into the discussion in a previous section about provisional SIP responses. Essentially, a PRACK is what occurs when one device acknowledges a connection attempt from another.

It’s a broader term that can be used to describe any provision response that a SIP device might have. For example, if you got a 180 Ringing message, that would be a PRACK. A 100 Trying message would be another example of a PRACK.

What is 180 ringing in SIP?

You might get a 180 Ringing message while using a SIP device sometimes. This is exactly what it sounds like. It’s basically the same as what happens when a telephone rings.

Essentially, a 180 Ringing message is a notification that your device is getting an incoming connection request from another. Your SIP device will notify you, through a ring, a message, or some other notification of this connection attempt.

What is the different between 180 ringing and 183 Session Progress?

This can be a bit complicated so let’s take a closer look at precisely what each SIP message means. A 180 Ringing message says that the UA receiving the invite is attempting to alert the user. This may initiate a ringing or some other notification on the receiver’s end.

A 183 Session Progress message is used to convey information about the progress of a call attempt. This is used for calls that are not otherwise classified as something else.

There’s one major difference between these two messages that is worth knowing. Essentially, 180 Ringing tells the UA to create a local dial-tone. The 183 Session Progress message allows for both regional ring-back and carrier announcements as well.

What is 487 request terminated?

The 487 Request Terminated is another message that you might get while using a SIP device. It means that a previous request was terminated. It could be used to show a request that’s been terminated by the user or by an action taken by the application.

This is a response code that will get sent to the client when the client sends a cancel request. It’s something that you might want to keep in mind if you’re someone who uses SIP devices fairly often.

It’s important to note, this isn’t a technical problem. When you see a 487 message, it doesn’t mean that your application isn’t working correctly. It just means that the person you tried to contact declined the request. They could’ve done that on their own or the application they’re using could’ve done it automatically for them.

Is 180 ringing mandatory?

No, 180 ringing is not mandatory. A connection can be formed between two SIP devices without one. With that in mind, the A-side should be prepared to receive a 200 code as the first response. Or, another response, such as a 400 error code could also be the first response between two SIP devices.

What is early media in SIP?

Early media is the ability of two different devices to communicate before a call is actually established. More specifically this occurs when media begins to flow before the call is actually connected.

These channels are used to provide the ringtone that a caller hears. They’re usually not generated by the caller’s endpoint or through any other queuing services. For example, hold music isn’t included in SIP early media.