If you’ve ever seen the dreaded message:

“There has been a critical error on your website.”

—don’t panic. This is a common issue in WordPress and can often be fixed in just a few steps.

In this guide, we’ll walk you through what causes this error, and how to troubleshoot and fix it quickly, even if you’re not a developer.

❓ What Causes This Error?

This message usually appears when WordPress encounters a fatal PHP error. The most common causes include:

  • A broken or incompatible plugin
  • A theme conflict or missing file
  • Using a PHP version that’s too old or too new for your theme/plugins
  • Corrupted core WordPress files
  • Low PHP memory limit

When the error happens, WordPress can’t load your site normally—so it shows this generic message instead.

🔧 Step-by-Step Troubleshooting Guide

1. Enable Debug Mode to See the Real Error

First, enable debug mode to get more details.

  • Check the wp-content/debug.log file — it will tell you which file or plugin caused the error.
  • Connect to your website using FTP or File Manager in your hosting panel.
  • Open the wp-config.php file.
  • Find this line:
define( 'WP_DEBUG', false );
  • Change it to:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
  • Save the file and reload your website.

2. Deactivate All Plugins

If the error started after installing or updating a plugin, it may be the culprit.

To deactivate plugins manually:

  • Go to wp-content/ via FTP/File Manager.
  • Rename the folder plugins to something like plugins_old.
  • This will disable all plugins.
  • Refresh your site — if it works, a plugin is the cause.

Then, restore the folder name and activate plugins one by one from the dashboard to find the problem plugin.

3. Switch to a Default Theme

If the error is related to your theme:

  • Go to wp-content/themes/
  • Rename your active theme folder (e.g., astra to astra_old)
  • WordPress will automatically switch to a default theme like twentytwentyfour
  • Reload your site and see if the issue is resolved

4. Check PHP Version Compatibility

Some plugins and themes require a certain PHP version. If your server is using an outdated or unsupported version, it could trigger a fatal error.

  • Log into your hosting control panel (e.g., cPanel or Plesk)
  • Check your current PHP version (should be PHP 7.4 or higher)
  • Upgrade if necessary, or downgrade if a plugin/theme isn’t compatible with the latest version.

5. Restore from Backup (If Available)

If nothing works and you recently made changes, restoring from a previous backup may be the fastest fix. Most managed WordPress hosts offer daily backups that can be restored in one click.


✅ Final Tip: Use the Recovery Mode Link (If Available)

When WordPress detects a fatal error, it often sends an email with a special recovery mode link. If you received this email:

  • Click the link to log into your site in safe mode
  • You can deactivate the problem plugin or theme directly from there

Make sure your admin email is correct in your WordPress settings to receive such notices in the future.

🧩 Bonus Tools to Help Troubleshoot

Here are a few plugins and tools you can install (after the site is back up) to make troubleshooting easier in the future:

  • Health Check & Troubleshooting – run tests and switch to troubleshooting mode safely
  • WP Debugging – easily enable debug mode from your dashboard
  • Query Monitor – see PHP errors and slow queries
  • Wordfence – check for file changes and malware

If you’re still stuck after trying all of this, feel free to contact your web host’s support — they often have access to logs and server-level tools that can help you pinpoint the issue faster.

Want help one-on-one? Drop a message through our Contact Page — we’re happy to help!

Leave a Reply

Your email address will not be published. Required fields are marked *