Error Encyclopedia

ERR_CONNECTION_TIMED_OUT Error

Fix 'ERR_CONNECTION_TIMED_OUT' errors when a website or server takes too long to respond. Learn how to diagnose and fix connection timeout issues.

What Does This Error Mean?

The ERR_CONNECTION_TIMED_OUT error means the browser sent a connection request but the server did not respond within the timeout period. The connection was established at the TCP level (unlike DNS errors) but no data was received.

Common Causes

1

Server is overloaded and cannot respond in time

2

Network congestion or high latency to the server

3

Firewall dropping packets after connection establishment

4

Server is behind a slow proxy or load balancer

5

Client's internet connection is slow or unstable

6

Server process is stuck or deadlocked and cannot respond

How to Fix It

Check server load and resources

Monitor server resource usage to identify bottlenecks.

# Check CPU and memory
htop
top
free -m

# Check disk I/O
iostat -x 1

# Check for runaway processes
ps aux --sort=-%cpu | head

Test connectivity step by step

Isolate where the timeout occurs by testing different parts of the network path.

# Ping the server
ping -n 10 example.com

# Traceroute to find where packets are dropped
tracert example.com  # Windows
traceroute example.com  # Linux/macOS

# Test specific port with telnet
telnet example.com 443

# Test with curl to see timing
curl -w "TCP handshake: %{time_connect}s
Total: %{time_total}s
" -o /dev/null -s https://example.com

Check for timeout settings

Ensure timeout values are appropriate for network conditions.

# Nginx: increase timeout
proxy_read_timeout 120s;
proxy_connect_timeout 30s;

# Node.js: increase timeout in fetch
const controller = new AbortController()
const timeout = setTimeout(() => controller.abort(), 60000)
fetch(url, { signal: controller.signal })
  .finally(() => clearTimeout(timeout))

Related Tools

Use these tools to debug and fix this error:

Related Errors

Other common errors in this category: