ERR_CONNECTION_TIMED_OUT in Chrome? 8 Fixes That Work

Seeing the dreaded ERR_CONNECTION_TIMED_OUT error in Chrome can be frustrating, especially when every other app on your device seems to work fine. This complete err_connection_timed_out chrome fix guide walks you through the eight most effective solutions, from quick browser tweaks to deeper network settings, so you can get back to browsing in minutes. The error simply means Chrome tried to reach a website but gave up after waiting too long for a response — and the cause can be anything from a stale cache to a broken DNS setting or a router hiccup. Work through the fixes below in order, starting with the easiest.

• What Causes ERR_CONNECTION_TIMED_OUT in Chrome?
• Fix 1: Restart Chrome, Your Device, and Your Router
• Fix 2: Clear Chrome’s Cache and Cookies
• Fix 3: Disable Extensions and Open an Incognito Window
• Fix 4: Change Your DNS Servers
• Fix 5: Flush Chrome’s Socket Pools and Host Cache
• Fix 6: Check Your Firewall and Antivirus
• Fix 7: Disable Proxy and Reset LAN Settings
• Fix 8: Reset Chrome Settings and Update Chrome
• Advanced: When the Error Persists on Every Device
• FAQs
• Conclusion

What Causes ERR_CONNECTION_TIMED_OUT in Chrome?

Before diving into fixes, it helps to understand what this error actually means. When you type a web address, Chrome sends a request to the site’s server and waits for a reply. If no reply arrives within a certain time window (roughly 30 seconds), Chrome stops waiting and shows ERR_CONNECTION_TIMED_OUT.

The most common causes include:

• Network connection problems: A weak Wi-Fi signal, an overloaded router, or an ISP outage can stop requests from ever reaching the server.
• Stale or corrupted browser cache: Cached files that conflict with the current version of a site can break the connection.
• DNS issues: If your DNS server cannot resolve the site’s domain name into an IP address, Chrome has nowhere to send the request.
• Firewall or antivirus interference: Security software sometimes blocks Chrome’s network access after an update.
• Proxy or VPN misconfiguration: A proxy server that is down or misconfigured will swallow your requests.
• Server-side problems: Sometimes the website itself is down or overloaded, and nothing on your end is wrong.

The key to an effective err_connection_timed_out chrome fix is working from the simplest explanation outward. Start with browser-level checks, then move to system and network-level fixes.

Fix 1: Restart Chrome, Your Device, and Your Router

This sounds almost too simple, but a restart resolves a surprising number of timeout errors. Temporary network states, stuck background processes, and minor router glitches all disappear with a fresh start.

1. Close Chrome completely. On Windows, open Task Manager (Ctrl + Shift + Esc), end all Chrome processes, then reopen Chrome. On a Mac, right-click the Chrome icon in the dock and choose Quit.
2. Restart your device. A full reboot clears stuck network stacks and refreshes your DHCP lease.
3. Restart your router. Unplug the router’s power cable, wait 30 seconds, then plug it back in. Wait another 1–2 minutes for it to reconnect fully before testing.
4. Try the website again. If the error is gone, a temporary glitch was the culprit.

If only one website is affected while others load fine, check whether that site is down for everyone. You can search for a down-detector service or try opening the site on your phone’s mobile data. If the site is down, no amount of troubleshooting on your end will fix it — you just have to wait.

Fix 2: Clear Chrome’s Cache and Cookies

Chrome stores cached copies of pages, images, and cookies to load sites faster. Over time, these files can become corrupted or outdated, causing connection timeouts on specific sites. Clearing them forces Chrome to fetch fresh data.

1. Open Chrome and press Ctrl + Shift + Delete (Windows/Linux) or Cmd + Shift + Delete (Mac). This opens the “Clear browsing data” dialog.
2. Set the time range to All time.
3. Check Cached images and files and Cookies and other site data. You can leave browsing history checked if you want to keep it.
4. Click Clear data and wait for the process to finish.
5. Close and reopen Chrome, then retry the website.

Note that clearing cookies will sign you out of most websites, so make sure you know your passwords or have them saved in a password manager. If the timeout only happens on one or two sites, you can instead clear data for just those sites: go to Settings > Privacy and security > Third-party cookies > See all site data, search for the site, and delete its entries.

Fix 3: Disable Extensions and Open an Incognito Window

Browser extensions — especially ad blockers, VPN extensions, and privacy tools — can intercept or delay network requests and trigger timeouts. The fastest way to test this is Chrome’s Incognito mode, which disables all extensions by default.

1. Press Ctrl + Shift + N (Windows/Linux) or Cmd + Shift + N (Mac) to open an Incognito window.
2. Visit the site that was timing out. If it loads in Incognito, an extension is almost certainly the problem.
3. Go back to your normal window and open chrome://extensions.
4. Toggle off all extensions, then re-enable them one at a time, testing the site after each one, until you find the culprit.
5. Remove or replace the problematic extension. If it is a VPN extension, check whether its servers are down before blaming the extension itself.

Also check whether you have a system-level VPN running. A VPN that routes traffic through an overloaded or distant server can easily cause timeouts. Disconnect the VPN temporarily and test again.

Fix 4: Change Your DNS Servers

DNS (Domain Name System) translates website names into IP addresses. If your ISP’s default DNS servers are slow or unreliable, Chrome may time out while waiting for the translation. Switching to a fast public DNS service like Google DNS or Cloudflare DNS often fixes the err_connection_timed_out error immediately.

Change DNS on Windows

1. Open Settings > Network & internet > Wi-Fi (or Ethernet, whichever you use).
2. Click your network name, then scroll to DNS server assignment and click Edit.
3. Change the setting to Manual, turn on IPv4, and enter a public DNS: 8.8.8.8 and 8.8.4.4 (Google), or 1.1.1.1 and 1.0.0.1 (Cloudflare).
4. Click Save, then restart Chrome and test.

Change DNS on Mac

1. Open System Settings > Wi-Fi, click Details next to your network.
2. Go to the DNS tab, click the + button, and add 8.8.8.8 and 8.8.4.4.
3. Click OK and test the site.

Change DNS on Android

1. Go to Settings > Network & internet > Private DNS.
2. Select Private DNS provider hostname and enter dns.google or one.one.one.one.
3. Tap Save and retry Chrome.

After changing DNS, it is also worth flushing your system’s DNS cache. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On a Mac, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. If your Wi-Fi itself is acting up on mobile, you may also want to read our guide on how to fix Wi-Fi connected but no internet on Android, since a broken local connection produces the same symptom.

Fix 5: Flush Chrome’s Socket Pools and Host Cache

Chrome maintains its own internal networking layer with pooled connections (sockets) and a host cache. If a pooled connection goes stale, Chrome can keep trying to reuse it and time out repeatedly. Flushing these internal pools is a lesser-known but highly effective err_connection_timed_out chrome fix.

1. In Chrome’s address bar, type chrome://net-internals/#sockets and press Enter.
2. Click Flush socket pools. This closes all idle pooled connections.
3. Next, type chrome://net-internals/#dns and press Enter.
4. Click Clear host cache to wipe Chrome’s internal DNS cache.
5. Restart Chrome and try the website again.

This fix is particularly useful when the timeout affects many sites at once and appeared suddenly, for example right after your network dropped and reconnected. Stale sockets from the old connection keep failing until they are flushed.

Fix 6: Check Your Firewall and Antivirus

After a Chrome or antivirus update, security software sometimes starts blocking Chrome’s network traffic. The result looks exactly like a timeout because Chrome’s requests never leave your machine.

1. Temporarily disable your antivirus web shield. Open your antivirus settings, turn off real-time or web protection for 5 minutes, and test the site. Re-enable protection immediately afterwards.
2. Check Windows Firewall. Go to Control Panel > System and Security > Windows Defender Firewall > Allow an app through Windows Firewall. Make sure Google Chrome is checked for both Private and Public networks.
3. Look for recently installed security software. If the error started right after installing a new antivirus or firewall, check its application rules for Chrome.
4. On a Mac, check System Settings > Network > Firewall and any third-party security apps.

If disabling the antivirus fixes the problem, do not leave protection off. Instead, add Chrome as an exception in the antivirus settings or reinstall the antivirus so its network filter resets cleanly. A related issue on Windows machines is a stuck update service hogging the connection; our guide on fixing Windows Update stuck at 0 percent can help if your connection problems started during an update.

Fix 7: Disable Proxy and Reset LAN Settings

If your system is configured to use a proxy server — sometimes set by malware, a VPN app, or a workplace policy — and that proxy is unreachable, every request will time out. Disabling the proxy restores a direct connection.

Disable Proxy on Windows

1. Open Settings > Network & internet > Proxy.
2. Turn Automatically detect settings on, and turn Use a proxy server off.
3. Alternatively, open Chrome and go to Settings > System > Open your computer’s proxy settings, which takes you to the same page.
4. Restart Chrome and test.

Disable Proxy on Mac

1. Open System Settings > Wi-Fi > Details > Proxies.
2. Uncheck all proxy protocols in the list.
3. Click OK and test.

While you are here, it is also worth resetting the Windows network stack, which clears corrupted TCP/IP and Winsock configurations that can cause persistent timeouts:

1. Open Command Prompt as administrator.
2. Run these commands one at a time, pressing Enter after each:
   
   netsh winsock reset
   
   netsh int ip reset
   
   ipconfig /release
   
   ipconfig /renew
   
   ipconfig /flushdns
3. Restart your computer and test Chrome.

Fix 8: Reset Chrome Settings and Update Chrome

If none of the targeted fixes worked, a full settings reset clears any misconfigured flag, broken policy, or bad experimental setting hiding in Chrome. This is safe: it keeps your bookmarks, history, and saved passwords.

1. Open Chrome and go to Settings > Reset settings.
2. Click Restore settings to their original defaults, then confirm.
3. This resets your startup pages, pinned tabs, extensions (they are disabled, not deleted), and temporary data.
4. Also make sure Chrome is up to date: go to Settings > About Chrome and install any pending update, then relaunch.
5. Test the previously failing websites.

As a final diagnostic, try the site in a different browser such as Edge or Firefox. If it loads there but not in Chrome even after a reset, creating a fresh Chrome profile (click your profile icon > Add) can isolate profile corruption. If the site fails in every browser, the problem is with your network or the site itself, not Chrome.

Advanced: When the Error Persists on Every Device

If phones, laptops, and tablets on the same network all show timeouts, the problem is upstream of any single device. Work through this checklist:

• Test with mobile data. Disconnect from Wi-Fi and load the site over cellular. If it works, your home network or ISP is at fault.
• Check your router’s lights. A red or blinking internet light usually means the ISP link is down. Our guide on router blinking red light meaning and fixes explains what each pattern means.
• Bypass the router. If possible, plug a computer directly into the modem with an Ethernet cable. If timeouts stop, the router is the problem — try a factory reset or firmware update.
• Contact your ISP. Ask whether there is an outage or throttling in your area, and whether they can refresh your line from their end.
• Check the site’s status. Large sites have status pages; smaller ones can be checked with independent uptime tools. If the server is down, waiting is the only fix.

FAQs

What does ERR_CONNECTION_TIMED_OUT actually mean?

It means Chrome sent a request to a website’s server but received no response before its internal timer expired. The request may have been lost on your network, blocked by security software, misdirected by bad DNS, or simply ignored by an overloaded or offline server.

Why does ERR_CONNECTION_TIMED_OUT happen on only one website?

When a single site fails while others work, the cause is usually site-specific: the site’s server is down or overloaded, your cached data for that site is corrupted, or your IP address has been temporarily blocked by the site. Clear that site’s data first, then check whether the site is down for everyone.

Can a VPN cause ERR_CONNECTION_TIMED_OUT?

Yes. A VPN routes your traffic through its own servers, and if those servers are overloaded, far away, or down, requests can time out before reaching the destination. Disconnect the VPN temporarily to test. If the error disappears, switch VPN servers or providers.

Is ERR_CONNECTION_TIMED_OUT the same as ERR_CONNECTION_REFUSED?

No. “Timed out” means the server never answered at all, while “connection refused” means the server actively rejected the connection. Timeouts point to network, DNS, or firewall issues; refusals usually mean the server is running but blocking you, or nothing is listening on that port.

Will reinstalling Chrome fix ERR_CONNECTION_TIMED_OUT?

It can, but it is rarely necessary. Resetting Chrome’s settings (Fix 8 above) achieves nearly the same result while keeping your data. Reinstall only if a reset and a fresh profile both fail, and back up your bookmarks first.

How long does Chrome wait before showing this error?

Chrome typically waits around 30 seconds for a server response before giving up and displaying ERR_CONNECTION_TIMED_OUT. You cannot change this timeout in normal settings, which is why fixing the underlying cause is the only real solution.

Conclusion

ERR_CONNECTION_TIMED_OUT looks alarming, but in most cases one of these eight fixes resolves it: a quick restart, clearing cache and cookies, disabling a bad extension, switching DNS servers, flushing Chrome’s socket pools, checking your firewall, disabling a stale proxy, or resetting Chrome’s settings. Work through them in order and test after each step so you know exactly which one did the trick. If the error appears on every device on your network, shift your attention upstream to the router and ISP. And if it is just one website, check whether the site itself is down before spending an hour troubleshooting your own setup — sometimes the only real err_connection_timed_out chrome fix is patience.