Modern WordPress replaced the old white screen with a slightly friendlier message: “There has been a critical error on this website.” It’s still vague, but WordPress usually emails the details to your admin address, and there are reliable ways to uncover the rest.
Check your admin email
When this error fires, WordPress sends an email to the site admin containing the specific error, often naming the exact plugin and file. Check that inbox first — the email frequently includes a special recovery-mode link that lets you log in and deactivate the broken component with one click.
Enable debug logging
If there’s no email (perhaps because the site can’t send mail), reveal the error yourself. Edit wp-config.php:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);Reload the page, then read wp-content/debug.log. The last few lines name the culprit — a specific plugin, theme file or PHP function.
Deactivate the offending plugin
If the log points to a plugin, disable it via File Manager: rename its folder inside wp-content/plugins. If the error clears, you’ve found it. Look for an update, an alternative, or contact the plugin’s developer.
Switch the theme if needed
If the error traces to a theme file, rename your active theme’s folder so WordPress falls back to a default theme. A working site confirms the theme was the problem.
Raise memory and PHP limits
Critical errors sometimes just mean the site hit a resource wall. Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php and, in cPanel’s INI Editor, raise max_execution_time. If that resolves it, dig into why the site is so hungry.
Check PHP compatibility
Critical errors often appear right after a PHP version change, when a plugin isn’t compatible. In MultiPHP Manager, try the previous version. If the site returns, update that plugin before upgrading PHP again.
Turn debug display off on live sites once you’ve fixed things. If the log shows a server-level fault rather than a plugin, send us the exact line and we’ll handle it.
