WordPress ERR_CONNECTION_TIMED_OUT

Critical Frequency: Uncommon

Error message: ERR_CONNECTION_TIMED_OUT — This site can't be reached

ERR_CONNECTION_TIMED_OUT means the browser couldn’t establish a connection to the server within the timeout period (usually 30 seconds). Unlike a 500 error, the server isn’t responding at all.

Common Causes

Web server (Apache/nginx) is down or not responding
PHP-FPM workers are all busy (max_children exceeded)
Server is overloaded (CPU/memory maxed out)
DNS not resolving to the correct IP address
Firewall blocking the connection (server-side or ISP)
DDoS attack consuming all server resources

How to Fix It

Check if the server is reachable: ping yourdomain.com and curl -I https://yourdomain.com
SSH into the server and check services: systemctl status nginx and systemctl status php8.x-fpm
Check PHP-FPM pool: ss -tlnp | grep php and look at pm.max_children in your pool config
Check server load: top or htop u2014 if load average exceeds CPU count, the server is overloaded
Check DNS: dig yourdomain.com u2014 verify the A record points to your server IP
Restart web server and PHP-FPM: systemctl restart nginx php8.x-fpm

Frequently Asked Questions

What's the difference between a timeout and a 500 error?

A timeout means the server didn't respond at all u2014 it's unreachable or too busy. A 500 error means the server responded but with an error. Timeouts are usually server infrastructure issues; 500 errors are usually application-level issues.

My site times out intermittently. What's wrong?

Intermittent timeouts usually indicate PHP-FPM running out of workers during traffic spikes. Check your pm.max_children setting and consider increasing it or optimizing slow PHP scripts.