"There has been a critical error on this website" is the message WordPress shows when PHP hits a fatal error while loading your site. Visitors see only that one line, but WordPress knows exactly which plugin or theme failed, and it usually tells you by email. This guide explains what the WordPress critical error means, how to use the recovery mode email safely, how to turn on WP_DEBUG to see the real error, and how to fix it.
What the critical error looks like
- On your website: There has been a critical error on this website. followed by a "Learn more about troubleshooting WordPress" link.
- In the WordPress dashboard: There has been a critical error on this website. Please check your site admin email inbox for instructions.
- On older WordPress versions, or if the error handler is switched off: a blank white page or a 500 Internal Server Error.
The most common causes on Instant Access Internet Services hosting are a plugin or theme update that went wrong, a plugin that doesn't support your PHP version, a PHP script running out of memory, or a mistake in a file you edited.
Step 1: Check for the "Technical Issue" email
When the error happens, WordPress sends an email to the site's administration email address (set under Settings > General). The subject is [Your Site Name] Your Site is Experiencing a Technical Issue. It names the plugin or theme that caused the error, shows the error details, and contains a recovery mode link.
You don't need the link to use the email. The most useful part is the plugin or theme name and the error details. Write those down and go to Step 2.
Is it safe to use the recovery mode link?
Our advice is never to click links in emails about your accounts, and that includes this one unless every one of these is true:
- The email came from your own site's address (normally
wordpress@example.com, where example.com is your domain), not a look-alike or a free email address. - It arrived just after you saw the critical error yourself, and your site really is showing the error right now.
- The link goes to your own domain, to
wp-login.phpwithaction=enter_recovery_modein the address.
If anything doesn't match, or you're not sure, don't use it. Delete the email and use one of the methods below instead -- they fix the same problem without trusting a link. The recovery link expires after about a day anyway; WordPress sends a new one if the error happens again after that.
If you do enter recovery mode, WordPress pauses the broken plugin or theme for you only. Visitors still see the error until you go to Plugins (or Appearance > Themes), deactivate or replace the problem item, and click Exit Recovery Mode.
Step 2: Disable the plugin or theme that failed
Try these in order.
- Log in yourself. Type
https://example.com/wp-login.phpinto your browser (use your own domain). If the error only affects the front of the site, the dashboard often still works: go to Plugins and deactivate the plugin named in the email. - Use WP Toolkit. In cPanel, go to Domains > WordPress Management (WP Toolkit), open your site, and on its plugins tab switch the problem plugin off.
- Rename the folder in File Manager. This always works, even when nothing else loads. In cPanel, go to Files > File Manager, open
public_html/wp-content/plugins, and rename the plugin's folder (for examplesome-plugintosome-plugin.off). WordPress deactivates it automatically. For a theme, do the same inwp-content/themes; WordPress falls back to a default theme if one is installed.
Reload your site. If it works, update or replace that plugin or theme before switching it back on. If you don't know which plugin is at fault, follow the "disable all plugins" steps in How to Fix the WordPress White Screen and 500 Errors.
Step 3: No email? Find the error with WP_DEBUG
If the email never arrived (check your spam folder first), find the error yourself.
- Look in the PHP error log first: a file named
error_loginpublic_htmlorpublic_html/wp-admin, or Metrics > Errors in cPanel (see How to Check Your Website Error Log and Recent Visitors). Look for a line starting with PHP Fatal error. - If that doesn't show it, turn on WordPress debug logging. In File Manager, edit
wp-config.phpand add these lines just above/* That's all, stop editing! */. If aWP_DEBUGline already exists, change it rather than adding a second one.
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 );
Then:
- Reload the page that shows the error.
- Open
wp-content/debug.logand read the newest lines at the bottom. A path such aswp-content/plugins/some-plugin/...tells you which plugin to disable in Step 2.
WP_DEBUG_DISPLAY set to false keeps errors off the screen, so visitors never see file paths from your site. Don't set it to true on a live site.
Turn debugging off when you're done. Set WP_DEBUG back to false and delete debug.log. The log sits inside your website folder, so anyone who guesses the address could read it. If you need to leave logging on for a while, give it a private location instead, for example define( 'WP_DEBUG_LOG', '/home/username/wp-debug.log' ); using your cPanel username.
Common errors behind the critical error
| Error in the log or email | What to do |
|---|---|
Allowed memory size of ... bytes exhausted | Raise memory_limit in Software > MultiPHP INI Editor. See PHP Allowed Memory Size Exhausted: What It Means and How to Fix It. |
Maximum execution time of ... seconds exceeded | A task ran too long. See PHP Maximum Execution Time Exceeded: What It Means and How to Fix It. |
Call to undefined function, or errors right after a PHP version change | The plugin or theme doesn't support your PHP version. Update it, or switch back in Software > MultiPHP Manager (How to Change Your PHP Version in cPanel). |
PHP Parse error: syntax error | A typo in a file that was just edited. Undo the edit, or restore the file with JetBackup 5. |
Error in a file under wp-includes or wp-admin | WordPress core files may be damaged or an update was interrupted. Restore from a backup (How to Back Up and Restore WordPress in WP Toolkit) or open a ticket. |
Common questions
Why didn't I get the recovery mode email?
It goes to the administration email address in WordPress, which may be an old address. It can also land in spam, and WordPress sends it at most about once a day. The fix doesn't depend on it -- use Steps 2 and 3.
Should I use WP_DISABLE_FATAL_ERROR_HANDLER?
No. That constant switches off the critical error page and recovery mode, which means raw errors or a blank page instead. It's meant for developers testing on a staging site.
Can I just restore a backup?
Yes. If the site broke after an update and you want it back quickly, restore the last working copy from WP Toolkit or JetBackup 5 (How to Back Up and Restore WordPress in WP Toolkit). Then update plugins one at a time to find the one that breaks it.
When to open a ticket
Open a ticket if you can't find the error, the error is in WordPress core files, or disabling plugins and themes doesn't help. Include your site address, the exact error line from the email or debug.log, and what changed just before the problem started. Please don't forward the recovery mode email itself -- copy the error text instead.
Related guides
- How to Fix the WordPress White Screen and 500 Errors
- How to Check Your Website Error Log and Recent Visitors
- 500 Internal Server Error: What It Means and How to Fix It
- PHP Allowed Memory Size Exhausted: What It Means and How to Fix It
- Never Click Links in Emails About Your Account: Log In Directly Instead
Still stuck? Open a support ticket and the Instant Access Internet Services team will help.
