Common WordPress Errors and How to Fix Them

Your browser tried to connect to the website server, but the server didn't respond in time. The connection attempt timed out after waiting for a response.

Overloaded hosting server sharing resources with too many other sites, a traffic spike overwhelming the server, faulty network configuration, or the server being down for maintenance.

Check if other sites on the same hosting account are also down - if so, contact your hosting provider. If it's just your site, try restarting your server from your hosting control panel. A temporary traffic spike might resolve on its own. For recurring timeouts, upgrade to a plan with dedicated resources.

A generic error message indicating something went wrong on the server side, but the server couldn't be more specific about what.

A corrupt .htaccess file, a PHP memory limit that's too low, a plugin or theme conflict after an update, or corrupted WordPress core files.

Rename your .htaccess file (via FTP or cPanel) to disable it - WordPress will generate a fresh one. If that doesn't work, temporarily disable all plugins by renaming the plugins folder. Switch to a default WordPress theme (Twenty Twenty-Four) via FTP. If none of these work, increase PHP memory limit in wp-config.php.

The domain name you're trying to reach cannot be found in the DNS system. It's like dialling a phone number that isn't assigned to anyone.

The domain has expired, DNS records were changed recently and haven't propagated, the domain is misconfigured in your hosting control panel, or the nameservers are pointing to the wrong place.

Check your domain registration status immediately - an expired domain is the most common cause. Use a DNS propagation checker to see if recent changes are still spreading. Verify nameserver settings are correct in your domain registrar. If you've recently changed hosts, DNS can take up to 48 hours to fully propagate.

A fatal PHP error has occurred that prevented WordPress from loading. WordPress 5.2+ shows this message instead of the old white screen, with an email sent to the admin address with more detail.

A plugin or theme update that introduced incompatible PHP code, a PHP version upgrade that broke older code, or memory exhaustion caused by a misbehaving plugin.

Check the email WordPress sent to your admin address - it will tell you which plugin or theme caused the error. Access your site via FTP and either rename the offending plugin folder or switch to a default theme. Enable WP_DEBUG in wp-config.php to see the actual PHP error message.

A completely blank white page with no error message or content. The page loads but nothing is displayed - no header, no footer, nothing at all.

PHP memory exhaustion (most common), a PHP error that crashes output before anything is rendered, a corrupted plugin or theme, or a fatal PHP error with error reporting disabled.

Increase PHP memory limit in wp-config.php by adding define('WP_MEMORY_LIMIT', '256M');. Disable all plugins by renaming the /wp-content/plugins/ folder via FTP. Switch to a default theme by renaming your active theme folder. Clear your browser and server cache.

WordPress cannot connect to the MySQL database that stores all your content, settings, and user data. Without the database, WordPress cannot function.

Incorrect database credentials in wp-config.php, the database server is down or overloaded, the database has been corrupted, or your hosting account's database user permissions were changed.

Double-check database name, username, password, and host in wp-config.php. Log into your hosting control panel and verify the database exists. Repair the database by adding define('WP_ALLOW_REPAIR', true); to wp-config.php and visiting /wp-admin/maint/repair.php. Contact your host if the database server itself is down.

Your IP address has been temporarily blocked because it sent too many requests to the server in a short period. This is a rate-limiting measure to prevent abuse.

A plugin or security tool with overly aggressive rate limiting configured, a misconfigured caching plugin, repeated login attempts triggering brute force protection, or a web application firewall blocking legitimate traffic.

Wait 5-10 minutes and try again - most rate limits reset automatically. If you're locked out of wp-admin, access your site via FTP and temporarily disable security plugins. Check your security plugin settings and increase rate limit thresholds. Whitelist your IP address in your security plugin or WAF if needed.

The server understood your request but is refusing to fulfil it. You don't have permission to access the requested resource.

Incorrect file permissions set on WordPress files or folders, a security plugin blocking access too aggressively, a corrupted .htaccess file with restrictive rules, or the server's index file is missing.

Check file permissions - folders should be 755, files should be 644 (use FTP to verify and correct). Rename .htaccess to disable it temporarily. Deactivate security plugins via FTP and check if access is restored. Verify an index.php or index.html file exists in the directory.