Something broken on your WordPress site? You’re in the right place. Below are clear, step-by-step fixes for the most common WordPress errors — written for real site owners, not just developers. Find your problem, follow the guide, and get back online fast.
When Your Site Won’t Load at All
Error Establishing a Database Connection
A blank page that just says your site can’t reach its database. Usually wrong credentials, a corrupted database, or a downed server.
500 Internal Server Error
A generic server failure with no detail. Often a corrupted .htaccess, a plugin conflict, or an exhausted memory limit.
The White Screen of Death
A completely blank page with no error and no wp-admin. Usually a fatal PHP error from a plugin, theme, or core file.
Errors During Updates & Heavy Tasks
Briefly Unavailable for Scheduled Maintenance
Stuck in maintenance mode after an update? It’s a leftover file with a one-minute fix.
Allowed Memory Size Exhausted
A fatal “memory exhausted” error means a task needed more RAM than your server allows. Here’s how to fix it.
413 Request Entity Too Large
Can’t upload a theme, plugin, or media file? Your server’s upload limit is too low — here’s how to raise it.
⚠️ Can’t even log in to wp-admin?
When an error blocks the dashboard itself, you can still restore your site without logging in. See how Emergency Recovery works →
Email & Functionality
WordPress Not Sending Emails
Contact forms, password resets or order emails missing? Here’s why PHP mail fails and how to fix it with SMTP.
Security & Recovery
Hacked WordPress Site
Strange redirects, spam pages, or a Google warning? Spot the signs, clean the infection — or restore a clean backup.
Mixed Content & “Not Secure” SSL Errors
Moved to HTTPS but the browser still shows “Not Secure”? Leftover http:// resources are the cause — here’s how to fix them site-wide.
The Best Fix Is Prevention
Almost every error on this page goes from a site-down emergency to a five-minute fix when you have a recent backup ready. Instead of troubleshooting under pressure, you simply restore the last working version of your site. A few habits that make these errors a non-event:
- Keep automatic, off-site backups. See how to back up WordPress to Google Drive.
- Back up before every update — the most common trigger for these errors. Here’s how.
- Test risky changes on staging first, then push to live. Set up a staging site.
Turn any WordPress error into a quick restore
Nota Backup & Restore keeps automatic, off-site backups and lets you recover even when wp-admin is down. Start your 14-day free trial — no credit card required.