How to fix ERR_CONNECTION_TIMED_OUT in Chrome on Windows, Mac and Android

"This site can't be reached. example.com took too long to respond. ERR_CONNECTION_TIMED_OUT."

Unlike a DNS error, this one means your browser already knew where to go. It sent a connection request to the server's IP address and then waited, usually around 20 to 30 seconds, without getting any reply. Something along the way swallowed the packets.

That "something" is one of four places: your device, your local network, the path in between, or the server. This guide checks them in that order, from quickest to slowest.

First: is it the site or you?

Spend ten seconds on this before changing any settings. Open the site from a different network, such as your phone on mobile data, or use an outside checker like upordown.online to see whether the site responds for everyone.

• Times out everywhere: the server or its hosting is down or overloaded. Nothing on your side will fix it. Wait, or contact the site owner.
• Works elsewhere: the problem is on your device or network. Continue.

Fix 1: Disable the VPN, proxy and "secure browsing" tools

Proxies and VPNs are the most common cause of timeouts that affect only you. A dead proxy server means every request goes nowhere.

Windows 10/11: Settings → Network & internet → Proxy. Turn off "Use a proxy server" under Manual proxy setup. Leave "Automatically detect settings" on unless your company says otherwise.

To check for a system-wide WinHTTP proxy, run in an admin Command Prompt:

netsh winhttp show proxy
netsh winhttp reset proxy

macOS: System Settings → Network → Wi-Fi → Details → Proxies. Turn all proxy types off unless you need them.

Android: Settings → Wi-Fi → long-press or tap your network → Advanced / Modify → Proxy → None.

Then disconnect any VPN app and pause antivirus "web shield" features for a quick test.

Fix 2: Test the browser in isolation

1. Open an incognito window (Ctrl+Shift+N / Cmd+Shift+N). If the site loads, an extension is responsible. Go to chrome://extensions and disable extensions one at a time.
2. Try a different browser. If Firefox works and Chrome doesn't, reset Chrome: Settings → Reset settings → Restore settings to their original defaults.
3. Clear Chrome's open connections: chrome://net-internals/#sockets → Flush socket pools.

Fix 3: Check the firewall

A firewall rule that silently drops traffic causes exactly this error, because dropped packets produce no reply at all.

Windows: search for "Allow an app through Windows Firewall" and confirm Chrome is allowed on Private and Public networks. Third-party security suites have their own firewall; temporarily disable it to test.

macOS: System Settings → Network → Firewall → Options. Make sure your browser isn't set to "Block incoming connections" and that "Block all incoming connections" is off.

Linux: check whether outbound traffic is restricted:

sudo ufw status verbose
sudo iptables -L OUTPUT -n

Fix 4: Prove where the connection stops

Use a command-line test that bypasses the browser completely.

Test the HTTPS port directly.

Windows PowerShell:

Test-NetConnection example.com -Port 443

TcpTestSucceeded : True means the port is reachable from your machine, so the problem is the browser or a proxy. False means the network or the server is dropping it.

macOS / Linux:

nc -vz -w 5 example.com 443
curl -v --connect-timeout 10 https://example.com -o /dev/null

Then find the hop where packets stop:

traceroute -T -p 443 example.com   # Linux (may need sudo)
traceroute example.com             # macOS
tracert example.com                # Windows

If it fails at hop 1 or 2, look at your router. If it travels far and dies right before the destination, the server or its provider is filtering or overloaded.

Fix 5: Restart and update the router

Routers running for months can run out of connection-tracking memory and begin dropping new connections, especially with many devices online.

1. Unplug the router and modem for 30 seconds, then power them back on.
2. Log into the router's admin page and check for firmware updates.
3. Look for parental controls, "safe browsing" or blocklist features that might cover the site.
4. If you're on public or hotel Wi-Fi, open any plain http:// page to trigger the sign-in portal; until you accept it, everything else times out.

Fix 6: Reset the network stack

Windows (admin Command Prompt, then restart):

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew

macOS: delete and re-add the Wi-Fi service in System Settings → Network, or simply forget the Wi-Fi network and rejoin it.

Android: Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth. Also try toggling Airplane mode for 10 seconds.

Fix 7: Try IPv4 versus IPv6

Some networks have broken IPv6: the device thinks IPv6 works, but packets go nowhere. Compare:

curl -4 -sS -o /dev/null -w "%{http_code}\n" https://example.com
curl -6 -sS -o /dev/null -w "%{http_code}\n" https://example.com

If -4 works and -6 hangs, disable IPv6 on the adapter as a workaround (Windows: Control Panel → Network Connections → adapter Properties → untick "Internet Protocol Version 6") and report the issue to your ISP.

If you run the server

When your own visitors get ERR_CONNECTION_TIMED_OUT:

• Confirm the service is listening: ss -tlnp | grep -E ':80|:443'.
• Check cloud security groups and the host firewall allow inbound 80/443.
• Check whether the server is overloaded: high load, exhausted connections, or a full disk.
• If you're behind a CDN or reverse proxy, check whether the origin is timing out (that often shows as 522/524 or 504 rather than a browser timeout).

FAQ

What is the difference between ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_REFUSED?

A timeout means no reply arrived at all, usually because packets were dropped. "Refused" means the server replied immediately and said nothing is listening on that port. A refusal is almost always server-side; a timeout can be either side.

Why does only one website time out?

Either that site's server is struggling, or something filters it on your path: a proxy, firewall, router blocklist, or your ISP. Testing from mobile data tells you which.

Why do I get ERR_CONNECTION_TIMED_OUT on my phone only?

Check for a proxy on the Wi-Fi network, a VPN or ad-blocking app, and a captive portal. Switching between Wi-Fi and mobile data quickly shows whether it's the network.

Can my ISP cause this error?

Yes. Routing problems or blocks at the ISP produce timeouts. If a traceroute stops inside the ISP's network and a VPN fixes it, contact the ISP.

Is it safe to reset network settings?

Yes. You'll lose saved Wi-Fi passwords and custom DNS or proxy settings, but no personal data.