A plugin, a theme or WordPress itself hit a PHP fatal error, and WordPress replaced the page with this message. The error is almost always in a plugin or theme, often right after an update. WordPress emails the site’s admin a recovery link that opens the admin with the culprit paused; the debug log names it.
There has been a critical error on this website.
How 5 other clients word the same error
In the admin
There has been a critical error on this website. Please check your site admin email inbox for instructions.
In recovery mode
There has been a critical error on this website, putting it in recovery mode. Please check the Themes and Plugins screens for more details.
WordPress 5.3–5.5
There has been a critical error on your website.
WordPress 5.2
The site is experiencing technical difficulties.
The email to the admin
[Example Site] Your Site is Experiencing a Technical Issue
| Error | There has been a critical error on this website. |
| Usually fixed by | The site owner or host |
| Status | 500 |
| Since | WordPress 5.2 (2019), which added the fatal error handler |
| Recovery link | Emailed to the admin address, valid for a day, at most one email a day |
Check the site from outside
Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.
What it means
When PHP stops on a fatal error, WordPress catches it and shows this page instead of a blank screen. If the error came from a plugin or a theme while someone was in the admin or signing in, it also emails the admin address a recovery link: signing in through it pauses the plugin or theme for that session, so you can deactivate or fix it.
The email only comes when the error happens in the admin or at sign-in, and on single sites — an error seen only by visitors sends none.
Why it happens
- A plugin or theme updated to a version that clashes with another, or with the PHP version.
- The PHP version changed (by you or the host) and older code no longer runs.
- Memory: “Allowed memory size … exhausted”.
- A half-finished update or edited file with a syntax error.
What the error log says
wp-content/debug.log, a plugin calling code that is not there
PHP Fatal error: Uncaught Error: Call to undefined function example_function() in /home/user/public_html/wp-content/plugins/example-plugin/example-plugin.php:42
How to fix it
- Look for the “Your Site is Experiencing a Technical Issue” email at the admin address, and sign in through its link: the failing plugin or theme is paused, and the admin says which.
- No email? Turn on the log: add define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_LOG’, true ); define( ‘WP_DEBUG_DISPLAY’, false ); to wp-config.php, load the page, and read wp-content/debug.log.
- Deactivate the plugin it names — by renaming its folder in wp-content/plugins if you cannot reach the admin — or switch to a default theme.
- Update, replace or roll back that plugin, then turn debugging off again.
If you are visiting the site
- Nothing on your side causes it; the site owner has to fix it.
See it for yourself
tail -n 20 wp-content/debug.log
wp plugin list --status=active
The fatal error’s line names the file, and the file’s path names the plugin or theme. The second command (WP-CLI) lists what is active.
Questions
I never got the recovery email. Why?
WordPress sends it only for errors in the admin or at sign-in, only on single sites, at most once a day, and to the admin email address — which may be an old one. Mail from the site may also be failing. The debug log gives the same answer.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- wordpress-develop/src/wp-includes/class-wp-fatal-error-handler.php at trunk — github.com
- wordpress-develop/src/wp-includes/class-wp-recovery-mode-email-service.php at trunk — github.com
- wordpress-develop/src/wp-includes/load.php at trunk — github.com
- Debugging in WordPress — developer.wordpress.org