err_connection_timed_out means Chrome tried to connect to a website but did not receive a response in time. This guide separates visitor-side fixes from checks for your own website, so you can find out whether the problem is your device, DNS, network, firewall or hosting.
What ERR_CONNECTION_TIMED_OUT means
Chrome describes ERR_CONNECTION_TIMED_OUT as a page that took too long to connect; the cause may be a slow connection or a busy website. It is different from ERR_NAME_NOT_RESOLVED, which means the hostname could not be resolved, and ERR_INTERNET_DISCONNECTED, which means the device has no internet connection. You can read Google’s explanation of common Chrome connection errors.
The message does not identify the exact cause. A timeout can happen before DNS finishes, while your browser is opening a connection, or while the website is trying to respond. That is why testing from another device or network is more useful than repeating refresh again and again.
| What you see | What it usually suggests | First useful test |
|---|---|---|
| One website times out on every device | The website, its DNS or its server path needs checking | Test the domain on mobile data and a hosting checker |
| Many websites time out on one Wi-Fi connection | Router, ISP, DNS, VPN or proxy problem | Try mobile data, then restart the router |
| Only Chrome shows the error | Extension, Secure DNS, proxy or Chrome profile issue | Open the page in Incognito |
| Your site times out for visitors but you can log in | DNS, firewall, plugin or front-end request issue | Check DNS and test from another network |
What you need before troubleshooting
Keep the exact URL, the time you first noticed the problem and the network you were using. If it is your website, also keep access to your domain registrar, hosting panel and WordPress administrator account.
For a Windows check, you need Command Prompt. For a site-owner check, have a recent copy made with your hosting panel’s self-service backup tools before changing plugins, themes or DNS. Do not change several things at once; otherwise you will not know which change fixed the timeout.
Step 1: Find out whether the problem is local
Why: A simple comparison tells you whether to troubleshoot your device or the website.
Do this:
- Open two or three other websites in the same browser.
- Open the failing URL in an Incognito window with
Ctrl + Shift + Non Windows orCommand + Shift + Non macOS. - Try another browser on the same device.
- If possible, turn off Wi-Fi on your phone and open the URL using mobile data.
- If it is your website, run the domain through HostKarle’s hosting checker.
Success looks like: The page opens in another browser, Incognito, device or network. That points to a local setting. If it fails everywhere, continue with the website and DNS checks below.

Step 2: Apply the quick visitor fixes
Why: VPNs, proxies, extensions and a temporary router problem can prevent Chrome from reaching one or more websites.
Do this:
- Close the timed-out tab, quit Chrome completely and open it again.
- Pause any large download and close tabs or apps that are using the connection.
- Restart the Wi-Fi router. Wait until the connection is available, then try the URL again.
- Disconnect a VPN temporarily. If you use a proxy, open Chrome Settings, search for proxy, and review the operating system’s proxy settings.
- Open the URL in Incognito. If it works there, open
chrome://extensions, switch off extensions, and test again. Turn extensions back on one at a time to find the conflict. - In Chrome, open Settings > Privacy and security > Delete browsing data. Clear cached images and files, then restart Chrome.
Do not leave security software or a VPN disabled permanently. Use a temporary test to identify the cause, then turn protection back on and adjust only the setting that is blocking the connection.
Success looks like: The page loads in normal Chrome after the router, VPN, proxy or extension change. If Incognito also times out, move to DNS and network checks instead of deleting more browser data.
Step 3: Flush DNS and test a different resolver
Why: Your device or network may be using an old or incorrect DNS answer. Flushing the local resolver cache makes Windows request the hostname again.
Do this on Windows:
- Search for Command Prompt.
- Right-click it and select Run as administrator.
- Run:
ipconfig /flushdns
- Wait for the message that the DNS resolver cache was successfully flushed.
- Close and reopen Chrome, then test the URL.
Microsoft lists /flushdns as the ipconfig option for flushing the DNS resolver cache while troubleshooting name-resolution problems. If you want to inspect the current network values first, run ipconfig /all.
If it still fails: Test another DNS resolver. In Chrome, open Settings > Privacy and security > Security > Advanced, find Use secure DNS, and temporarily turn it off or select your current service provider. Google documents these Secure DNS controls in its Chrome safety settings.
You can also change the device or router DNS after noting the current settings. Google’s documented public IPv4 addresses are 8.8.8.8 and 8.8.4.4; its Public DNS setup guide includes Windows, macOS, ChromeOS, router and mobile instructions. Use two different addresses, test the site, and restore the previous values if the change does not help.
Success looks like: The URL opens after the cache flush or after changing the resolver. If only changing DNS helps, investigate the domain’s DNS records if you own the website; do not assume the web server is the problem.
Step 4: Check the domain and nameservers if it is your website
Why: A website can be online while its domain still points to the wrong server or has incomplete DNS records.
Do this:
- Open the domain without
www, then withwww. Note whether both versions behave the same way. - Run this command in Command Prompt, replacing the example domain:
nslookup -type=NS example.com
- Compare the returned nameservers with the nameservers shown in your domain account and hosting panel.
- Check that the domain’s A or AAAA record points to the current hosting destination. If you recently moved the website, check both the root domain and the
wwwrecord. - If you use HostKarle nameservers, the current pair is
ns1.fastnsdns.comandns2.fastnsdns.com. Confirm the spelling before saving a change. - Test again from mobile data and from a second Wi-Fi connection. A result that changes by network usually needs DNS or routing investigation rather than a WordPress change.
Success looks like: The root domain and www resolve consistently to the intended hosting service, and the site opens from more than one network. DNS edits can take time to appear in different resolvers, so record the old values before changing anything.
Step 5: Check whether your IP is blocked
Why: A firewall can reject or ignore requests from one public IP while the same website works from mobile data or another broadband connection.
Do this:
- Compare the result on your usual Wi-Fi and mobile data.
- If the website works on mobile data but not Wi-Fi, restart the router and test once more.
- Ask your host to check whether your current public IP is blocked by a firewall or security rule. Send the domain, exact URL, approximate time, public IP and the result from the second network.
- If you manage the server or hosting panel yourself, review the firewall’s blocked-IP list and remove only the confirmed false block.
- For background on checking an address block, see how to unblock an IP address from cPanel. HostKarle accounts use DirectAdmin, so use the equivalent firewall or security screen in your own panel.
Success looks like: The page loads again on the affected network after the correct IP block is removed or the network path is corrected. Never add a broad allow rule for every address; allow only the IP you have verified.
Step 6: Isolate WordPress plugins, themes and heavy requests
Why: If DNS is correct but your own WordPress website times out, a plugin, theme, PHP request or unusually heavy page can stop the application from completing a response.
Do this:
- Make a current copy with your hosting panel’s self-service backup tools.
- If
wp-adminopens, go to Plugins > Installed Plugins and deactivate the plugin updated or installed just before the timeout. Test the front end. - If the dashboard does not open, use your hosting file manager or FTP to rename the suspected folder inside
wp-content/plugins, for example fromplugin-nametoplugin-name-disabled. Renaming the folder disables that plugin without deleting its settings. - If the timeout remains, temporarily switch to a default WordPress theme. Restore the original theme after testing.
- Re-enable plugins one at a time and load the affected page after each change. Check the page’s PHP error log if your hosting panel provides one.
- If a database error appears instead of a timeout, use the steps in our guide to fixing a WordPress database connection error.
WordPress’s official troubleshooting guidance also recommends deactivating plugins and testing a default theme to isolate a conflict. Keep a note of each change and return the site to the last working configuration once you identify the cause.
Success looks like: The website loads after one plugin or theme is disabled, or the log identifies the request that is taking too long. Update, replace or reconfigure the specific component after confirming it is the cause.
Step 7: Know when to contact your hosting provider
Why: A host can check DNS records, firewall logs, web-server connections and account-level errors that are not visible in Chrome.
Contact your host when the domain times out from several unrelated networks, DNS points to the correct destination but no page responds, or you have already isolated the issue to the hosting account. Include:
- The complete URL, including whether it uses
www. - The exact error code and a screenshot if useful.
- Your local time and time zone; for India, write the time as IST.
- Results from Wi-Fi, mobile data, Incognito and another browser.
- The
nslookupresult and the public IP that was tested. - Any recent DNS, plugin, theme or domain changes.
This evidence lets the host start with the relevant layer instead of asking you to repeat unrelated browser steps.
Verify the fix
After making a change, verify the result in this order:
- Open the original URL in a normal Chrome window.
- Open the same URL in Incognito.
- Test both the root domain and
wwwif both are configured. - Test from Wi-Fi and mobile data.
- Open one internal page, the WordPress login page and a page with images or a form.
- If you changed a plugin, theme, DNS record or firewall rule, check that the rest of the website still works.
If only one test passes, the error is not fully resolved. Keep the working and failing combinations in your notes and share them with your host or developer.
Troubleshooting checklist
| Result after a check | Next action |
|---|---|
| Incognito works, normal Chrome fails | Disable extensions and review cached data |
| Every browser fails on one Wi-Fi network | Restart the router, review VPN/proxy and try another DNS resolver |
| Mobile data works but broadband fails | Check the broadband public IP, firewall block and route |
| All networks fail after a nameserver change | Verify nameservers and A/AAAA records with the registrar and host |
| DNS resolves correctly but WordPress alone fails | Test the last plugin/theme change and review the PHP error log |
| The site works for some people but not you | Compare DNS answers and check whether your public IP is blocked |
FAQ
What is the fastest fix for ERR_CONNECTION_TIMED_OUT?
First test the page in Incognito and on mobile data. If it works there, inspect extensions, VPN, proxy and local DNS; if it fails everywhere, check the website’s DNS, firewall and hosting.
Why does Chrome say “This site can’t be reached” and take too long to respond?
Chrome could not complete a connection to the website within the expected time. The cause can be your network, DNS, a firewall rule or a website that is not responding, so the error message alone cannot identify which one it is.
Does flushing DNS fix a connection timeout?
It can fix a stale or incorrect DNS answer on your device, but it cannot repair a blocked IP, wrong nameserver or WordPress plugin problem. Run ipconfig /flushdns, test again, and continue with the other checks if the timeout remains.
Why does my website work on mobile data but not Wi-Fi?
The Wi-Fi network may have a DNS, proxy, routing or public-IP block. Restart the router, test another resolver, and ask the host to check the Wi-Fi network’s public IP if the website works everywhere else.
Can a WordPress plugin cause ERR_CONNECTION_TIMED_OUT?
Yes. A plugin or theme can create a long-running request or conflict that prevents WordPress from completing the page. Make a backup, deactivate the newest or most suspicious component, and re-enable items one at a time to find it.
DONE fix-err-connection-timed-out words=2171
Want to partner with us, suggest a resource or advertise on this blog? Email partnerships@hostkarle.in



