There’s no WordPress logo, no error page from your host, nothing from your theme. Just the browser’s own grey screen. In Chrome it reads “This site can’t be reached. example.com took too long to respond.” with ERR_CONNECTION_TIMED_OUT in small letters. Firefox says “The connection has timed out” and suggests the site may be temporarily unavailable or too busy.
That plainness is the clue. Your browser didn’t get a bad answer from the server. It got no answer at all. Before blaming a plugin, you need to know whether your request ever reached the server, because a timed-out connection is very often a network, DNS or firewall matter rather than anything inside WordPress.
How it differs from a slow page or a 504
These three get mixed up all the time:
- A slow page eventually loads. The server answered; it just took a while.
- A 504 Gateway Timeout is an actual error page from a server or proxy. Something answered you, to say that the piece behind it was too slow. We cover that in our post on what 502, 503 and 504 errors mean.
- ERR_CONNECTION_TIMED_OUT means your browser tried to open a connection to the server’s address and nothing completed the handshake in time. No HTTP response arrived at all.
So the question for this error is not “what is WordPress doing?” but “is anything at that address listening to me?”
The most likely reasons
The server’s firewall has blocked your IP address
This is the one that confuses people most, because the site works for everyone except you. Server firewalls on many hosts automatically block an IP address after repeated failed logins, whether to wp-admin, FTP, email or the control panel. Once blocked, connections from your address are silently dropped, which looks exactly like a timeout. An office where several people share one internet connection can be blocked because one person’s email client keeps trying an old password.
The domain points to the wrong place
If DNS still points to an old server after a move, or a record was edited by mistake, the browser is knocking on a door that nobody opens. This is common in the days after a migration or a change of nameservers, and it can look different on different networks while the change spreads. If you’re unsure which part is the domain and which is the hosting, our explainer on the difference between a domain and hosting sets it out simply.
The server is down or overwhelmed
A server that has crashed, been switched off, run out of disk space, or is under very heavy load may stop accepting new connections at all. In that case everyone sees the timeout, not just you.
HTTPS isn’t actually being served
If the site was moved to HTTPS but the server isn’t listening on port 443, or a firewall blocks that port, the http:// version might work while the https:// version times out. This also happens when a CDN is pointed at an origin that refuses its connections.
Your own network
Office firewalls, antivirus web filters, VPNs, and occasionally an internet provider’s routing problem can stop a connection to one particular server. The site is fine; the path from you to it isn’t.
WordPress itself, occasionally
A site that is extremely slow can look like a timeout in some situations, especially behind certain proxies. More often, though, WordPress-level slowness produces a slow load or a 504 rather than this error. Treat WordPress as the last suspect here, not the first.
Narrowing it down
None of the early checks below change anything on your site. Later ones do; before those, make sure the host’s most recent backup is in place, or take one, so changes to DNS or the server can be traced and reversed.
1. Change the network, not the browser
Switch your phone off Wi-Fi and load the site on mobile data. If it loads, the server is fine and something about your normal connection is the problem: an IP block, an office firewall or a local DNS cache. Trying a different browser on the same Wi-Fi tells you much less, because the network path is the same.
2. Ask someone elsewhere
A colleague in another city, or a friend abroad, can quickly tell you whether the site loads for them. Online “is it down” checkers do the same job. If it’s down everywhere, skip ahead to the server checks. If it’s only you, the firewall is the prime suspect.
3. Find your IP address and ask the host
Search “what is my IP” from the affected network and send that address to your host’s support, asking whether it is blocked on the server firewall. Hosts can usually unblock it quickly. Then find what caused the block, such as a saved wrong password in an email app or an FTP client, or it will happen again.
4. Check DNS
In your domain registrar or DNS provider’s panel, check that the A record (and AAAA record, if there is one) for the domain and for www points to the IP address your host gave you. A forgotten AAAA record pointing at an old server can cause timeouts only on networks that use IPv6, which makes the problem appear random. If you use Cloudflare, check the records there instead, since it then controls DNS.
5. Check the hosting account itself
Log in to the hosting control panel. Look for an account suspension notice, an unpaid invoice, a full disk or a server status warning. Hosts sometimes suspend accounts for resource abuse or unpaid renewals, and depending on how that’s done, visitors may see a timeout rather than a suspension page.
6. Test both http and https
Try http://yourdomain and https://yourdomain separately. If only the secure one times out, the certificate or port 443 is the issue, and the host or CDN settings need checking. Our older guide on adding an SSL certificate to your website covers the basics of that setup.
Optional: two quick commands
If you’re comfortable with a command prompt, two tools give useful evidence. On Windows open Command Prompt; on a Mac open Terminal.
nslookup yourdomain.comshows which IP address your computer thinks the domain points to. Compare it with the IP your host lists in the control panel. If they differ, DNS is your problem.tracert yourdomain.comon Windows, ortraceroute yourdomain.comon a Mac, lists the network hops between you and the server. If the trace stops at the last hop or two, the block is close to the server, which fits a firewall. If it stops early, near your own provider, the issue is more likely on your side of the internet.
Don’t read too much into ping on its own. Many servers ignore ping requests on purpose, so no reply doesn’t prove the server is down. Screenshots of these results are exactly what a host’s support team will ask for, and they save a round of back-and-forth.
7. Only then look inside WordPress
If the site connects but hangs before any content appears, open the server error log and WordPress’s debug log, if enabled. A line saying “Maximum execution time of 30 seconds exceeded” or an out-of-memory error points at a plugin or a heavy task. Renaming the wp-content/plugins folder over the file manager deactivates all plugins at once so you can test whether the hang comes from one of them; rename it back when you’re done.
Cases that are easy to miss
It only fails from the office
Almost always an IP block on the server, triggered by a device in the office repeatedly failing to log in to something. Fix the device, not just the block.
It fails on some phones but not others
Consider IPv6 and the AAAA record, or a mobile network that is still resolving the old DNS after a migration.
It started straight after a move
Check DNS first, then the CDN’s origin address, then whether the old host has already shut the server down. Our list of problems that follow a WordPress migration has more on this.
Preventing it
- When you change a password for hosting, email or FTP, update every device and app that stores it. Saved old passwords are the usual trigger for firewall blocks.
- Keep DNS records tidy and documented. Delete records for servers you no longer use.
- Plan migrations with DNS changes made at a quiet time, and keep the old server running until the new one is confirmed working everywhere.
- Use external uptime checks from more than one location, so you know whether an outage is global or local.
Getting help
If the site times out for everyone and the host can’t explain why, or you can’t tell whether DNS, the CDN or the server is at fault, it’s time to get someone who can look at all three together. Other errors that look similar are grouped in our WordPress error fix guide.
When the site is unreachable for customers, our emergency help for a WordPress site that’s down is where to start. Message us with your domain, where you tested from, and anything that changed recently. We work from India on IST and accept payment from abroad through PayPal or Wise, and nothing on the server gets touched until we’ve explained what we think is wrong.
Next in this series: “Are You Sure You Want to Do This?” WordPress Error
