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

When you see the message "there has been a critical error on this website," it means a PHP script on your site has failed, usually in a plugin or theme, and WordPress has stopped the page rather than show a broken one. This guide explains how to use the admin email link to regain access, read your error logs to find the exact cause, and fix the faulty plugin or theme, including what to do if the recovery email never arrives.

What Causes the "There Has Been a Critical Error on This Website" Message?

"WordPress displays the message… to inform you that “a piece of its code — a PHP script to be precise — has failed to run to completion”." — WPMarmite

This specific error message is a vast improvement over the blank "White Screen of Death" that plagued sites before WordPress 5.2. Instead of leaving you entirely in the dark, WordPress now halts the failing script and alerts you.

While it feels alarming, the error is usually tied to a few common triggers. According to an analysis of 2,847 cases, “plugin conflicts account for 65% of WordPress critical errors”. The second most frequent cause is PHP memory limit exhaustion at 23%, followed by corrupted core files at 12%.

Other potential culprits include broken theme code (especially if you recently edited your functions.php file), obsolete PHP versions on your server, or exhausted server storage limits.

How to Use WordPress Recovery Mode and the Admin Email Link

Since version 5.2, when a plugin or theme causes a fatal PHP error, WordPress emails the site administrator a one-time link to Recovery Mode. The link opens a private session in which the broken plugin or theme is paused for you alone, so you can log in and fix it. Visitors keep seeing the error until you do.

Here is how to use the email link to fix the issue:

1. Check your inbox: Look for an email with the subject line "Your Site is Experiencing a Technical Issue." Be sure to check your spam or junk folder.
2. Click the recovery link: The email names the plugin or theme that crashed, then gives a long link containing enter_recovery_mode. Click it; it works for one day.
3. Log in: Enter your standard WordPress admin username and password.
4. Identify the culprit: A notice at the top confirms you are in recovery mode. On the Plugins screen (or Appearance → Themes), the item that crashed is marked "This plugin failed to load properly and is paused during recovery mode," with the error underneath.
5. Deactivate the item: Click Deactivate under the paused plugin, or switch to a default theme.
6. Exit Recovery Mode: Once the site loads correctly on the frontend, click Exit Recovery Mode in the top admin toolbar to return your dashboard to normal.

What to Do When the Recovery Email Never Arrives

It is surprisingly common for the recovery email to fail to deliver. Many hosts block or spam-filter mail that WordPress sends on its own, and if the plugin that crashed is the one that sends your site’s email (an SMTP plugin, for example), the message may never leave the server. Check your spam folder, and remember it goes to the administration email address set under Settings → General, which may be an old address.

There is no address you can type to switch Recovery Mode on yourself. It only starts from the link in that email, which carries a one-time security key. You may see guides suggest visiting wp-login.php?action=entered_recovery_mode, but that address only shows the "Recovery Mode Initialized" message a real link leads to; logging in from it takes you straight back to the same error.

Without the email, you still have three ways in:

1. Switch the plugin off by hand. Rename its folder in wp-content/plugins using your host’s File Manager or FTP, as shown in the fixes below. If you don’t know which plugin it is, rename the whole plugins folder to plugins-disabled, log in, rename it back, then turn your plugins on again one at a time until the error returns. If your host gives you SSH and WP-CLI, wp plugin deactivate plugin-name --skip-plugins does the same in one line.
2. Read the error log to see which plugin or theme crashed, as explained in the next section.
3. Wait for a new email. The link expires after one day, and WordPress sends a fresh one the next time the error happens after that.

How to Find the Faulty Plugin or Theme Using Error Logs

If Recovery Mode does not clearly identify the culprit, or if you are locked out entirely, you need to read the server error log. You can generate a detailed, site-specific log by editing your wp-config.php file.

Warning: Always back up your site and your wp-config.php file before editing core configuration files. A single typo here can break your site further.

1. Access your site files via FTP or your hosting control panel’s File Manager.
2. Open the wp-config.php file located in the root directory of your WordPress installation.
3. Find the line that says define( 'WP_DEBUG', false );.
4. Change it to the following code block:

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

The first line activates debugging. The second line prevents the raw errors from displaying to your public visitors. The third line “creates a file called debug.log in the wp-content folder” and saves all PHP errors inside it.

Refresh your website to trigger the error, then open the newly created debug.log file inside your wp-content directory. Look at the very bottom of the file for the most recent error. It will list the exact file path and line number causing the crash, pointing you directly to the faulty plugin or theme.

Step-by-Step Fixes for the Most Common Culprits

Once you know what is breaking your site, apply the correct fix based on the error log or Recovery Mode notice.

1. Deactivate a conflicting plugin
If the log points to a specific plugin, deactivate it via Recovery Mode. If you cannot access the dashboard, use FTP or File Manager to navigate to wp-content/plugins/. Rename the folder of the offending plugin (e.g., change bad-plugin to bad-plugin-disabled). This forces WordPress to deactivate it.

2. Switch to a default theme
If the error originates in your theme, activate a default WordPress theme like Twenty Twenty-Four via Recovery Mode. If locked out, navigate to wp-content/themes/ via FTP and rename your active theme’s folder. WordPress will automatically fall back to a default theme.

3. Increase the PHP memory limit
If your debug.log mentions "exhausted memory" or "allowed memory size," your site needs more RAM. Add this line to your wp-config.php file, just before the "That’s all, stop editing" line:

define( 'WP_MEMORY_LIMIT', '256M' );

4. Reinstall WordPress core files
If the error log points to files in wp-admin or wp-includes, missing or corrupted WordPress core files may be to blame. Download a fresh copy of WordPress from WordPress.org. Extract the zip file and use FTP to replace your core folders (like wp-admin and wp-includes), being careful not to overwrite your wp-content folder or wp-config.php file.

What This Error Means for Your Site Maintenance Strategy

The fact that nearly two-thirds of critical errors stem from plugin conflicts highlights a crucial reality for site owners: regular backups and staging environments are not optional extras, they are essential safeguards.

When you update a plugin, theme, or PHP version, doing it on a staging site first prevents your live site from going down. Furthermore, keeping a recent, automated backup ensures that if a critical error does occur and you cannot resolve it via Recovery Mode, you can restore your site to its last working state in minutes. This minimizes downtime, protects your search engine rankings, and prevents lost revenue.

Frequently Asked Questions

What does it mean when a website has a critical error?

It means a PHP script failed to execute properly, so WordPress stopped loading the page. It then emails the site administrator a link to Recovery Mode, a private way into the dashboard with the broken plugin or theme paused, so you can troubleshoot.

How can I fix the "There Has Been a Critical Error on This Website" error in WordPress?

Check your admin email for a Recovery Mode link, log in, and deactivate the faulty plugin or theme. If the email does not arrive, rename the faulty plugin’s folder in wp-content/plugins with your host’s File Manager or FTP, or enable WP_DEBUG in wp-config.php and read the error log to find it.

What does "critical error" mean?

In WordPress, a critical error is a fatal PHP error that stops the website from loading. It is usually caused by incompatible plugins, theme code errors, or exhausted server memory, rather than a permanent site failure or a security breach.

AboutShahid Anwer