Skip to content
Rescue 404
Rescue

Server Errors

ERR_CONNECTION_TIMED_OUT

Intermediate Risk: medium

Last reviewed

Hosting access often needed Database access usually not needed

Direct answer

ERR_CONNECTION_TIMED_OUT

ERR_CONNECTION_TIMED_OUT means the browser sent a connection request and never got any reply at all — not even a refusal — usually because the server is down, a firewall is silently dropping packets, DNS points at the wrong IP, or a network path between visitor and origin is broken. Confirm the server is actually reachable from outside your own network before changing any WordPress settings.

This is a network-layer failure, not an application error: WordPress, PHP, and your theme never get a chance to run because the TCP connection itself never completes. This guide separates real outages from single-network routing problems and gives the fastest way to tell which one you have.

Intermediate

Key facts

Verifiable numbers and definitions — each claim links to its source.

What the error means

ERR_CONNECTION_TIMED_OUT fires when the browser cannot establish a TCP connection to the server within its timeout window, and — critically — never receives an explicit rejection either. That silence points at packets being dropped somewhere: the origin server is powered off or the web service has crashed, a firewall or security group is silently discarding the traffic instead of returning a refusal, DNS is resolving to an IP nothing is listening on, or a network segment between the visitor and the origin (an ISP route, a VPN, a corporate proxy) is broken. This differs from ERR_CONNECTION_REFUSED, where the server or a device in the path actively rejects the connection right away, and from 504 Gateway Timeout, where a connection was established but an upstream application (like PHP-FPM) took too long to respond. Because a timeout can be purely local to the visitor’s network, always confirm the failure from a second network before touching server configuration.

Common symptoms

  • Chrome shows “This site can’t be reached — ERR_CONNECTION_TIMED_OUT”
  • The page hangs for a long time before failing, unlike an instant refusal or DNS error
  • The site fails from your office or home network but loads fine on mobile data
  • Other sites on the same server also fail, suggesting the whole host or IP is unreachable
  • ping or traceroute to the domain times out or dies partway through the route
  • The problem started after a server reboot, firewall change, IP migration, or DNS update
  • wp-admin, SSH, and the public site are all unreachable at the same time

Most likely causes

  1. 01 Web server, hosting VM, or container is down or the service crashed
  2. 02 Host firewall, security group, or CSF/Imunify rule silently dropping inbound traffic
  3. 03 DNS A/AAAA record pointing at a stale or wrong IP after a migration
  4. 04 Network path issue between the visitor’s ISP/VPN and the origin (not global, may be local to some networks)
  5. 05 Server overloaded to the point new connections cannot be accepted (SYN backlog exhausted)
  6. 06 DDoS mitigation, rate limiting, or an upstream provider blackholing traffic to the IP
  7. 07 Wrong port or the web service not actually listening on 80/443 after a config change

What changed before the problem started

  • Server reboot, resize, or hosting migration that changed the IP address
  • New firewall rules, security group, or CDN/proxy toggle
  • DNS record edited and not yet fully propagated, or edited incorrectly
  • Traffic spike or attack triggering aggressive rate limiting upstream
  • Network change on the visitor’s side — new VPN, ISP outage, or corporate proxy
  • Web server or container crash after a resource-limit or deployment change

Troubleshooting steps

  1. 01

    Reproduce from a second, unrelated network first

    Test the URL from mobile data (with WiFi off) or ask a colleague on a different ISP to try it. If it loads there, the timeout is local to your original network — a VPN, corporate proxy, or ISP route — and no server change is needed. Only proceed to server checks if the second network also fails.

  2. 02

    Confirm the server is actually reachable, not just DNS

    Check whether SSH, the hosting control panel, and other sites on the same server are also unreachable. If everything on that IP is down, this is a host outage or firewall issue, not a WordPress problem — contact the host immediately with the IP and timestamp.

  3. 03

    Verify DNS points at the correct, current IP

    Look up the domain’s A/AAAA record and compare it against the IP shown in your hosting control panel. A stale IP after a migration is one of the most common causes of a total, unrecoverable timeout for everyone.

  4. 04

    Check the host’s status page and recent maintenance notices

    Many timeouts during a wide outage are explained immediately by the host’s own status page. Confirm before assuming a local misconfiguration and spending time on changes that will not fix a provider-side event.

  5. 05

    Ask the host to check the firewall and web server process

    If you do not have direct server access, have the host confirm the web server (Apache/Nginx/LiteSpeed) is running and that no firewall rule, security group, or DDoS mitigation is silently dropping traffic to ports 80/443.

  6. 06

    Rule out a local network cause before opening a ticket as “site down”

    If only your network times out and DNS/IP are confirmed correct, try a different browser, disable any VPN, and flush your local DNS cache. Report the exact network and time to your host or IT only after confirming the failure is not visitor-specific.

When to stop troubleshooting

Escalate immediately if the server, SSH, and control panel are all unreachable (likely a real outage), you cannot confirm the current IP or DNS status yourself, the timeout persists across multiple independent networks, or the site is down during business-critical hours. Provide the host with the domain, current DNS records, and confirmation the failure is not visitor-specific.

Information to collect before requesting help

  • 01 Exact browser error text and the URL that fails
  • 02 Whether the failure reproduces from at least two independent networks
  • 03 Current DNS A/AAAA record value versus the hosting panel’s listed IP
  • 04 Whether SSH, control panel, and other sites on the same server are reachable
  • 05 Approximate time the problem started and any recent server/DNS/firewall changes
  • 06 Output of ping or traceroute/mtr to the domain and to the raw IP
  • 07 Host status page notices for the relevant time window

How a professional repairs the problem

A technician first confirms whether the timeout is visitor-local or a real outage by testing from independent networks and checking whether the whole server (not just one site) is unreachable. From there they verify DNS matches the live IP, confirm the web server process and firewall/security group are actually accepting connections on 80/443, and review capacity or DDoS mitigation logs if the server is up but refusing new connections under load — escalating to the network or hosting provider rather than editing WordPress, which never had a chance to run.

Frequently asked questions

Is ERR_CONNECTION_TIMED_OUT a WordPress error? +
No. It happens before any request reaches WordPress or PHP — the browser could not even establish a connection to the server. Any fix is at the network, DNS, firewall, or hosting level, not inside WordPress.
How is this different from ERR_CONNECTION_REFUSED? +
Refused means something actively rejected the connection right away — the port is reachable but closed or blocked. Timed out means no response came back at all, which usually points at a down server, a silent firewall drop, or a broken network path.
Why does the site work on my phone but not my computer? +
That is a strong sign the timeout is specific to your original network — a VPN, corporate firewall, or ISP routing issue — rather than the server being down. Confirm from a second independent network before contacting your host as an outage.
Could a recent DNS change cause this? +
Yes. If DNS still points at an old IP after a migration, or the change has not fully propagated, connections will go nowhere and time out. Compare the live DNS record against your current hosting panel IP.
Can too much traffic cause a timeout instead of just slowness? +
Yes. If the server’s connection queue or worker limits are exhausted, new connections may never get a SYN-ACK at all, which presents as a timeout rather than a slow-but-successful load. That is a capacity and mitigation issue, not a code problem.
Should I keep refreshing the page if I see this error? +
Refreshing will not help while the underlying path is broken. Confirm reachability from another network and check the host status page first; only retry after a fix has actually been made on the server, DNS, or network side.

Repair dispatch

Still Need Help Fixing Your Website?

If you are not comfortable editing website files, changing server settings, repairing a database, or troubleshooting a live website, professional help may prevent additional damage or downtime. We will review the problem before accepting the repair.

  • You will receive a clear explanation of the likely cause.
  • We will tell you if the issue falls outside our repair scope.
  • No additional work will be performed without approval.
  • A backup should be created whenever access and website condition allow it.
Emergency repair Request diagnosis

Do not share passwords through an unencrypted contact form — use Password Pusher (self-destructing link). Prefer a dedicated Rescue 404 admin account, not your personal owner login; if you cannot create one yet, we will add ours after repair.

Written by Josh

Last reviewed

Platform note: Full rescue available for WordPress and self-hosted sites. Wix, Squarespace, Webflow, Weebly, and similar closed builders have very limited backend access — fixes may not be possible. I will tell you honestly before we start.