Skip to main content

How to Fix “There Has Been a Critical Error on This Website” in WordPress

  • By Md Sayfur Rahman
  • 6 min read
How to Fix “There Has Been a Critical Error on This Website” in WordPress

Seeing "There has been a critical error on this website" on your own site is worrying, especially when you cannot log in to fix it. But this error almost always has a clear cause, and in most cases you can fix it yourself without FTP, using only your hosting control panel.

This guide explains what the message means, why these errors happen more often than before, how to fix the error step by step, and the mistakes people often make while trying to fix it.

What the Critical Error Message Means

The message appears when PHP, the programming language WordPress runs on, hits a "fatal error" and cannot finish loading the page. Instead of showing a blank white screen, WordPress shows this short message to visitors. Since WordPress 5.2, it also tries to send an email to the site administrator with details about the problem.

That email has the subject "Your Site is Experiencing a Technical Issue". It tells you which plugin or theme caused the error, and it includes a special link to log in using recovery mode. In recovery mode, WordPress pauses the broken plugin or theme only for you, so you can open the dashboard and fix it while visitors still see the error page.

Why Critical Errors Happen More Often Now

Most critical errors are caused by code that does not work with the server it is running on. This happens more often today because of PHP versions. Many WordPress sites still run old versions of PHP, while new plugin and theme updates are written for newer versions. When the two do not match, the site can crash.

PHP versions used by WordPress sitesShare of sites
PHP 8.3About 25.7%
PHP 8.2About 24.5%
PHP 7.4About 16.7%
PHP versions that no longer get security updates (8.1 and older)About 37.6%

These numbers come from the official WordPress.org statistics. More than a third of WordPress sites run a PHP version that no longer receives security fixes, and PHP 7.4 reached its end of life back in November 2022. When a host finally upgrades PHP on these servers, or a site owner updates an old plugin, outdated code often stops working and causes a critical error.

The other common causes are a plugin update with a bug, two plugins that conflict, a theme that is too old for the current WordPress version, and a PHP memory limit that is too low for a large plugin like WooCommerce or a page builder.

How to Fix the Critical Error Step by Step

Work through these steps in order and stop when your site works again. You only need access to your hosting control panel and its file manager. Take a backup first if your host offers one, so you can undo any change.

  1. Check your email, including the spam folder. Look for the message "Your Site is Experiencing a Technical Issue" in the inbox of the site's admin email address. Click the recovery mode link, log in, and deactivate or update the plugin or theme it names.
  2. Turn on the debug log. If no email arrived, open the file manager, edit wp-config.php and add the debug lines shown below. Reload the page once, then open wp-content/debug.log. The last lines usually show the exact plugin or theme file that caused the error.
  3. Turn off the plugin that caused the error. In the file manager, open wp-content/plugins and rename the folder of the plugin named in the log, for example by adding "-off" to the end of the name. WordPress then deactivates it. If you do not know which plugin it is, rename the whole plugins folder, log in, then rename it back and turn plugins on one by one.
  4. Switch the theme if the error is in the theme. Rename your active theme's folder in wp-content/themes. WordPress will switch to a default theme such as Twenty Twenty-Five, if one is installed.
  5. Check the PHP version in your hosting panel. If the error started right after a PHP change, you can temporarily switch back to the previous version. This gives you time to update the plugin or theme properly instead of leaving the site down.
  6. Raise the memory limit if the log mentions memory. An error that says "Allowed memory size exhausted" means PHP needs more memory. Your host can raise the limit, or you can increase WP_MEMORY_LIMIT in wp-config.php.

For step 2, add these lines to wp-config.php, just above the line that says "That's all, stop editing". The last line keeps the error details hidden from your visitors.

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

When the site works again, change WP_DEBUG back to false. Leaving debug mode on can fill your server with large log files and show technical details to the wrong people.

Site down and no time to debug? Our team fixes critical errors and other WordPress emergencies fast. Request emergency help and we will start working on it immediately.

Mistakes People Often Make

In WordPress support forums, the same questions come up many times. One of the most common is "the error says check my email, but no email arrived". The WordPress documentation explains why this happens. The error can occur before your email plugin loads, so WordPress tries to send the email directly from the server, and many of these emails are blocked or sent to spam.

In one WordPress.org support thread, a site owner got the critical error one morning and never received the recovery email. With help from their host, they found the wp-content folder in the file manager, renamed the plugin they suspected, logged in, and deleted the broken plugin. The site worked again within minutes. This is the same method described in step 3.

Other common mistakes are easy to avoid.

  • Deleting plugins too quickly instead of renaming their folders. Deleting can remove settings and data that you need later.
  • Editing files without a backup, then making the problem worse.
  • Leaving debug mode on after the fix, so error details stay visible or log files keep growing.
  • Fixing the error on the live site with no idea what caused it, so it returns after the next update.

If the debug log shows strange file names, unknown plugins or code you did not add, the error may be caused by malware rather than an update. In that case, follow our guide on how to clean a hacked WordPress site.

How to Stop Critical Errors From Happening Again

Most critical errors appear right after an update, so the best protection is a better update routine. Test updates on a staging site first, update plugins regularly instead of letting them become very old, and plan PHP upgrades instead of waiting for your host to force them.

Always keep a recent backup that you can restore quickly, so a bad update costs you minutes and not days. Our guide to a WordPress backup strategy explains how to set this up, and our guide on updating WordPress safely shows a safer way to update.

If you prefer not to manage this yourself, our WordPress maintenance plans include tested updates, daily backups and monitoring, and we fix it free if an update we run ever breaks your site.

Written by

Md Sayfur Rahman

A website that doesn't break, doesn't slow down, and doesn't get hacked. Sounds like a fantasy. But it's exactly what I build. After more than 14 years in the WordPress ecosystem, I've learned that a truly great website isn't just about how it looks on launch day. It's about how it performs under pressure, how easy it is to manage, and how secure it remains as time goes on.