Are you seeing the “ERR_CONNECTION_TIMED_OUT” error in your browser? Not a very helpful error message, is it? If you are a daily WordPress user, then it’s always good to be aware of common errors like these that might prevent you from getting access to your website.
In today’s post, we’re going to take a deep dive into the “ERR_CONNECTION_TIMED_OUT” error and examine why you might see this and what you can do to fix it quickly. Simply put, it’s an indication that the system is unavailable and the time given for one to connect has elapsed, and now the request has timed out. But what does that actually mean?
Let’s find out!
We’ve taken our knowledge of effective website management at scale, and turned it into an ebook and video course. Click here to download the The 2020 Guide to Managing 40+ WordPress Sites!
What is the ERR_CONNECTION_TIMED_OUT Error?
An ERR_CONNECTION_TIMED_OUT error typically means there is something wrong with your local network connection. However, that’s not always the case.
According to the WordPress support documentation, a connection timed out error appears when your website is trying to do more than your server can manage. It’s particularly common on shared hosting where your memory limit is restricted.
When you visit a website and it doesn’t load, your browser will try for around 30 seconds or so until it terminates the connection. After which it will return an “ERR_CONNECTION_TIMED_OUT” error, indicating a communication problem. In Google Chrome you might see this as “This site can’t be reached. Domain.com took too long to respond.”
Due to all the different web browsers, operating systems, and servers, the error can present itself in a number of different ways. But most of them have the same or similar meaning. “ERR_NETWORK_CHANGED” and “ERR_CONNECTION_REFUSED” are two very closely related errors that can usually be solved with the same troubleshooting steps below.
Below are a few examples of how the error might present itself in different browsers.
In Mozilla Firefox the error will show as “The connection has timed out.” The server at domain.com is taking too long to respond.
In Microsoft Edge, the error will show as “Hmmm… can’t reach this page. Domain.com took too long to respond.” In Edge, however, it does also contain the “ERR_CONNECTION_TIMED_OUT” error.
In Safari, the error will show as “Safari Can’t Open the Page. Safari can’t open the page domain.com because the server where this page is located isn’t responding.”
How to Fix the ERR_CONNECTION_TIMED_OUT Error
Where should you start troubleshooting if you see this error on your WordPress site? Without a great deal of context, it can sometimes be frustrating and overwhelming where to even begin. Typically these are either client-side problems (issues with your network connection or firewall) or an issue with the server at which the site is hosted (memory limits, execution times, etc.).
1. Check Your Connection
Google Chrome, Firefox, and Edge all recommend that you should check your network connection. While this might sound obvious, they all point to checking your connection first as it’s one of the most common reasons for the error. Here are a few things we recommend:
- Restart your home or office router. This only takes a few minutes and solves more problems than a lot of people would like to admit. To completely power cycle it, disconnect the power supply and then wait 30 seconds before plugging it back in.
- Check to see if you’re on a bad or slow wifi connection. This is a common occurrence on busy public wifi hotspots such as coffee shops or airports.
2. Disable Firewall and Antivirus Software Temporarily
Firewalls and antivirus software are intended to protect users and their systems. They scan your device regularly and automatically block any suspicious activity. However, this type of security can at times lead to connection issues.
This is because firewalls can often block pages they don’t need to or reject content that is completely safe. We’ve seen this happen many times with software like AVG. To check whether this is the case for you, try disabling your firewall and antivirus programs. Of course, this is only advised if you know for sure that the site you’re intending to visit is safe.
Additionally, you should only disable this kind of software temporarily. Switch it back on after you’ve finished checking to see whether the error has been resolved, so you don’t become vulnerable to attacks. If you repeatedly encounter errors because of your firewall or antivirus software, you may want to consider changing what you’re using.
These types of tools also have what is called a “false-positive” report you can fill out. If you’re 100% positive that a site your visiting is blocked and shouldn’t be, you can let the software developer know. Here are a few quick links:
3. Disable Proxy Settings
Sometimes you might see the ERR_CONNECTION_TIMED_OUT error if you are utilizing a proxy service. This is usually pretty rare, especially on the client-side. However, one might have been set without you even knowing it. To disable or check to ensure no proxy settings are enabled, follow these steps.
Access the Settings menu in your Chrome browser. This will open up the complete menu of options. Under the System section (you’ll need to click Advanced at the bottom to see this), you should find an entry titled Open proxy settings. By selecting it, you’ll be taken to the corresponding menu:
Your next step depends on the system you’re currently using. Windows users will want to click on LAN Settings and uncheck the Use proxy server for LAN option. If you’re a Mac user, you should immediately find yourself in the relevant menu. You’ll then have to uncheck all selectable proxy protocols and check to see if the ERR_CONNECTION_TIMED_OUT message has been resolved.
If you’re on Windows, you will see a “Local Area Network (LAN) Settings” window appear. You will want to confirm that the “Use a proxy server for your LAN” option is unchecked.
The same goes if you’re using a VPN like ExpressVPN or TunnelBear. Make sure you’re not connected by accident.
4. Change DNS Servers
The next thing you can try is changing your DNS servers. By default, DNS servers are automatically assigned by your ISP. But you could try temporarily changing these to a public DNS server, such as Google or Cloudflare.
- Some prefer to use Google’s public DNS (22.214.171.124 and 126.96.36.199) long-term due to them sometimes being more reliable.
- Cloudflare also offers secure and blazing fast free DNS (188.8.131.52 and 184.108.40.206) which we will be using in this example. If you want to use Google’s the steps are the same, you simply replace the DNS server addresses with Googles.
Tip: If you’re already using a free DNS server and having issues, removing it and defaulting back to your ISP’s DNS servers also sometimes fix things.
Google and Cloudflare aren’t perfect 100% of the time and there have been a few instances where we’ve noticed switching back has resolved the issue. This is especially true if you’re using a Wifi hotspot in an airport or coffee shop.
In Windows simply open up Command Prompt by pressing the Windows logo key and R. Then type “control panel” and hit Enter.
Click on “Network and Internet” and then “Network and Sharing Center.” On the left-hand side, click on “Change Adapter Settings.”
Right click on your current connection, this will either be Local Area Connection or Wireless Network Connection based on how you’re connecting. Then click on “Properties.”
Select Internet Protocol Version 4 (or Version 6 if desired) and click on “Properties.”
Make a note of any existing settings in case you need to revert back. Click “Use the following DNS server addresses.” Enter the following, or replace the existing with these:
Click OK, then Close. Restart your browser.
To change DNS servers on a Mac, go to System Preferences…
Click on the network icon and then click “Advanced.”
Click on the “DNS” tab.
Then add Cloudflare’s DNS server addresses.
5. Flush/Renew DNS
You can also try flushing your local DNS cache. This is similar to clearing your browser cache. It could be that the site you’re trying to visit isn’t resolving to the correct IP address. If you’ve just migrated your WordPress site to a new host, it’s important to wait for things to fully propagate. This can sometimes take up to 24 hours, although it can be as little as a few minutes. This depends on your DNS provider and the TTL value of your DNS records.
In Windows simply open up Command Prompt and enter the following:
You should see a “Successfully flushed the DNS resolver Cache” if it worked.
For macOS users, you can enter the following in the terminal:
Note: There is no success message on Macs.
6. Check Your Hosts File
Every computer has what they call a local hosts file. This is a file that contains manual DNS entries which are mapped to specific IP addresses. Typically this is only edited when you want to preview your DNS before switching over domains to a new host. Or perhaps you have a local development site running using a tool like DevKinsta, Vagrant or Docker.
There is a multitude of different ways this file could have been changed or edited. Therefore, it’s always good to check to ensure the website you’re trying to access isn’t in there. Just follow the steps below.
The hosts file typically requires additional access. So the first step is to open up your text editor as an administrator. Simply click on your start menu, search for your text editor, right-click on it and select “Run as administrator.” This can be done in any text editor such as Notepad, Notepad++, Atom, etc. We are using Sublime in our example below.
Within your text editor click File → Open and browse to the following location:
Click on the hosts file and “Open.”
Double-check and make sure the website you’re trying to visit isn’t listed in there. If it is, remove it.
To check your hosts file on a Mac, we recommend getting Gas Mask. It’s a free application which can be used as hosts file manager, hosts files editor, and switch between them. It makes everything quick and easy! Otherwise, you can follow the steps below to edit your hosts file on Mac manually.
Go to Utilities and then click on “Terminal.”
Enter in the following command and press Enter (you will most likely be prompted for your administrator password as well).
sudo nano /private/etc/hosts
Double-check and make sure the website you’re trying to visit isn’t listed in your hosts file. If it is, remove it.
7. Check the DNS of Your Domain
You should also verify that the DNS of your domain is correctly pointed to your hosting provider. If you’re a Kinsta client we have an in-depth post on how to point your domain and or DNS to Kinsta. If you recently migrated your WordPress website to a new host, it could be the DNS was cached incorrectly on your computer. In which case, step 5 above should resolve that. Or it may simply be too soon and you need to wait a few hours for the DNS to fully propagate.
8. Clear Browser Cache
Web browsers store information in cache on your computer. This includes your browsing history, saved login data, and cookies – all of which are recorded in order to load the relevant pages more quickly the next time they’re visited.
Although they’re useful, caches can cause numerous issues when they become outdated. Fortunately, this problem is easily solved by clearing your cache.
But before you do that, you can easily check to see if it’s a browser cache issue by first opening up your browser in incognito mode. Or you can try a different browser. If you’re still seeing the error, then you will want to proceed with clearing your cache.
In this example, we’ll be using Google Chrome. Begin by opening up the primary menu (in the top-right corner of your browser window). From there, select More Tools: You can then click on Clear browser data.
On the resulting page, you’ll need to make sure that all listed file categories are selected. If they aren’t, Chrome won’t be able to empty the entire cache. Instead, it will simply remove the most recent entries, which won’t result in the desired effect:
An alternative method of completing this process is to enter the following URL into your address bar:
The resulting screen should grant you access to the same options we’ve outlined above. Here are some other helpful links for clearing cache.
- How to Force Refresh a Single Page for All Browsers
- How to Clear Cache for Google Chrome
- How to Clear Cache for Mozilla Firefox
- How to Clear Cache on Mac (Safari)
- How to Clear Cache for Internet Explorer
- How to Clear Cache for Microsoft Edge
- How to Clear Cache for Opera
9. Look at The Maximum Execution Time
The rest of the troubleshooting steps we’ll be diving into are those that have to do with the configuration of your WordPress site or server that may help fix the “ERR_CONNECTION_TIMED_OUT” error.
The first is the maximum execution time set for your site. On most servers, the default time is set to 30 seconds. This is the amount of time a PHP script is allowed to run (after which it times out). On shared hosts, this is typically set low or left at the default.
You can’t easily modify this from WordPress as the php.ini file is located on your server. To modify this, we recommend reaching out to your hosting provider to see if they can help. At Kinsta, we set the default maximum execution time to 300 seconds.
If you want to try and modify this yourself, it can usually be done with one of the following options. Both will depend on how your hosting provider configures their servers.
Option 1 – Modify Max Execution Time in php.ini File
If you have a
php.ini file in your home directory, find the
max_execution_time parameter and modify it. For example, if it’s set to 30 seconds, you can increase it to 300 seconds.
max_execution_time = 300
Option 2 – Modify Max Execution Time in .htacess File
If the above option doesn’t work, you might be able to change it within your .htaccess file. Just like with the
php.ini file, this is typically located within your home directory. Place the following in the top of your
php_value max_execution_time 300
10. Temporarily Disable Your Plugins
As with most WordPress errors, a plugin can definitely be the root of the problem. To determine if that’s what’s happening, you’ll need to disable all of your site’s plugins. However, if you’re getting the “ERR_CONNECTION_TIMED_OUT” error it means you don’t have access to your WordPress admin area. This means you will need to SFTP into your site. We recommend using FileZilla.
Once your SFTP client is ready, connect to your website through it and navigate to your WordPress root folder. In case you can’t find it, it’s usually called public_html, html, public, www, or your site’s name. If you’re a Kinsta client, it’s your public folder.
Open that folder, and navigate to the wp-content directory. Inside, you’ll see a folder called plugins, which contains individual subdirectories for each of the plugins installed on your site (both active and inactive).
What you’re going to do now is right-click on the plugins folder, and rename it to something else. We recommend plugins.old or plugins.deactivated, so you can easily recognize it later.
WordPress will now not be able to find any of your plugins. When that happens, it will automatically disable those plugins.
Now, try accessing your WordPress dashboard. If the timeout error is gone, then you can assume that one of your plugins was the culprit. All you have to do is figure out which one was at fault.
Return to the wp-content directory, and rename your original plugins folder correctly. Then, you’ll need to disable each of your plugins one by one, until you find the culprit.
To do this, open the wp-content/plugins directory. Inside, you’ll find one folder for each of your plugins. The process you’re going to follow is much the same as before:
- Start with the first folder, and rename it to anything you like.
- Check your website to see if the error is gone.
- If it isn’t, return the plugin folder from the previous step to its original name.
- Move on to the next plugin on your list, repeating the above steps.
This process can take a while if you have a lot of plugins, but it’s vital to check each plugin in turn. If at any point you identify the plugin that’s causing the error, you can uninstall it or replace it with another tool.
If you make it to the end of these steps without finding a solution, you can move on to the next stage of troubleshooting.
11. Temporarily Revert to Default Theme
Now that you’ve ruled out your plugins as the cause of the timeout error, it’s time to do the same with your active theme. In fact, your theme could also be creating compatibility issues.
Unfortunately, the process doesn’t work the same as above. WordPress won’t revert to the default theme if simply rename the theme folder, you would end up with an error like “The theme directory “theme name” does not exist.” Or if you try to rename the entire theme directory folder, you end up with “ERROR: The themes directory is either empty or doesn’t exist. Please check your installation.”
Click into the “wp_options” table, then click on the “Search” tab. You will want to search under the “option_name” for template.
Under the “option_value” column you will see the current name of your theme. Change this to one of the default themes, such as “twentynineteen.”
Check your website again to see if this has fixed the error. If it did, it simply means it’s a problem with your WordPress theme and you might want to try reinstalling it or reverting to your most recent backup.
12. Increase the Memory Limit
WP_MEMORY_LIMIT parameter allows you to specify the maximum amount of memory that can be consumed by PHP. If you are using shared hosting, it’s most likely set to a low value such as 64M. At Kinsta, we set the default memory limit to 256M.
define( 'WP_MEMORY_LIMIT', '256M' );
Not sure what your current PHP memory limit is set to? If you have access to your WordPress dashboard and are running WordPress 5.2 or above, you can see the PHP memory limit under the “Site Health” tool.
Connection and timeout errors are never fun to troubleshoot, but hopefully, you have a little more knowledge in your toolbelt now to help resolve it quickly.
It’s important to remember that the “ERR_CONNECTION_TIMED_OUT” error be a result of a client-side problem such as your network connection, or an issue with the server where your WordPress site is hosted. Have any other tips to resolve this error? Let us know below in the comments.
(Suggested reading: Learn how to fix the ERR_CACHE_MISS error in Chrome)
Save time, costs and maximize site performance with:
- Instant help from WordPress hosting experts, 24/7.
- Cloudflare Enterprise integration.
- Global audience reach with 32 data centers worldwide.
- Optimization with our built-in Application Performance Monitoring.