WordPress ERR_CONNECTION_TIMED_OUT

WordPress ERR_CONNECTION_TIMED_OUT - MakeWPFast
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

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

How to Fix It

  1. Check if the server is reachable: ping yourdomain.com and curl -I https://yourdomain.com
  2. SSH into the server and check services: systemctl status nginx and systemctl status php8.x-fpm
  3. Check PHP-FPM pool: ss -tlnp | grep php and look at pm.max_children in your pool config
  4. Check server load: top or htop u2014 if load average exceeds CPU count, the server is overloaded
  5. Check DNS: dig yourdomain.com u2014 verify the A record points to your server IP
  6. Restart web server and PHP-FPM: systemctl restart nginx php8.x-fpm
Related Errors
500 Internal Server Error in WordPressError Establishing a Database Connection
⚡

Diagnosing WordPress errors?

WP Multitool helps you find and fix performance issues, slow queries, and plugin conflicts without guesswork.

Try WP Multitool →
Get WordPress Performance Tips

Plugin reviews, speed optimization guides, and error debugging — straight to your inbox.

No spam. Unsubscribe anytime. We respect your privacy.