You type a URL into Chrome, wait… wait… and finally get: “This site can’t be reached. ERR_CONNECTION_TIMED_OUT.” The page never loads. Maybe it happens on every website, or maybe just one specific site.
This error means Chrome sent a request to the server but never received a response within the timeout period (usually 30 seconds). The server didn’t refuse the connection — it simply didn’t respond at all.
Unlike ERR_CONNECTION_REFUSED (where the server actively rejects you), a timeout means something between your computer and the server is blocking or delaying the connection. The fix depends on where the blockage is.
What Causes ERR_CONNECTION_TIMED_OUT?
The timeout error has several possible causes:
- DNS resolution failure — Chrome can’t translate the domain name to an IP address, or it takes too long
- Proxy misconfiguration — Windows is set to use a proxy that doesn’t exist or isn’t responding
- Firewall blocking outbound connections — Windows Firewall or your antivirus is blocking Chrome
- Corrupted browser cache or DNS cache — Stale cache data points Chrome to the wrong IP address
- LAN settings misconfigured — Windows has incorrect automatic configuration settings
- The website is actually down — the simplest explanation, but check this first
How to Fix ERR_CONNECTION_TIMED_OUT
Method 1: Check if the Website Is Actually Down
Before touching any settings, verify the site isn’t just down for everyone.
Step 1: Open your phone browser (using mobile data, NOT WiFi) and visit the same URL.
Step 2: Check downdetector.com or isitdownrightnow.com for the specific website.
Step 3: If the site loads on your phone but not Chrome, the problem is your computer or network. Continue to Method 2.
Method 2: Flush DNS Cache and Renew IP
Corrupted DNS cache is the most common cause of timeout errors.
Step 1: Open Command Prompt as Administrator (right-click Start → Terminal (Admin)).
Step 2: Run these commands one by one:
Step 3: Restart your computer.
Step 4: Also clear Chrome’s internal DNS cache: type chrome://net-internals/#dns in the address bar and click “Clear host cache”.
Why this works: Windows caches DNS results locally. If a website changed its IP address or your DNS cache became corrupted, Chrome keeps trying to reach the old (non-responsive) IP address, causing a timeout.
Method 3: Disable Proxy / Check LAN Settings
A misconfigured proxy setting is a very common but overlooked cause.
Step 1: Press Windows + R, type inetcpl.cpl, press Enter.
Step 2: Go to the Connections tab → click LAN Settings.
Step 3: Make sure these settings are correct:
- ✅ “Automatically detect settings” — UNCHECK this box
- ❌ “Use a proxy server for your LAN” — make sure this is UNCHECKED
- ❌ “Use automatic configuration script” — make sure this is UNCHECKED
Step 4: Click OK → OK → restart Chrome.
Why “Automatically detect settings” causes problems: This option uses WPAD (Web Proxy Auto-Discovery Protocol) to find a proxy. On many home networks, WPAD fails or times out, adding 20-30 seconds of delay to every connection — which triggers the timeout error.
Method 4: Change DNS Servers
Your ISP’s default DNS servers might be slow or unreliable.
Step 1: Open Settings → Network & Internet → Advanced network settings.
Step 2: Click your active network adapter → Edit (or More adapter options → right-click → Properties).
Step 3: Select Internet Protocol Version 4 (TCP/IPv4) → Properties.
Step 4: Select “Use the following DNS server addresses”:
| Provider | Primary DNS | Secondary DNS |
|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| 8.8.8.8 | 8.8.4.4 |
Step 5: Click OK, close all windows, restart Chrome.
Method 5: Clear Chrome Cache and Cookies for the Specific Site
If only one website times out while everything else works, Chrome may have cached incorrect data for that specific site.
Step 1: In Chrome, press Ctrl + Shift + Delete to open Clear Browsing Data.
Step 2: Set time range to “All time”.
Step 3: Check:
- ✅ Cookies and other site data
- ✅ Cached images and files
Step 4: Click Clear data.
Step 5: Try the website again.
For a targeted approach, you can clear data for just one site: go to chrome://settings/siteData, search for the domain, and delete only that site’s data.
Method 6: Check Windows Firewall
Windows Firewall might be blocking Chrome’s outbound connections.
Step 1: Press Windows + I → search for “Windows Defender Firewall”.
Step 2: Click “Allow an app or feature through Windows Defender Firewall”.
Step 3: Click “Change settings” and look for Google Chrome in the list.
Step 4: Make sure both Private and Public boxes are checked.
Step 5: If Chrome isn’t in the list, click “Allow another app” → Browse to C:\Program Files\Google\Chrome\Application\chrome.exe → Add it.
One Site vs All Sites — How to Narrow It Down
| Symptom | Likely Cause | Fix |
|---|---|---|
| ALL websites time out | DNS, proxy, or network issue | Methods 2, 3, 4 |
| Only ONE site times out | Website down, or cached data issue | Method 1, 5 |
| Sites work in other browsers but not Chrome | Chrome proxy/cache issue | Methods 3, 5 |
| Sites work on phone WiFi but not PC | PC-specific DNS or firewall issue | Methods 2, 4, 6 |
| Sites work on mobile data but not home WiFi | Router/ISP issue | Restart router, Method 4 |
Frequently Asked Questions
ERR_CONNECTION_TIMED_OUT only happens on one website. Is it my problem or theirs?
If the website loads fine on your phone (using mobile data) and other people can access it, the issue is likely your DNS cache or firewall. Flush your DNS (Method 2) and clear Chrome’s cache for that specific site (Method 5).
What’s the difference between ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_REFUSED?
TIMED_OUT means the server never responded at all — something blocked the connection or the server is unreachable. REFUSED means the server actively rejected your connection — the server is reachable but isn’t accepting connections on that port.
I get this error after connecting to a VPN. Why?
VPNs route your traffic through different servers and often use their own DNS. The VPN’s DNS might be slow, or the VPN server might not have a route to the website you’re trying to reach. Try changing your VPN’s DNS to 1.1.1.1, or test with the VPN disconnected.
Chrome times out but Firefox works fine. What’s going on?
Chrome uses its own DNS cache and proxy settings separate from Firefox. Clear Chrome’s DNS cache (chrome://net-internals/#dns), check Chrome’s proxy settings (chrome://settings/system → “Open your computer’s proxy settings”), and make sure WPAD/auto-detect is disabled (Method 3).
Conclusion
ERR_CONNECTION_TIMED_OUT is a network issue, not a Chrome bug. Flush your DNS and disable proxy auto-detection first — these two steps fix the error for most users. If it persists, change your DNS servers to Cloudflare or Google and check your Windows Firewall settings.