Most WordPress errors come from five causes: a plugin conflict, a theme update, a PHP memory or version problem, a broken .htaccess file, or a database connection issue. Take a backup, turn on debug logging, then disable plugins one by one and switch to a default theme. That simple order fixes the large majority of errors in under an hour.
- Always back up the site before you touch files or the database.
- The error message itself usually names the guilty plugin or theme folder. Read it slowly.
- Renaming the plugins folder over FTP or File Manager is the fastest way to test for a plugin conflict.
- WordPress Recovery Mode emails you a special login link when a fatal error happens. Check your inbox first.
- If the fix needs database or server changes you are not comfortable with, stop and get help before you make it worse.
Why do WordPress errors happen in the first place?
Picture a small bakery owner who clicks “Update all” on a Monday morning. Ten plugins update at once, one of them needs a newer PHP version than the hosting account runs, and the homepage turns into a blank page with the words “There has been a critical error on this website.”
Nothing was hacked and nothing is lost. Two pieces of software simply stopped agreeing with each other. That is what most WordPress errors are: a disagreement between WordPress core, a plugin, a theme, PHP and the server. Once you know which piece changed last, you know where to look.
What should you do before fixing any WordPress error?
- Take a backup. Use your host’s backup tool or a plugin such as UpdraftPlus if you can still reach the dashboard. Download a copy of the files and the database.
- Check your email. Since WordPress 5.2, a fatal error sends the admin email a Recovery Mode link that lets you log in with the broken plugin paused.
- Turn on the debug log. In wp-config.php set
WP_DEBUGto true,WP_DEBUG_LOGto true andWP_DEBUG_DISPLAYto false. Errors are then written to wp-content/debug.log instead of being shown to visitors. - Write down what changed. An update, a new plugin, a host migration or a PHP switch? The last change is the first suspect.
Which WordPress errors are the most common, and what fixes them?
| Error | Usual cause | First fix to try |
|---|---|---|
| There has been a critical error on this website | PHP fatal error in a plugin or theme | Use the Recovery Mode email, or rename the plugin folder named in debug.log |
| White screen of death | Fatal error with display turned off, or memory limit | Enable the debug log, raise WP_MEMORY_LIMIT to 256M |
| Error establishing a database connection | Wrong DB details in wp-config.php or database server down | Check DB_NAME, DB_USER, DB_PASSWORD and DB_HOST against your hosting panel |
| 500 Internal Server Error | Broken .htaccess, PHP error or server limits | Rename .htaccess, then re-save Settings, Permalinks |
| 404 on every page except the homepage | Rewrite rules lost | Settings, Permalinks, click Save without changing anything |
| Briefly unavailable for scheduled maintenance | An update was interrupted | Delete the .maintenance file in the site root |
| Memory exhausted | PHP memory limit too low | Add define(‘WP_MEMORY_LIMIT’, ‘256M’); and ask the host to raise PHP memory |
| Too many redirects | Wrong site URL, SSL or CDN loop | Check WordPress Address and Site Address, then the SSL mode at Cloudflare or your host |
| Upload failed / missing a temporary folder | Folder permissions or upload size limit | Set folders to 755, files to 644, raise upload_max_filesize |
| Connection timed out | Heavy plugin or overloaded shared hosting | Find the slow plugin with Query Monitor, then consider better hosting |
How do you find out which plugin is causing the error?
If you can log in, go to Plugins, deactivate everything, and check the site. If the error is gone, reactivate plugins one at a time and reload after each one. The plugin that brings the error back is your culprit.
If you cannot log in, open File Manager in your hosting panel or connect by FTP, go to wp-content, and rename the plugins folder to plugins-off. WordPress will deactivate all plugins. Rename it back, then rename individual plugin folders to narrow it down.
The free Health Check and Troubleshooting plugin can do the same test only for your own login session, so visitors keep seeing the normal site while you investigate.
Share the error or a screenshot and get a free diagnosis. Most WordPress errors are fixed the same day, with a backup taken first.
How do you tell if the theme is the problem?
Switch to a default theme such as Twenty Twenty-Five. If you cannot reach the dashboard, rename your active theme’s folder inside wp-content/themes and WordPress falls back to a default theme it can find. If the error disappears, the theme or your child theme’s functions.php is the cause. A missing semicolon in functions.php is one of the most common self-inflicted errors on WordPress sites.
When is the problem the server, not WordPress?
Check these when plugins and themes are ruled out:
- PHP version: WordPress recommends PHP 8.3 or newer. Very old PHP versions break modern plugins, and a jump to a much newer version can break old ones.
- Disk space and inode limits: a full hosting account causes failed uploads and broken updates.
- Database server: if several sites on the same host show database errors, the host has an outage. Open a ticket.
- Security rules: a firewall (ModSecurity or a CDN WAF) can block saves in the editor and show 403 errors.
How do you stop these errors coming back?
- Update plugins in small groups, not all at once, and test the site after each group.
- Use a staging copy for big updates such as WooCommerce, Elementor or a theme major version.
- Keep daily off-site backups and test a restore at least once.
- Remove plugins you no longer use. Every plugin is code that can break.
- Choose hosting that runs a supported PHP version and gives you error logs.
For a deeper look at the two errors that scare people most, read the guides to fixing the white screen of death and fixing WordPress emails that never arrive.
Frequently asked questions
What is the most common WordPress error?
The critical error message (previously the white screen) caused by a PHP fatal error in a plugin or theme is the most common. The Recovery Mode email and the debug log tell you which plugin caused it.
Will I lose my content when WordPress shows an error?
Almost never. Posts and pages live in the database, which errors rarely touch. Take a backup before fixing anything, just in case.
How do I fix WordPress if I cannot log in?
Use your hosting File Manager or FTP to rename the plugins folder, or the active theme folder. That disables them so you can log in again and investigate.
Is it safe to raise the PHP memory limit?
Yes. 256M is a normal value for modern WordPress sites. If the site still runs out of memory, find the heavy plugin instead of raising the limit further.
When should I hire someone to fix WordPress errors?
When the error involves the database, a hacked site, a failed migration, or when it affects sales and you cannot fix it within an hour. A professional can usually fix it faster and safer.
Sources
Share the error or a screenshot and get a free diagnosis. Most WordPress errors are fixed the same day, with a backup taken first.
More WordPress guides
Guide, 4 min readWordPress Not Sending Emails? The Complete Fix (2026 Guide)
Guide, 4 min readHow to Fix the WordPress White Screen of Death (2026 Guide)
Guide, 3 min readHow to Price Your WordPress Services for Clients (2026 Guide)
Guide, 4 min readHow to Recover a Hacked WordPress Website (2026 Guide)Rather have an expert run your WordPress site?
Tanvir H is a Bangladesh-based WordPress and Elementor web designer with 7+ years of experience, 650+ projects and a 4.9 client rating. New websites, redesigns, fixes, speed, security and SEO, handled by one expert who explains everything in plain English and works with clients worldwide.
