Every WordPress site breaks sooner or later. A plugin update goes wrong, the host has a bad night, an SSL certificate expires, or you edit one file you shouldn’t have. Suddenly your homepage is a blank page, a cryptic error code, or a browser warning your visitors won’t click past.
I’ve been there myself. Once my site went white after a theme problem, and once it threw a database error while I was restoring a backup. Both times the fix turned out to be simpler than the panic.
That’s the point of this guide. It collects the WordPress errors small business owners run into most, explains what each one actually means in plain English, and gives you the first thing to try. Where we’ve written a full step-by-step guide, you’ll find a link to it.
Start with the next section before touching anything. It covers three habits that make every fix below safer and faster.
Before You Fix Anything
1. Take a backup if you still can
If the dashboard or your hosting panel still opens, make a copy of your files and database first. Most hosts can do this in one click. That way, even a fix that goes wrong can be undone. Our guide to backing up and restoring a WordPress site shows how.
2. Check your email for “recovery mode”
When a plugin or theme crashes the site, WordPress usually emails the site admin a message with the subject “Your Site is Experiencing a Technical Issue”. It names the plugin or theme causing the problem and includes a special link that lets you log in and deactivate it. Check your inbox and spam folder before anything else.
3. Find out what the real error is
A blank page or a vague message hides the cause. Two places tell you more:
- Your hosting panel’s error log. Look for “Error Logs” or “Logs” in cPanel, hPanel or your host’s dashboard.
- WordPress debug mode. Open wp-config.php in File Manager and change the debug line to:
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
This writes errors to wp-content/debug.log without showing them to visitors. Open that file and look at the last few lines, which usually name the file and plugin at fault. Turn debug mode off again when you’re done.
The universal first fix
When you can’t tell what’s wrong, this works more often than anything else: in File Manager, rename the wp-content/plugins folder to plugins-off. That switches off every plugin at once. If the site comes back, rename the folder back and turn plugins on one by one in the dashboard until the problem returns.
Quick Lookup: Find Your Error
| Error you see | Most likely cause | Try this first |
| Blank white page | Plugin or theme crash, memory limit | Switch off plugins via File Manager |
| “There has been a critical error on this website” | Plugin or theme PHP error | Use the recovery mode email |
| 500 Internal Server Error | Broken .htaccess, plugin, PHP limits | Rename .htaccess, then switch off plugins |
| Error establishing a database connection | Wrong database details or server down | Check wp-config.php details |
| 502 / 503 / 504 | Server overloaded or timing out | Wait a few minutes, check host status |
| “Briefly unavailable for scheduled maintenance” | Update interrupted | Delete the .maintenance file |
| 403 Forbidden | File permissions or security rule | Check permissions and security plugins |
| Too many redirects | SSL or URL settings clash | Check Cloudflare SSL mode and site URLs |
| “Your connection is not private” | SSL certificate missing or expired | Renew or install SSL in hosting |
| 404 on every post | Broken permalinks | Settings → Permalinks → Save |
| Image upload “HTTP error” or file too big | Upload limits or memory | Raise limits or resize the image |
| Login keeps redirecting back | Cookies, URLs or a plugin | Clear cookies, check site URLs |
Errors That Take the Whole Site Down
White screen of death
A completely blank page, often on the front end, the dashboard or both. It’s almost always a plugin or theme conflict, or PHP running out of memory. Switch off plugins first, then try a default theme like Twenty Twenty-Five by renaming your theme’s folder. Full steps: how to fix the WordPress white screen of death.
“There has been a critical error on this website”
This is the newer version of the white screen. WordPress caught a PHP error and shows a polite message instead of a blank page. Look for the recovery mode email, which names the culprit. If it never arrived, use debug mode or the plugin-folder trick from the top of this guide.
500 Internal Server Error
A general “something went wrong on the server” message. The usual suspects are a corrupted .htaccess file, a plugin, or a PHP memory or version problem.
- In File Manager, rename .htaccess to .htaccess-old. If the site loads, go to Settings → Permalinks → Save Changes to create a fresh one.
- If not, switch off plugins.
- Check your PHP version in the hosting panel. Very old versions, or a jump to a much newer one, can break older plugins.
Error establishing a database connection
WordPress can’t reach its database. Usually the details in wp-config.php are wrong (common after moving hosts or restoring a backup), or the database server is down. Full steps: how to fix “Error establishing a database connection”.
502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout
These mean the server is overloaded, restarting or too slow to answer. Wait five minutes and reload. If it continues, check your host’s status page and your account’s resource usage. A plugin running heavy tasks, a traffic spike or a bot attack can all cause them. If they happen often, your hosting plan may be too small. See shared hosting vs VPS.
“Briefly unavailable for scheduled maintenance”
WordPress shows this during updates. If an update was interrupted, it can get stuck. In File Manager, open your site’s main folder, turn on “show hidden files”, and delete the file called .maintenance. Then rerun the update.
Access, Redirect and SSL Errors
Too many redirects
The browser bounces between two addresses until it gives up, usually http and https, or www and non-www. After adding SSL or Cloudflare, the most common cause is Cloudflare’s SSL mode set to Flexible. Switching it to Full (strict) fixes most cases. Full steps: how to fix “Too many redirects” in WordPress. If you’re new to Cloudflare, Cloudflare for beginners explains the settings.
“Your connection is not private”
Visitors see a full-page browser warning because your SSL certificate is missing, expired or doesn’t match the domain. Most hosts include free SSL, so this usually means renewing or reinstalling it. Full steps: how to fix “Your connection is not private” on your own website.
403 Forbidden
The server is refusing access. Common causes are wrong file permissions, a security plugin or firewall rule blocking you, or a bad .htaccess rule. Try renaming .htaccess first, then temporarily switching off security plugins. Folders should normally have permissions of 755 and files 644. Your host can check and reset them if you’re unsure.
Login keeps redirecting back to the login page
You enter the right password and land back on the login screen. Clear your browser cookies for the site, then check that WordPress Address and Site Address match exactly, including https and www. A caching or security plugin can also cause this, so switch them off if the problem stays.
Page, Upload and Memory Errors
404 “Page not found” on every post
Your homepage works, but every post or page shows a 404. This usually happens after a migration or a change to permalink settings. Go to Settings → Permalinks and click Save Changes without changing anything. That rebuilds the rules WordPress uses for links. If you’ve just moved hosts, also check our guide to moving a WordPress site to a new host.
“Allowed memory size exhausted”
PHP ran out of memory, often on bigger plugins like page builders or WooCommerce. Ask your host to raise the PHP memory limit, or add this line to wp-config.php above the “stop editing” line:
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
This only works up to the limit your hosting plan allows.
Image upload fails or “file exceeds the maximum upload size”
The file is bigger than your server allows, or the server ran out of memory while processing it. Resize large photos to around 2,000 pixels wide and compress them before uploading, which also makes your site faster. If you regularly upload big files, ask your host to raise the upload limit.
Mixed content warnings
The page loads over HTTPS, but some images or scripts still use http, so browsers show a “not fully secure” warning. Update old http links to https with a search-and-replace plugin, and make sure both site URLs in Settings → General start with https.
Slow Site and Email Problems
These don’t take your site down, but they quietly cost you visitors and enquiries.
The site is slow
A slow site is usually heavy images, too many plugins, no caching or underpowered hosting. Work through how to speed up a slow WordPress site before paying for more hosting. Picking the right caching plugin helps a lot. See LiteSpeed Cache vs WP Rocket.
Contact form emails never arrive
WordPress sends mail through the web server by default, and those emails often land in spam or vanish. The reliable fix is to send through a real email account using an SMTP plugin, connected to a business mailbox such as Google Workspace. Also make sure your domain has SPF, DKIM and DMARC records, so receiving servers trust your emails. Our guide to SPF, DKIM and DMARC in Cloudflare walks through it.
How to Avoid Most of These Errors
You can’t stop every problem, but a few habits prevent most of them:
- Back up automatically, daily for the database and weekly for files, stored off the server.
- Update one thing at a time, and check the site after each plugin or theme update instead of clicking “update all”.
- Use a staging site for big changes if your host offers one. Many do, free.
- Keep plugins lean. Delete anything you don’t use, and avoid plugins that haven’t been updated in a year.
- Choose solid hosting. Cheap, overloaded servers cause many 5xx errors and slow pages. Our picks of the best web hosting for small businesses and Hostinger vs SiteGround can help.
- Understand your setup. Knowing where your domain, DNS and hosting live makes every fix faster. Domain, hosting and DNS explained covers the basics.
When to Call Your Host or a Developer
Get help when:
- the error stays after you’ve switched off plugins and changed the theme;
- your host’s status page shows a problem, or phpMyAdmin won’t open;
- you suspect the site has been hacked (strange redirects, spam pages, unknown admin users);
- you’ve been down for more than an hour and it’s costing you customers.
Your host’s support can see server logs you can’t, and fixes many 5xx and database problems in minutes. On a VPS, though, much of this is your responsibility, so check managed vs unmanaged VPS before you choose one. When you contact support, include the exact error, when it started and what you’ve already tried.
See also: Best Web Hosting in India for a WordPress Site · How to Set Up Professional Email on Your Own Domain With Google Workspace (Step by Step) · Small Business Cybersecurity: The Complete Guide · AI for Small Business: A Practical Guide to Tools, Automation and Privacy · The Small Business Software Stack: What You Actually Need (and What It Costs)
More step-by-step fixes for problems you might run into:
- How to fix the 403 Forbidden error
- WordPress site hacked? A calm clean-up guide
- How to fix WordPress emails not sending
- How to secure your WordPress login
- Core Web Vitals explained for WordPress
FAQ
What is the most common WordPress error?
Plugin or theme conflicts, which show up as a white screen, a “critical error” message or a 500 error. Switching off plugins is the fastest first test.
How do I fix WordPress if I can’t log in to the dashboard?
Use your hosting panel’s File Manager. You can switch off plugins by renaming the plugins folder, change themes by renaming the theme folder, and edit wp-config.php directly.
Will fixing these errors delete my content?
No. Your posts and pages live in the database, and none of the fixes in this guide touch your content. Taking a backup first keeps you safe anyway.
How do I turn on WordPress debug mode?
Set WP_DEBUG to true in wp-config.php, with WP_DEBUG_LOG true and WP_DEBUG_DISPLAY false. Errors are then saved to wp-content/debug.log. Switch it off when you’re finished.
Why does my site show different errors to different people?
Caching. Some visitors see an old cached version while others see the live problem. Purge your caching plugin and Cloudflare cache after every fix.
Do WordPress errors hurt SEO?
Short outages don’t. If the site is down for days, Google may drop pages from search. Fix errors quickly and check Google Search Console afterwards.
Final Word
Most WordPress errors look far scarier than they are. Nearly all of them come down to a handful of causes: a plugin or theme, a settings mismatch, an SSL or Cloudflare setting, or a server under strain.
Keep a backup, check the recovery email, read the error log, and switch off plugins when in doubt. Bookmark this page, so next time your site breaks you can find the right fix in a minute instead of an hour.


