ERR_CONNECTION_TIMED_OUT: Fix in Chrome

This guide walks you through the most effective fixes for the “ERR_CONNECTION_TIMED_OUT” error in Google Chrome. This error appears when your browser tries to reach a website but the server doesn’t respond in time, and it can affect a single site or all sites. The steps below cover the most common causes, from simple browser issues to network and DNS problems, and are ordered from quickest to most involved.

What You’ll Need

Access to your router (for a restart, if needed)
Administrator rights on your computer (for some steps)
Your network password (in case you need to reconnect)

Step-by-Step

Check if the site is down for everyone. Open a different browser (Firefox, Edge, Safari) or use your phone on the same Wi-Fi to visit the same URL. If the site loads there, the problem is likely with Chrome or your computer. If it doesn’t load anywhere, the website itself may be down, or your internet connection is the issue.
Restart Chrome completely. Close all Chrome windows and tabs, then reopen Chrome. If the error persists, force-quit Chrome. On Windows, press Ctrl+Shift+Esc to open Task Manager, find Chrome in the list, select it, and click “End task.” On Mac, press Cmd+Q while Chrome is in the foreground, then reopen it.
Restart your router and modem. Unplug the power from your modem and router. Wait 30 seconds, then plug the modem back in first. Wait for it to fully boot (usually 1-2 minutes), then plug in the router. Once the lights stabilize, try loading the page again. This clears temporary network glitches.
Disable Chrome extensions. Type chrome://extensions in the address bar and press Enter. Toggle off all extensions, or click “Remove” for ones you don’t recognize. Then reload the page. If it works, re-enable extensions one by one to find the culprit. A problematic ad-blocker, VPN, or privacy extension is a common cause.
Clear Chrome’s cache and cookies. Click the three-dot menu (top-right), go to “More tools” > “Clear browsing data.” Set the time range to “All time,” check “Cached images and files” and “Cookies and other site data,” then click “Clear data.” This removes corrupted data that can cause timeouts.
Flush your DNS cache. DNS translates website names to IP addresses. A corrupted cache can cause timeouts. Open Command Prompt (Windows) by typing “cmd” in the Start menu and running as administrator, or Terminal (Mac/Linux). Type ipconfig /flushdns on Windows, or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on Mac, and press Enter. Then restart Chrome.
Change your DNS server. Your ISP’s DNS may be slow or unreliable. Switch to a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). In Windows, go to Network Settings > Wi-Fi/Ethernet > “Change adapter options,” right-click your connection, select Properties, then “Internet Protocol Version 4 (TCP/IPv4)” and enter the new DNS addresses. On Mac, go to System Settings > Network > your connection > Details > DNS, and add the addresses.
Disable VPN or proxy settings. If you use a VPN, turn it off temporarily and try the site. Also check if a proxy is enabled. In Chrome, go to Settings > System > “Open your computer’s proxy settings.” Ensure “Automatically detect settings” is on and no manual proxy is set (unless you know you need one).
Reset Chrome settings. Go to Chrome Settings > Reset and cleanup > “Restore settings to their original defaults.” This disables extensions, clears temporary data, and resets search engines, but does not remove bookmarks or passwords. Try the site again after this.
Temporarily disable your firewall or antivirus. Some security software blocks connections. If you have third-party antivirus, pause it briefly. On Windows, you can also temporarily turn off Windows Defender Firewall (Control Panel > System and Security > Windows Defender Firewall > Turn off). Do this only for a test, and re-enable immediately. If the site loads, add Chrome to the firewall’s allowed list.
Check your hosts file. A misconfigured hosts file can block sites. On Windows, it’s at C:\Windows\System32\drivers\etc\hosts. On Mac/Linux, it’s /etc/hosts. Open it with Notepad (as admin) or a text editor. Look for any lines with the site’s domain that aren’t preceded by “#”. If you see an entry like 127.0.0.1 example.com, that’s blocking it. Delete that line and save.
Use Chrome’s built-in network diagnostics. Type chrome://net-internals in the address bar. Go to “DNS” and click “Clear host cache.” Then go to “Sockets” and click “Flush socket pools.” Restart Chrome and try again.

Common Mistakes

Only restarting the browser, not the computer. A full system restart clears many network-related processes that a browser restart won’t.
Skipping the router restart. Many people assume the problem is on their computer, but the router is often the source. Always test another device first.
Clearing cookies while logged in. Clearing cookies will log you out of most sites. This is fine, but you’ll need to log back in. It’s a necessary step if cache corruption is suspected.
Changing DNS incorrectly. Entering a wrong IP address (like 8.8.8.8 instead of 8.8.8.8) or forgetting to set both primary and secondary can leave you without internet. Double-check the numbers.
Disabling the firewall permanently. Turning off your firewall “just to test” and forgetting to turn it back on is a serious security risk. Always re-enable it as soon as the test is done.

Tips

Try Incognito Mode first. Press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac). If the site loads there, the issue is almost certainly an extension or cached data in your normal profile.
Use a different Chrome profile. Click your avatar in the top-right, then “Add” to create a new profile. Test the site there. This isolates profile-specific corruption.
Check your date and time. Incorrect system time can break HTTPS connections and cause timeouts. Right-click the clock and select “Adjust date/time.” Ensure “Set time automatically” is on.
Run Windows Network Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters > “Network Adapter” and run it. It can automatically detect and fix common issues.
Update Chrome. Go to chrome://settings/help. Chrome will automatically check for updates and install them. An outdated browser can have bugs that cause timeouts.

Troubleshooting

If the error persists after trying all the steps above, here are additional things to check:

Test on a different network. Use your phone’s mobile hotspot to connect your computer. If the site loads on the hotspot, the problem is with your home network or ISP, not your computer. Contact your ISP.
Check if the error is only on one site. If only one specific website times out, the site’s server may be down, or it may be blocking your IP address. Try accessing it via a different network (like your phone’s data) to confirm.
Look for recent system changes. Did you install new software, a new router, or change network settings recently? Reverting those changes can help.
Check for malware. Run a full system scan with Windows Defender or your antivirus. Malware can hijack network settings and cause timeouts.
Reset the network stack. On Windows, open Command Prompt as administrator and run these commands one by one, pressing Enter after each: netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew, ipconfig /flushdns. Restart your computer afterward.
Try a different browser entirely. If the site loads in Firefox or Edge but not Chrome even after a reset, consider uninstalling Chrome completely (back up bookmarks first) and reinstalling the latest version.

Frequently Asked Questions

Why does this error only happen in Chrome and not other browsers?

This usually points to a Chrome-specific issue like a corrupted cache, a problematic extension, or a misconfigured proxy setting within Chrome. The steps to clear cache and disable extensions are the most likely fixes.

Will clearing my cache log me out of websites?

Yes, clearing “Cookies and other site data” will log you out of most sites. You’ll need to log back in after clearing. This is a necessary trade-off to fix the timeout issue.

Is changing my DNS safe?

Yes, using a public DNS like Google or Cloudflare is safe and often faster than your ISP’s default. It’s a standard practice and doesn’t affect your security. You can always revert to “Obtain DNS server address automatically” to go back.

How do I know if the website is down and not my computer?

The easiest way is to try the site on another device (phone, tablet) using a different network (mobile data, not your Wi-Fi). If it fails there too, the site is down. You can also use an online service like “isitdownrightnow” to check.

What does “ERR_CONNECTION_TIMED_OUT” actually mean?

It means your browser sent a request to the server but didn’t receive a response within a set time limit (usually 30 seconds). The server may be overloaded, offline, or your connection to it is blocked or too slow.

Will resetting Chrome delete my bookmarks and passwords?

No. “Restore settings to their original defaults” only resets settings like your homepage, search engine, and pinned tabs. It disables extensions and clears temporary data, but your bookmarks, history, and saved passwords are not deleted.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →