ERR_CONNECTION_TIMED_OUT: Causes and Fixes for Visitors and Owners

ERR_CONNECTION_TIMED_OUT is Chrome's message when it sent a connection request and heard nothing back before giving up, typically after about 20 to 30 seconds. The page reads "This site can't be reached. example.com took too long to respond."

Unlike a refusal, there was no reply at all. Packets were dropped somewhere: by a firewall, by a congested or broken route, or because the server is overloaded or powered off. For the refused and reset variants see ERR_CONNECTION_REFUSED और ERR_CONNECTION_RESET.

If you are a visitor

1. Test another site. If nothing loads, your connection is the issue; restart the router and check ERR_INTERNET_DISCONNECTED.
2. Check whether the site is down globally. Use Down From Where. If it fails from every region, wait and try later.
3. Try mobile data or another network. If it works there, your ISP, router or office firewall is blocking or dropping traffic to that site.
4. Disable VPN, proxy and security software. A slow VPN exit or a filtering proxy often causes timeouts. See ERR_PROXY_CONNECTION_FAILED.
5. Flush DNS and restart your network adapter. ipconfig /flushdns on Windows, then disable and re-enable the adapter.
6. Check your hosts file for a stale entry pointing the domain at an unreachable IP.
7. Try another browser. If it works there, reset Chrome's network state by clearing browsing data or disabling extensions.

If a corporate or school network blocks the site, you will need the network administrator.

If you own the site

A timeout means you must find where packets die. Work along the path.

1. Is the server reachable at all?

ping -c 4 203.0.113.10
curl -v --connect-timeout 10 https://example.com/
traceroute -T -p 443 203.0.113.10

Ping may be blocked even on a healthy server, so rely on a TCP test. The पोर्ट चेकर tests ports 80 and 443 from outside your network. If the check times out from everywhere, the server or its firewall is the culprit. If it only fails from some regions, suspect routing or a regional block; check with Down From Where.

2. Firewall DROP rules and security groups

Cloud security groups and iptables or nftables rules drop packets without a reply, which looks exactly like a timeout. Confirm that inbound TCP 80 and 443 are allowed from 0.0.0.0/0, and check network ACLs and any DDoS or geo-blocking rules.

sudo ufw status verbose
sudo iptables -L INPUT -n --line-numbers | head -n 30

Fail2ban or a similar tool may also have banned the visitor's IP. Ask the user for their address (they can find it with What Is My IP) and check sudo fail2ban-client status.

3. The server is overloaded or hung

When the listen backlog fills, new connections are silently dropped. Look at load and sockets:

uptime
ss -s
dmesg | grep -i -E "oom|syn flooding"

A kernel message about SYN flooding or an out-of-memory kill suggests the box is exhausted. Restart the stuck service, add capacity, or fix the runaway process. For gateway-style timeouts in front of an app, read nginx upstream timed out और Fix 504 Gateway Timeout.

4. DNS points at a dead or wrong IP

If the A record leads to a server that no longer exists, packets disappear. Compare the answer from the DNS चेकर with the real server IP. After a migration this is the first thing to check.

5. IPv6 records without a working IPv6 server

A published AAAA record that points to an address nothing answers on makes dual-stack clients stall before falling back to IPv4. Test with curl -6 -v https://example.com/ and either fix the IPv6 listener or remove the AAAA record.

6. Path MTU and routing problems

If small requests work but large ones hang, suspect an MTU or ICMP issue, often with tunnels and VPNs. Allow ICMP "fragmentation needed" messages and test with ping -M do -s 1400 example.com.

7. Blocklisted or rate-limited server IPs

Some networks block IPs with a poor reputation. Check the address in the Blacklist Checker. A CDN in front can show a related symptom as Cloudflare error 522.

Verify

1. curl -sS -o /dev/null -w "%{time_connect}\n" https://example.com/ should return well under a second.
2. Run the वेबसाइट हेल्थ चेक and the HTTP स्टेटस चेकर.
3. Set up an अपटाइम मॉनिटर with alerts so timeouts reach you first.

अगले कदम

• Read the connection errors explained guide.
• Compare with the generic ERR_TIMED_OUT.
• See Why is my website down?.
• Tune alerts with how often to monitor a website.

सामान्य प्रश्न

How long does Chrome wait before showing this error?

Typically 20 to 30 seconds for the connection attempt, though the exact figure depends on the operating system's TCP retry settings.

Does a timeout mean the server is down?

Not always. The server may be fine while a firewall or route drops your traffic. Test from a different network to tell the two apart.

Why does it time out on Wi-Fi but work on mobile data?

Your Wi-Fi router, ISP or local DNS is the likely cause. Reboot the router and try a different DNS resolver.

How is this different from ERR_CONNECTION_REFUSED?

A refusal is an instant reply saying no. A timeout is no reply at all.

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.