If you run a WordPress site long enough, two things are guaranteed: it will break, and it will break at the worst possible moment.
Maybe you’re about to publish a post and the dashboard refuses to load. Maybe a reader messages you saying your site is blank. Maybe you updated a plugin and something that worked perfectly yesterday just… stopped. If any of that sounds familiar, this guide is for you.
The good news is that most WordPress errors are not mysterious. They follow patterns. Once you’ve seen the White Screen of Death twice, you stop panicking and start working through the checklist. This article is that checklist — written for bloggers and site owners who are not developers, but who need to fix their sites themselves.
WordPress powers over 40% of the web. That means millions of people have run into these exact problems before you, and the solutions are well-tested. Let’s go through them one by one.
The White Screen of Death — When Your Site Goes Completely Blank
You open your site and there’s nothing. No error message, no loading spinner — just a white page staring back at you. This is the White Screen of Death (WSOD), and while it looks catastrophic, it almost always comes down to one of two things: a plugin conflict or an exhausted PHP memory limit.
Fix 1: Increase Your PHP Memory Limit
Connect to your site via FTP or your hosting control panel’s file manager. Open the wp-config.php file in your WordPress root directory and add this line just before the comment that reads “That’s all, stop editing!”:
define(‘WP_MEMORY_LIMIT’, ‘256M’);
Save the file and refresh your site. If the screen is no longer white, you found the problem. Move on.
Fix 2: Deactivate All Plugins
If the memory fix didn’t work, a plugin is almost certainly the culprit. Since you may not be able to access your dashboard, do this through FTP: find the wp-content folder, locate the plugins folder inside it, and rename it to plugins_old. That single rename deactivates every plugin simultaneously.
Refresh your site. If it loads, you’ve confirmed it was a plugin. Rename the folder back to plugins, then reactivate each plugin one at a time from your dashboard — refreshing your site after each one — until the white screen returns. That’s your problem plugin. Delete it and find an alternative.
Fix 3: Switch to a Default Theme
If deactivating plugins didn’t fix it, your theme may be the issue. Via FTP, go to wp-content/themes and rename your active theme’s folder. WordPress will automatically fall back to a default theme. If your site now loads, the theme is the cause — contact the theme developer or switch themes entirely.
Internal Server Error (HTTP 500) — The Most Frustrating One
The 500 error is maddening because it gives you almost no information. The server encountered something unexpected, and it refuses to elaborate. Most of the time, it’s a corrupted .htaccess file or, again, a plugin.
Fix 1: Regenerate Your .htaccess File
Connect via FTP and find the .htaccess file in your WordPress root directory (you may need to enable hidden files in your FTP client — it’s hidden by default). Download a copy to your computer as a backup, then delete the original from the server.
Log into your WordPress dashboard, go to Settings → Permalinks, and without changing anything, just click Save Changes. WordPress will automatically regenerate a clean, correct .htaccess file. Check whether the 500 error is gone.
Fix 2: Memory Limit and Plugin Check
If regenerating .htaccess didn’t solve it, apply the PHP memory limit fix from the WSOD section above. Then try the plugin deactivation method. 500 errors and white screens often share the same root causes.
If neither of those resolves it, contact your hosting provider and ask them to check the server error logs. This is a completely normal support request — a good host will identify the exact cause within minutes.
Connection Timed Out — Your Site Just Won’t Load
A timeout error means your browser made contact with the server but the server took too long to respond. Usually this means a script is running too long, or your hosting plan is undersized for what your site is currently trying to do.
Fix 1: Deactivate All Plugins
Poorly coded plugins that create heavy database queries or endless loops are the most common cause of timeout errors. Use the folder-renaming method described above. If your site loads after deactivating plugins, reactivate them one by one to find the one causing the timeout.
Fix 2: Increase PHP Execution Time
Create or edit a php.ini file in your WordPress root directory (check your hosting documentation for the correct location — some hosts handle this differently) and add:
max_execution_time = 300
max_input_time = 600
memory_limit = 256M
These settings give scripts more time to complete before timing out. If your host doesn’t allow direct php.ini editing, contact support and ask them to increase these values for your account.
⚠ If timeout errors persist even after these fixes, your hosting plan may simply be too small for your site’s current needs. Shared hosting has hard limits that no amount of PHP tweaking can overcome. A managed WordPress host or VPS will solve it at the infrastructure level.
Error Establishing a Database Connection
This one is alarming because it usually means your site is completely down — not just slow, but actually unreachable. Your WordPress site depends on a MySQL database, and this error means it can’t connect. There are a few possible causes.
Check Your Credentials in wp-config.php
Open wp-config.php via FTP and look for these four values:
DB_NAME — your database name
DB_USER — your database username
DB_PASSWORD — your database password
DB_HOST — usually ‘localhost’, but varies by host
Log into your hosting control panel and navigate to the databases section. Verify that each value in wp-config.php exactly matches what’s shown there. Pay attention to capitalisation and special characters — a single wrong character breaks the connection.
If Credentials Are Correct: Database Repair
Sometimes the database itself gets corrupted. WordPress has a built-in repair tool. Add this line to your wp-config.php temporarily:
define(‘WP_ALLOW_REPAIR’, true);
Then visit: yourdomain.com/wp-admin/maint/repair.php and click the repair button. Once done, remove that line from wp-config.php immediately — leaving it active is a security risk.
If you can’t access phpMyAdmin through your hosting panel at all, this is a server-side problem and needs to go to your host’s support team.
404 Errors on Posts and Pages That Definitely Exist
You know a post exists. You can see it in your dashboard. But clicking the link gives you a 404. This is almost always a broken permalink structure — and it’s one of the easiest fixes in this entire guide.
Go to Settings → Permalinks in your dashboard. Without changing anything, just click Save Changes. That regenerates the rewrite rules. In most cases, your 404 errors will disappear immediately.
If they don’t, your .htaccess file may be missing or unwritable. Set .htaccess permissions to 644 via FTP, then try the permalink reset again. If you don’t see a .htaccess file in your root directory at all, create one and paste in the standard WordPress code block — your hosting documentation or the WordPress Codex has the exact content needed.
Your Sidebar Has Moved Below Your Content
This is a layout break rather than a technical error, and it always looks worse than it is. The culprit is almost always an unclosed HTML tag somewhere — either in a post you recently published or in a widget you recently added.
Start by reviewing your most recent content additions: the last post or page published, and any recently added or edited widgets. Look for missing closing tags — particularly </div> — in any custom HTML. Even a single unclosed tag can collapse your entire layout.
If your layout broke right after a theme update, switch temporarily to a default WordPress theme. If the sidebar returns to the correct position, the theme update introduced the bug. Contact the theme developer or roll back to the previous version.
Images Won’t Upload to the Media Library
Upload failures have three common causes: wrong file permissions, PHP upload limits that are too small, and a full disk. Start with the easiest check.
Fix 1: File Permissions
Via FTP, navigate to wp-content/uploads. The folder permissions should be 755. If they’re more restrictive, change them to 755 and try uploading again.
Fix 2: PHP Upload Limits
Create or edit a php.ini file in your WordPress root directory and add:
upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 300
These values increase the maximum file size WordPress will accept. Some hosting providers require you to make these changes through their control panel rather than directly — check their documentation.
Fix 3: Disk Space
Log into your hosting control panel and check how much disk space you’ve used. If you’re near or at your limit, WordPress cannot write new files. Delete old backups, remove unused themes and deactivated plugins, and clear out the Media Library of anything you no longer need.
Locked Out of Your WordPress Dashboard
Getting locked out feels drastic, but there are reliable ways back in without contacting your host.
First, try the “Lost your password?” link on the login screen. If the reset email doesn’t arrive within a few minutes, check your spam folder. If nothing comes at all, your site has an email delivery issue — that’s a separate problem but fixable.
If you can’t receive password reset emails, go to phpMyAdmin through your hosting control panel. Find the wp_users table, locate your username, and click Edit. In the user_pass field, generate a new MD5 hash using any free online MD5 generator, paste it in, and save. You can now log in with the password you used to generate that hash. Change it properly through your profile page immediately after.
If a security plugin locked you out — too many failed login attempts, suspicious activity detection — rename that plugin’s folder via FTP to deactivate it, regain access to your dashboard, then reactivate the plugin and adjust its lockout settings to something less aggressive.
Quick Reference: The Universal Troubleshooting Order
When something breaks and you don’t immediately know why, work through this order before anything else:
- Deactivate all plugins (folder rename via FTP).
- Switch to a default theme.
- Increase PHP memory limit to 256M in wp-config.php.
- Regenerate .htaccess by saving permalinks.
- Check database credentials in wp-config.php.
- If still broken: contact your host and ask them to check the server error logs.
Most WordPress errors you’ll ever encounter are solved somewhere in those six steps. Keep this article bookmarked. You’ll come back to it.
