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.
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 |
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.
Why: A simple comparison tells you whether to troubleshoot your device or the website.
Do this:
Ctrl + Shift + N on Windows or Command + Shift + N on macOS.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.
Why: VPNs, proxies, extensions and a temporary router problem can prevent Chrome from reaching one or more websites.
Do this:
chrome://extensions, switch off extensions, and test again. Turn extensions back on one at a time to find the conflict.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.
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:
ipconfig /flushdns 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.
Why: A website can be online while its domain still points to the wrong server or has incomplete DNS records.
Do this:
www, then with www. Note whether both versions behave the same way.nslookup -type=NS example.com www record.ns1.fastnsdns.com and ns2.fastnsdns.com. Confirm the spelling before saving a 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.
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:
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.
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:
wp-admin opens, go to Plugins > Installed Plugins and deactivate the plugin updated or installed just before the timeout. Test the front end.wp-content/plugins, for example from plugin-name to plugin-name-disabled. Renaming the folder disables that plugin without deleting its settings.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.
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:
www.nslookup result and the public IP that was tested.This evidence lets the host start with the relevant layer instead of asking you to repeat unrelated browser steps.
After making a change, verify the result in this order:
www if both are configured.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.
| 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 |
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.
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.
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.
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.
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
Compare zoho mail alternatives for Indian businesses by rupee cost, IMAP access and mailbox limits,…
Compare Wix alternatives for Indian small businesses: see 3-year rupee costs, WordPress hosting, migration limits,…
Titan email price in India explained with mailbox costs, features, team totals and a comparison…
HostKarle vs Bluehost compares Indian shared hosting prices, renewal bills, email, SSL, backups, panels and…
Learn how to write blog in hindi with WordPress, Hindi typing tools, domain and hosting…
Compare Google Workspace alternatives in India by yearly rupee cost, email features and migration effort…
This website uses cookies.