Error fix

How to fix “ETIMEDOUT — connection timed out

TCP connection attempts timed out—host unreachable, firewall, or wrong address.

Updated Apr 20, 2026

Tools that help with this

Fastest fix

Start here first. Step 1 fixes most cases—then work down the list.

  1. Ping/traceroute and test port with nc/telnet from the same environment.
  2. Check cloud security groups and on-prem firewalls for egress/ingress.
  3. Validate DNS A/AAAA records and TTL after changes.

Why this works

These steps work because it rules out local security software dropping the connection.

What this means

No response to SYN within the OS timeout—different from refused (actively rejected) or reset.

Common causes

  • Network path

    Firewall rules, security groups, or routing to a dead IP.

  • DNS to wrong region

    Geo DNS points to an unreachable PoP from your network.

Step-by-step fix

  1. Verify reachability

    1. Ping/traceroute and test port with nc/telnet from the same environment.
    2. Check cloud security groups and on-prem firewalls for egress/ingress.
    3. Validate DNS A/AAAA records and TTL after changes.

FAQ

ETIMEDOUT in Docker?
Check bridge networking, published ports, and DNS inside the container.
Intermittent only?
Suspect flaky Wi‑Fi, MTU issues, or overloaded NAT gateways.
IPv6 timeout?
Try disabling AAAA temporarily to see if IPv4 path works.

Still stuck? Try these related fixes next.

Edit your error

Tweak the message and run again—we'll match an existing fix or generate a new page.

Original error message
connect ETIMEDOUT
Fix another errorHTTP status codesURL status checkerRedirect checkerAll tools