Last Updated July 22, 2026
The most common WordPress errors are the white screen of death, the 500 internal server error, “error establishing a database connection,” being stuck in maintenance mode, 404 errors, the memory exhausted error, and login redirect loops. Most are caused by plugin conflicts, PHP or memory limits, or a corrupted .htaccess file, and over 90% can be fixed in under 30 minutes once you know the cause.
We fix these errors on client sites all the time, and the pattern is reassuring: the scary-looking ones are usually the quickest to solve. A blank white page feels like your site is gone forever, when the real fix is often deactivating one plugin. This guide covers the errors you are most likely to hit, what each one actually means, and the exact steps to fix it, starting with the one habit that makes every error easier to solve.
Before you fix anything: two habits that save you
Two habits solve or prevent most WordPress errors, and skipping them is how people turn a small problem into a disaster.
First, always back up before you touch anything. Even a broken site should be backed up before you start, because some fixes (editing files, cleaning the database, reinstalling core) can make things worse if something goes wrong mid-fix. A backup is your way back.
Second, turn on debug logging so you can see the real error instead of a generic blank screen. Add these lines to your wp-config.php file, above the line that says “That’s all, stop editing”:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false );This records the exact plugin, theme, or file behind most failures to a log file, turning a vague error into a specific, fixable cause. On a live site, log the error, do not display it to visitors.
One more useful fact: your content is almost always safe. Most WordPress errors are code or configuration problems, and your posts, pages, and settings sit in the database untouched. The site looks dead; your data is fine.
The White Screen of Death
The white screen of death is a completely blank page with no error message, usually caused by a plugin conflict, a theme problem, or an exhausted PHP memory limit. It is alarming because it gives you nothing to work with, but it is one of the most fixable errors.
Fix it in this order. Deactivate all plugins by renaming the /wp-content/plugins folder to plugins_old over FTP; if the site returns, rename it back and reactivate plugins one at a time until the culprit reappears. If plugins are not the cause, switch to a default theme like Twenty Twenty-Four by renaming your active theme folder.
If it is still blank, increase the PHP memory limit (see the memory error below). With debug logging on, the log will often name the exact file causing the crash.
500 Internal Server Error
The 500 internal server error is a server-side failure that means something broke while loading your page, but the message gives no clue what. The usual causes are a corrupted .htaccess file, an exhausted memory limit, a plugin or theme conflict, or an incompatible PHP version.
The fastest fix first: connect over FTP, open the root folder where wp-config.php lives, and rename .htaccess to .htaccess_old. Reload your site. If it works, go to Settings, then Permalinks in wp-admin, and click Save Changes to generate a fresh .htaccess file.
This single step resolves a large share of 500 errors. If that does not do it, deactivate all plugins via FTP as above, then raise the PHP memory limit. Because a 500 is server-side, the fix is usually a configuration reset, not a rebuild.
Error Establishing a Database Connection
This error means WordPress cannot reach the MySQL database where all your content lives, so nothing can display. It typically appears suddenly, often after a host migration, a credentials change, or a database crash on the server.
Start by opening wp-config.php and confirming that DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST exactly match what your hosting panel shows. A mismatch, common after a migration, is the most frequent cause. If the credentials are correct, the database server itself may be down or overloaded, which happens on shared hosting during traffic spikes, so contact your host.
Corrupted database tables are another cause, repairable by adding define( 'WP_ALLOW_REPAIR', true ); to wp-config.php and visiting the repair page. If your admin still loads but the front end is down, the issue is often a single corrupted table rather than the whole connection.
Stuck in Maintenance Mode (“Briefly Unavailable for Scheduled Maintenance”)
This message appears while WordPress installs an update, controlled by a hidden .maintenance file, and your site gets stuck when an update is interrupted and that file never gets deleted. It locks out visitors and admins alike.
The fix takes under two minutes and works in nearly every case: connect over FTP or your host’s file manager, open the root directory, and delete the .maintenance file. Your site returns immediately. If the update was left half-finished, you may then need to reapply it.
To prevent it happening again, update plugins one at a time rather than in bulk, since a single timeout in a bulk update chain can leave the whole site stuck, and update on staging first when your host offers it. WordPress is supposed to clear this lock automatically after ten minutes, so if it does not, the file is genuinely stuck and needs manual deletion.
Memory Exhausted Error
The “Allowed memory size exhausted” error happens when WordPress needs more PHP memory than your hosting allows, often triggered by a heavy plugin, a complex theme, or too many plugins running at once. It can show as a white screen or a direct memory message.
Increase the limit by adding this line to wp-config.php, above the “stop editing” line:
define( 'WP_MEMORY_LIMIT', '256M' );If the limit will not rise, your host may cap it, in which case you adjust php.ini or ask your host. Memory is one of the most under-configured settings on shared hosting, so raising it also prevents stuck updates and white screens. If you constantly hit the ceiling, the real answer is fewer heavy plugins or a hosting plan with more resources.
404 Errors on Posts and Pages
When individual posts return a 404 “not found” error while your homepage works fine, the cause is almost always broken permalinks, often after a migration or an .htaccess change. The content exists; WordPress just cannot route to it.
The fix is usually one click: go to Settings, then Permalinks, and click Save Changes without altering anything. This regenerates the rewrite rules and the .htaccess file, restoring your URLs. If posts still 404, confirm your .htaccess file exists and is writable, and check that mod_rewrite is enabled on your server. For genuinely deleted or moved pages, set up proper 301 redirects with a plugin like Redirection so visitors and search engines land somewhere useful.
Login Page Redirect Loop
In a login redirect loop, you enter correct credentials but WordPress sends you straight back to the login page in an endless cycle. It is usually caused by incorrect site URL settings, a plugin conflict, or corrupted browser cookies.
Start simple: clear your browser cookies and cache, since stale cookies cause this more often than people expect, then try a different browser. If that fails, confirm your WordPress Address and Site Address are correct in wp-config.php by adding WP_HOME and WP_SITEURL lines, and deactivate plugins over FTP to rule out a conflict. Login and security plugins are frequent culprits here.
403 Forbidden and Too Many Redirects
Two more you will likely meet. A 403 Forbidden error means the server is refusing access, usually from incorrect file permissions, a security plugin, or a corrupted .htaccess file; fix it by regenerating .htaccess (Save Permalinks), checking folder permissions (755 for folders, 644 for files), and testing with security plugins off. The ERR_TOO_MANY_REDIRECTS error means your site is caught in a redirect cycle, typically from a misconfigured URL setting, an SSL/HTTPS plugin, or a caching issue; fix it by clearing all caches, checking your site URL settings, and reviewing any redirect or SSL plugin.
How to prevent WordPress errors in the first place
Most WordPress errors trace back to a few preventable causes, and plugins lead the list. According to Patchstack, 96% of WordPress vulnerabilities in 2024 originated from plugins, and plugin conflicts cause a large share of the errors above too. Prevention is mostly discipline.
Keep core, themes, and plugins updated, but update one at a time and test after each. Use a staging environment for updates and changes so nothing risky touches your live site. Choose quality plugins and delete ones you do not use, since inactive plugins still carry risk.
Keep automated backups running so any error is a quick restore rather than a crisis. Give your site enough PHP memory and modern PHP (8.x) through decent hosting. Do these consistently and most of the errors in this guide simply stop happening.
Conclusion
Common WordPress errors look frightening but are usually quick to fix once you know the cause. Back up first, turn on debug logging to see the real error, and remember your content is almost always safe in the database. The white screen and 500 error usually come down to a plugin conflict or a corrupted .htaccess file.
Database errors trace to wp-config credentials, especially after a migration. Stuck maintenance mode is a leftover .maintenance file you delete in two minutes. And since plugins cause most errors and most vulnerabilities, disciplined updates, staging, quality plugins, and backups prevent the majority of problems before they start.
Frequently Asked Questions
What are the most common WordPress errors?
The most common are the white screen of death, the 500 internal server error, “error establishing a database connection,” being stuck in maintenance mode, 404 errors on posts, the memory exhausted error, the login redirect loop, and the 403 Forbidden error. Most stem from plugin conflicts, memory limits, or a corrupted .htaccess file.
Will I lose my content when WordPress shows an error?
Almost never. Most WordPress errors are code or configuration problems, and your posts, pages, settings, and users are stored safely in the database. The site may look completely down while your data sits untouched. Still, always back up before troubleshooting, in case a fix goes wrong.
How do I find out what is causing a WordPress error?
Enable debug logging by adding WP_DEBUG and WP_DEBUG_LOG to your wp-config.php file. With logging on, WordPress records the exact plugin, theme, or file behind most failures to a log, turning a vague error into a specific, fixable cause. It is the first step for nearly every error.
How do I fix the white screen of death in WordPress?
Deactivate all plugins by renaming the wp-content/plugins folder over FTP. If the site returns, reactivate plugins one at a time to find the culprit. If not, switch to a default theme, then increase the PHP memory limit. Debug logging will often name the exact file causing the crash.
How do I fix WordPress stuck in maintenance mode?
Connect to your site over FTP or your host’s file manager, open the root directory, and delete the hidden .maintenance file. Your site returns immediately. This happens when an update is interrupted, so afterward, update plugins one at a time instead of in bulk to prevent it recurring.
Can I fix WordPress errors without a developer?
Yes, most of them. Over 90% of common WordPress errors can be fixed in under 30 minutes with FTP access and clear steps, no coding required. That said, recurring errors, database corruption, or a hacked site are worth handing to a professional before you risk making things worse.
Too many WordPress errors? Let someone else handle it.
Fixing the occasional error yourself is fine. But if your site keeps breaking, or an error is costing you visitors right now, you do not have to sort it alone. Survyc fixes WordPress errors and keeps sites stable with ongoing maintenance, so problems get caught before your visitors ever see them. Reach out to Survyc and tell us what is broken, and we will get your site working again.
