ERR_CONNECTION_TIMED_OUT 🧭 Browser

ERR_CONNECTION_TIMED_OUT: This site can’t be reached — example.com took too long to respond

The browser waited for the server but got no response — the server is down/unreachable, a firewall drops traffic, or DNS points to the wrong IP.

Seen on: Chrome

Meaning

Unlike “refused”, nothing answered at all. Common causes: server offline, firewall/security group blocking port 80/443, DNS pointing to an old IP, or a local proxy/firewall blocking the site.

Common causes

  • Server down or overloaded
  • Firewall/security group blocking 80/443
  • DNS still pointing to an old server
  • Local proxy/firewall blocking

⚡ Quick fix

  1. Check the site from another network or an uptime checker
  2. Verify DNS resolves to the right server
  3. Site owners: open ports 80/443 and check the server is listening

Detailed fix by platform

Shell

  1. bash
    nslookup example.com
curl -I --max-time 10 https://example.com
nc -vz example.com 443

How to diagnose

  1. DNS — Correct IP?
  2. Server — Listening and reachable?
  3. Local — Proxy/VPN?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.