ERR_CONNECTION_TIMED_OUT: 8 Fixes That Actually Work

ERR_CONNECTION_TIMED_OUT means Chrome waited too long for a response from the web server and gave up. The browser sent a connection request but the server did not respond within Chrome’s timeout window (typically 30 seconds). This is different from ERR_CONNECTION_REFUSED (server actively rejected you) because with a timeout, the server simply never answered.

This error can be caused by problems on the server side (overloaded, down, or unreachable), on your network (DNS issues, firewall blocks, proxy misconfiguration), or on your device (corrupted network settings, hosts file redirects). Here are all the proven fixes.

Fix 1: Check if the Website Is Down

Before troubleshooting your own setup, verify whether the site is down for everyone. Visit downdetector.com or isitdownrightnow.com and check the domain. If the site is globally unreachable, no client-side fix will help. Wait for the server administrators to resolve the issue. If it loads for others but not you, the problem is on your end.

Fix 2: Clear Browser Cache and Cookies

Cached DNS entries or corrupted session data can prevent Chrome from connecting. Press Ctrl+Shift+Delete, select “All time,” check both cache and cookies, then clear. Close and reopen Chrome. Also clear Chrome’s socket pools: navigate to chrome://net-internals/#sockets and click “Flush socket pools.”

Fix 3: Change DNS Servers

Slow or unresponsive DNS servers are a top cause of connection timeouts. Switch to Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare DNS (1.1.1.1, 1.0.0.1). On Windows, go to Network Settings, Change adapter options, right-click your connection, Properties, IPv4, and enter the DNS addresses. Flush your DNS cache after: run “ipconfig /flushdns” in Command Prompt.

Fix 4: Disable Proxy Settings

A misconfigured proxy routes your traffic through a non-existent server, causing timeouts. Go to Chrome Settings, System, Open proxy settings. Make sure “Use a proxy server” is OFF and “Automatically detect settings” is ON. On Windows, also run “netsh winhttp reset proxy” in an elevated Command Prompt to clear system-wide proxy settings.

Fix 5: Check Your Firewall

Windows Firewall or third-party security software may block Chrome. Temporarily disable your firewall: Windows Security, Firewall & network protection, turn off for your active profile. If the site loads, add Chrome to the allowed applications list and re-enable the firewall. Check antivirus web filtering settings too.

Fix 6: Flush DNS and Reset TCP/IP

Corrupted network stack settings cause persistent timeouts. Open Command Prompt as Administrator and run in order: “ipconfig /flushdns” then “netsh winsock reset” then “netsh int ip reset” then “ipconfig /release” then “ipconfig /renew.” Restart your computer after all commands complete.

Fix 7: Check Your Hosts File

The hosts file can redirect domains to wrong IPs, causing timeouts. On Windows, open Notepad as Admin and check C:\Windows\System32\drivers\etc\hosts. Remove any entries for the domain showing the timeout error. Malware and parental control software often modify this file.

Fix 8: Increase Chrome Timeout

For very slow servers, Chrome’s default timeout may be too short. While Chrome does not expose a timeout setting directly, disabling the QUIC protocol can help: go to chrome://flags, search for “Experimental QUIC protocol,” set to Disabled, and restart Chrome. QUIC can cause faster timeouts on incompatible networks.

Frequently Asked Questions

What is the difference between ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_REFUSED?

ERR_CONNECTION_TIMED_OUT means the server never responded to your connection request (silence). ERR_CONNECTION_REFUSED means the server actively rejected your connection (got a response, but it was “no”). Timeouts suggest network problems or an unreachable server. Refused connections suggest the server is running but not accepting connections on that port.

Why does ERR_CONNECTION_TIMED_OUT only affect one website?

If only one site times out, the problem is likely server-side (overloaded, geographically restricted) or DNS-specific (your DNS cache has a stale entry for that domain). Change your DNS to Google (8.8.8.8) and flush your cache. If it still fails, the server itself may be unreachable from your geographic location.

Can a VPN fix ERR_CONNECTION_TIMED_OUT?

Sometimes. If your ISP blocks the server or has routing issues to that specific IP, a VPN routes your traffic through a different path. Try connecting to a VPN server in a different country. If the site loads through VPN, your ISP or local network is blocking or misrouting the connection.