Connection Timed Out Error: What It Means and How to Fix It

A connection timed out error (shown as ERR_CONNECTION_TIMED_OUT in Chrome) means your browser tried to connect to a server but gave up waiting for a response. Unlike ERR_CONNECTION_REFUSED where the server actively rejects you, a timeout means the server just... didn't reply.

It's the network equivalent of knocking on a door and getting no answer.

Connection Timed Out vs Connection Refused

These two errors get confused but they're different:

• Connection refused: The server received your request and actively said "no". Something is there but won't let you in.
• Connection timed out: Your request went out but nothing came back. The server may be unreachable, overloaded, or there may be a network issue in between.

What Causes a Connection Timeout?

1. Server Is Down or Unreachable

The most straightforward cause. If the server is powered off, has crashed, or has lost network connectivity, your connection attempt simply never gets a response.

Check if this is affecting everyone using an online website down checker or by asking someone on a different network to try.

2. Firewall Blocking the Connection

A server-side or network-level firewall may be silently dropping packets rather than rejecting them. This produces a timeout rather than a refused connection — the firewall doesn't send back a rejection, it just discards the packets.

Common scenarios:

• A cloud provider's security group blocking port 80 or 443
• A server firewall rule added during maintenance that was too restrictive
• A network device (router, ISP) filtering traffic to the server

3. Server Is Overloaded

An overwhelmed server that can't accept new connections in time will cause timeouts for new visitors. Existing connections might still work, but new ones can't get established fast enough before the browser gives up.

4. Network Issues Between You and the Server

Packet loss, routing problems, or congestion between your location and the server can cause timeouts. This might affect only some users depending on their geographic location or ISP.

5. Wrong IP Address or Port

If a DNS record is pointing to the wrong IP address, or the server is listening on a non-standard port that you're not specifying, your connection will time out attempting to reach something that isn't there.

6. Local Network Problem

Slow or unstable local internet connection, a congested VPN, or a faulty router can all cause timeouts for all sites — not just one.

How to Diagnose a Timeout

Test From Multiple Locations

Use a tool like Down For Everyone Or Just Me or Domain Monitor's status checker to see if the timeout is just you or universal.

Trace the Route

A traceroute shows where packets stop traveling:

# macOS/Linux
traceroute yourdomain.com

# Windows
tracert yourdomain.com

If packets stop at a specific hop, that's where the problem is.

Test the Port Directly

telnet yourdomain.com 80
telnet yourdomain.com 443

A timeout here confirms the server isn't responding on that port.

Check From the Server Side

If you have SSH access:

# Is the web server running?
sudo systemctl status nginx
sudo systemctl status apache2

# Is it listening on port 80/443?
sudo ss -tlnp | grep -E ':80|:443'

# Is the firewall blocking?
sudo ufw status

Fixes for Server-Side Timeouts

Web server not running: Start it with sudo systemctl start nginx or sudo systemctl start apache2.

Firewall blocking: Open the necessary ports:

sudo ufw allow 80/tcp
sudo ufw allow 443/tcp

For cloud servers (AWS, DigitalOcean, etc.), also check the security group or network ACL rules in your cloud provider's console.

Server overloaded: Check CPU and memory usage, identify bottlenecks, and either scale up or optimise the application. Our cloud server monitoring guide covers strategies for managing server resources under load.

Fixes for Client-Side Timeouts

If the site loads fine elsewhere and only times out for you:

1. Restart your router — clears local network state
2. Disconnect from VPN — VPNs can introduce routing problems
3. Try a different DNS server — sometimes a DNS issue can indirectly cause routing problems
4. Flush DNS cache — ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS
5. Try from mobile data — rules out your home network being the issue

Monitor So You're the First to Know

A timeout means nobody can reach your site. Without monitoring, you might not find out for hours. Domain Monitor checks your website every minute from multiple global locations and sends an instant alert if your site stops responding — giving you the chance to fix it before your users even notice.

Set up downtime alerts today and stop finding out about problems after the fact.

Related Articles

• Cloudflare Error 522 - Connection Timed Out (How to Fix It)
• 403 Forbidden Error - What It Means and How to Fix It
• 500 Internal Server Error - Causes and How to Fix It