How to Fix WordPress Critical Error on Your Website

June 23, 2026 by RankNewly SEO EXPERT
How to Fix WordPress Critical Error on Your Website

The “There has been a critical error on your website” message is one of the most dreaded sights for any WordPress site owner. This error can appear suddenly, locking you out of your admin dashboard and leaving visitors with a broken site. The good news is that this error is almost always fixable, and there is a structured way to approach the problem.

Essentially, this critical error is a fatal PHP error. When WordPress cannot execute a piece of code due to a conflict, a syntax error, or a resource issue, it fails to load the page and displays this generic message to protect sensitive information. WordPress 5.2 introduced a safety net: it will often send an email to the site admin with a special “Recovery Mode” link. This guide will walk you through a step-by-step process to fix this error, from the simplest fixes to more advanced solutions.

Table of Contents

  • Understanding the Critical Error and Its Causes

  • Pre-Flight Checklist: Initial Steps to Take

  • Step 1: Check Your Admin Email for the Recovery Mode Link

  • Step 2: Clear Your Caches

  • Step 3: Enable WordPress Debug Mode to Find the Culprit

  • Step 4: Deactivate All Plugins via FTP or File Manager

  • Step 5: Switch to a Default WordPress Theme

  • Step 6: Increase the PHP Memory Limit

  • Step 7: Reinstall WordPress Core Files

  • Step 8: Check Your PHP Version

  • Step 9: Restore Your Website from a Backup

  • Frequently Asked Questions (FAQ)

Understanding the Critical Error and Its Causes

A critical error means a PHP script on your website has stopped working and was unable to complete its process. This is a fatal error, and it can be triggered by several issues.

The most common causes are:

  • Plugin or Theme Conflicts: This is the number one culprit. A conflict can occur when a plugin or theme has a syntax error, is incompatible with your current version of WordPress or PHP, or when two plugins conflict with each other. Failed updates can also leave plugins or themes with corrupt or missing files

  • Corrupted WordPress Core Files: An incomplete WordPress update, a failed migration, or a manual file change can corrupt or delete essential WordPress files.

  • PHP Memory Limit Exhaustion: If your site runs out of allocated PHP memory, often due to a resource-intensive plugin or theme, it can cause a fatal error.

  • Outdated or Incompatible PHP Version: Your site might be running a version of PHP that is no longer supported by the plugins or themes you use. WordPress recommends PHP 7.4 or greater.

  • Malware Infections: Malicious code injected into your site files can break PHP execution and cause errors.

Pre-Flight Checklist: Initial Steps to Take

Before diving into complex file edits, perform these quick checks.

  • Reload the Page: Sometimes, a temporary server glitch can cause the error. Simply refreshing the page might resolve it.

  • Clear Your Browser Cache: You might be seeing a cached version of the error page. Open your site in an incognito or private browsing window to bypass your browser’s cache.

  • Check Your Admin Email: Look for an email from WordPress with the subject line “Your Site is Experiencing a Technical Issue.” This is the most important initial step, as it often provides a direct solution.

Step 1: Check Your Admin Email for the Recovery Mode Link

When a critical error occurs, WordPress often sends a notification to the site administrator’s email address. This email is crucial because it contains a time-limited link to enter Recovery Mode.

Recovery Mode is a safety feature introduced in WordPress 5.2. It allows you to log into your admin dashboard safely, even when a fatal error would normally prevent you from doing so. In Recovery Mode, the problematic plugin or theme is paused just for your session, allowing you to investigate and deactivate it.

  1. Check the inbox of the email address associated with your WordPress admin account.

  2. Find the email from WordPress detailing the error.

  3. Click the link provided to enter Recovery Mode.

  4. Once logged in, you should see a notice indicating which plugin or theme caused the error. You can then deactivate it, and your site should be restored.

If you didn’t receive the email, check your spam folder. If it’s not there, don’t worry—you can proceed with the other manual methods.

Step 2: Clear Your Caches

Caching, while great for performance, can sometimes serve as a stored version of the error page even after you have fixed the underlying issue. This can make it seem like the error is still present. To ensure you are seeing the latest version of your site, clear:

  • Browser Cache: Clear your browser’s cache or test in an incognito/private window.

  • Plugin/Server Cache: If you use a caching plugin like LiteSpeed Cache, W3 Total Cache, or WP Rocket, clear its cache via your hosting control panel or the plugin’s settings (if accessible). Some hosts provide a “Flush Cache” button in their control panel.

  • CDN Cache: If you use a Content Delivery Network (CDN) like Cloudflare, purge its cache as well.

Step 3: Enable WordPress Debug Mode to Find the Culprit

If the recovery mode link didn’t work or you want to be more precise, the next step is to enable WordPress debugging. This mode will log specific PHP errors to a file, pinpointing the exact plugin, theme, or file causing the issue

  1. Connect to your website’s server using an FTP client (like FileZilla) or your hosting provider’s File Manager.

  2. Navigate to the root directory of your WordPress installation (the folder containing. wp-config.php, wp-admin, and wp-content).

  3. Locate the wp-config.php file and open it for editing.

  4. Find the line that says define( 'WP_DEBUG', false );. If it’s not there, add the following code just before the line that says /* That's all, stop editing! Happy publishing. */ :

    php
    define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

    • WP_DEBUG: Triggers the debug mode.

    • WP_DEBUG_LOG: Saves error messages to a debug.log file in the /wp-content/ directory.

    • WP_DEBUG_DISPLAY: Prevents errors from being displayed on the live site, which is important for security.

  5. Save the file.

  6. Reload your website to trigger the error again.

  7. Navigate to /wp-content/debug.log to view the error log.

  8. Open the file. The latest entries will show you the specific file and line number causing the fatal error. The log will likely mention a specific plugin or theme folder.

Important: Once you have resolved the issue, set WP_DEBUG back to false To turn off logging.

Step 4: Deactivate All Plugins via FTP or File Manager

If you can’t access the WordPress admin, you can deactivate all plugins by renaming the plugin folder. This is a highly effective method to determine if a plugin is the source of the critical error.

  1. Access your site’s files via FTP or File Manager.

  2. Navigate to /wp-content/.

  3. Find the plugins  Rename it to something like plugins-disabled  plugins_old .

  4. Try reloading your website.

If the error disappears, you have confirmed that a plugin conflict is the cause.

  • To find the specific plugin, rename the folder back to plugins.

  • Then, inside the plugins folder, rename individual plugin folders one by one (e.g., rename akismet to akismet-stop) and reload the site after each rename. When the error disappears, you have found the faulty plugin. You can then keep it deactivated or seek an update.

Step 5: Switch to a Default WordPress Theme

If disabling plugins doesn’t fix the issue, the error might be in your active theme. You can force WordPress to switch to a default theme by renaming your current theme’s folder.

  1. Access your site’s files via FTP or File Manager.

  2. Navigate to /wp-content/themes/.

  3. Find the folder of your active theme. Rename it to something like yourtheme-disabled .

  4. Reload your website.

If the error is fixed, WordPress will automatically fall back to a default theme (like Twenty Twenty-Four or Twenty Twenty-Five) if one is installed. If no default theme exists, you may need to upload one manually. Once you’ve confirmed the theme is the issue, you can either delete it, update it, or contact the theme developer for support.

Step 6: Increase the PHP Memory Limit

WordPress sets a default PHP memory limit, often 128 MB. A complex site with many plugins might exceed this limit, leading to a critical error.

You can increase the memory limit by editing the wp-config.php file.

  1. Access your wp-config.php File via FTP or File Manager.

  2. Add the following line of code just before the /* That's all, stop editing! Happy publishing. */ line :

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

    You can try 256M or even 512M if your hosting plan allows it .

  3. Save the file and reload your site to see if the error is resolved.

Some hosting providers also allow you to increase PHP limits directly from their control panel (e.g., hPanel’s PHP Configuration or cPanel’s MultiPHP INI Editor). If increasing the memory limit doesn’t solve the problem, it might be a sign you need to upgrade your hosting plan.

Step 7: Reinstall WordPress Core Files

If the error points to a core WordPress file (in wp-admin  wp-includes), or if all else fails, reinstalling the core files can resolve file corruption issues

Important: Do not delete the wp-config.php file or the entire wp-content folder, as this contains your themes, plugins, and media uploads.

  1. Download a fresh copy of the latest WordPress version from wordpress.org.

  2. Unzip the downloaded file on your computer.

  3. Access your site’s files via FTP or File Manager.

  4. Delete the wp-admin and wp-includes folders from your server.

  5. Upload the new wp-admin  wp-includes Folders from the fresh WordPress copy to your server.

  6. Upload all the individual files from the root of the fresh WordPress folder to your site’s root directory, but do not overwrite your wp-config.php or .htaccess files.

This process essentially refreshes all of WordPress’s core functionality without affecting your themes, plugins, or content. After completing the upload, reload your site. This solution is also effective if the error occurred right after a WordPress update.

Step 8: Check Your PHP Version

Running an outdated PHP version is a common cause of compatibility issues. WordPress recommends at least PHP 7.4.

  1. Log into your hosting account and find the section for PHP settings (often under “PHP Configuration,” “PHP Version,” or “Software”).

  2. Check your current PHP version.

  3. If it’s an older version (PHP 7.3 or lower), change it to PHP 7.4 or PHP 8.0 or higher.

  4. Save the changes and reload your site.

Sometimes, updating PHP can introduce new errors if your plugins or themes aren’t compatible. If that happens, you can revert to the old PHP version while you update your plugins and themes.

Step 9: Restore Your Website from a Backup

If none of the troubleshooting steps work, the final solution is to restore your website from a backup made before the critical error occurred. This is why regular backups are crucial.

  • Restore via your hosting provider: Many web hosts, including Namecheap, Bluehost, and Hostinger, offer one-click backup restoration through their control panel. This is often the easiest and fastest way.

  • Restore via a backup plugin: If you use a plugin like UpdraftPlus, Solid Backups, or Jetpack, you can use its restore function. You may need to use the Recovery Mode link to access your admin dashboard to run the restore.

Frequently Asked Questions (FAQ)

1. What does the “There has been a critical error on your website” message mean?

This is a generic message WordPress shows when a fatal PHP error occurs, preventing your site from loading properly. It’s a safety measure to avoid revealing sensitive code details to visitors.

2. Will I always get an email from WordPress about the critical error?

WordPress attempts to send a recovery mode email to the site administrator’s address. However, it might not arrive if the error occurred before the email function could load, or if it gets filtered to spam.

3. What is WordPress Recovery Mode and how do I access it?

Recovery Mode is a safe state that allows you to log into your admin dashboard when a fatal error would otherwise block you. You can access it by clicking the special link sent to your admin email. If you don’t have the link, you can also try to access it manually by adding ?action=entered_recovery_mode to your wp-login.php URL.

4. How can I identify which plugin or theme is causing the error?

The fastest way is to enable WordPress debugging (WP_DEBUG_LOG) and check the debug.log file in the /wp-content/ folder. It will list the file and line number of the error, often pointing to a specific plugin or theme folder. You can also find the culprit by deactivating all plugins or switching to a default theme via FTP/File Manager

5. Is it safe to edit my WordPress files via FTP or File Manager?

Yes, it is standard practice for troubleshooting, but you must be careful. Always create a full backup of your site before making any changes. A single mistake in a file can break your site. Only edit files you are sure of, and follow instructions carefully.

6. Will increasing my PHP memory limit fix the critical error?

It can, if the error is caused by your site running out of allocated memory. This is a common problem for complex sites. If the memory limit is already high (e.g., 512M) and the error persists, the issue is likely elsewhere.