Common WordPress Errors Explained (and What to Do About Them)
Plain-English explanations of common WordPress errors (white screen, critical error, 500 errors, database connection errors, 404s and maintenance mode) and safe first steps to fix them.
On this page
- Most critical errors and white screens come from a plugin or theme conflict after an update.
- Database, 500 and 404 errors have common causes your host's error logs usually reveal.
- Don't change things at random: note what changed, check backups and get logs.
Few things are more stressful than opening your website and seeing an error instead of your homepage. Most WordPress errors have common causes and safe fixes. Here's what they mean and what to do first. If you're not comfortable with technical steps, share this with your developer.
"There has been a critical error on this website"
Usually: a plugin or theme conflict, often right after an update.
First steps: check the site admin's email for WordPress's recovery mode link, which lets you log in and deactivate the faulty plugin. Otherwise, a developer can disable plugins via hosting file access.
Step-by-step guide: how to fix "There has been a critical error".
White screen (blank page)
Usually: a PHP error or exhausted memory.
First steps: think about what changed recently (update, new plugin). Restore the last backup or disable the latest plugin. Your host can check error logs.
500 Internal Server Error
Usually: a server configuration issue, corrupted .htaccess file, plugin error or hosting resource limits.
First steps: check your hosting account for resource warnings and ask your host for the error log, which tells you exactly what failed.
"Error establishing a database connection"
Usually: the database server is down, the database credentials changed, or the database is corrupted.
First steps: check your host's status page. If the host is fine, the database details in the site's configuration may need correcting. This often appears after migrations.
404 errors on pages that should exist
Usually: permalink settings or redirects broke after a change or migration.
First steps: re-save permalinks (Settings → Permalinks → Save). If URLs changed, set up 301 redirects; see redesigning without losing rankings.
"Briefly unavailable for scheduled maintenance"
Usually: an update was interrupted.
First steps: a leftover maintenance file needs removing via hosting file access, then the interrupted update should be re-run.
Browser security warnings
Usually: an SSL certificate problem, or Google has flagged malware.
First steps: see SSL certificate errors explained and signs your site is hacked.
Warnings caused by a hack? See removing WordPress malware step by step.
Golden rules when something breaks
- Don't keep clicking update or changing settings at random
- Note what changed just before the error
- Check your backups; see the backup and restore guide
- Get error logs from your host, because they usually point to the cause
Most of these errors are prevented by careful updates, backups and monitoring; see updating WordPress safely and maintenance plans.
Need help with your website?
I'm Sameer, a freelance WordPress developer building fast, SEO-friendly websites since 2020. Tell me what you need and I'll reply with a plan and a fixed quote within 24 hours.
Freelance WordPress developer and founder of Samverse, building websites for clinics, manufacturers, agencies and online stores since 2020.
More about me
