Opening your website only to see a completely blank white screen—or WordPress’s dreaded message, “There has been a critical error on this website. Please check your site admin email inbox for instructions”—is every site owner’s worst nightmare. Worse, if your host blocks outbound PHP mail, that recovery email never arrives!
Don’t worry: your posts and database are safe. Follow this 3-step recovery procedure to pinpoint the exact cause and bring your site back online in under 5 minutes.
Outgrowing Free Hosting Limits? Claim Our Partner Discounts
Upgrade to fast Hostinger LiteSpeed WordPress Hosting (with an extra 20% referral discount + free domain) or grab low-cost Namecheap cPanel Hosting & Domains with free WHOIS privacy:
Step 1: Turn On Safe Background Debug Logging (`WP_DEBUG_LOG`)
Instead of guessing which plugin or theme crashed, let WordPress write the exact PHP fatal error to a private log file:
- Open our Free WordPress wp-config.php & Debug Snippet Generator and select “Enabled to wp-content/debug.log (Hidden on Screen)”.
- Paste those 3 lines (`WP_DEBUG`, `WP_DEBUG_LOG`, `WP_DEBUG_DISPLAY = false`) into your `wp-config.php` file via cPanel File Manager.
- Refresh your broken website once, then open
/wp-content/debug.login File Manager. Look at the bottom line starting withPHP Fatal error:—it will name the exact `/wp-content/plugins/plugin-name/` folder responsible!
Step 2: Rename the Faulty Plugin Folder in cPanel
Once `debug.log` reveals the offending plugin (or if you want to test all plugins at once):
- Navigate to
public_html/wp-content/plugins/in cPanel File Manager. - Rename the broken plugin’s folder (for example, `heavy-plugin` → `heavy-plugin-off`).
- WordPress will automatically deactivate that single plugin and your site will load immediately!
Step 3: Check PHP Memory & Version Compatibility
If the fatal error says Allowed memory size exhausted, follow our WordPress Memory Limit Fix Guide. If it says Uncaught TypeError or Call to undefined function after a hosting update, open cPanel → MultiPHP Manager and switch from PHP 8.3 back to PHP 8.1 or 8.2 until the plugin developer releases a patch.
Frequently Asked Questions (FAQ)
What causes ‘There has been a critical error on this website’ in WordPress?
This message (which replaced the blank White Screen of Death in modern WordPress) occurs when a PHP fatal error stops page execution—almost always due to a plugin conflict, an incompatible PHP 8.x theme function, or exhausted PHP memory.
How do I find out which plugin caused the critical error if I can’t access /wp-admin/?
Enable WP_DEBUG and WP_DEBUG_LOG inside wp-config.php using cPanel File Manager, reload the broken page once, and open /wp-content/debug.log to see the exact file and line number that crashed.
How do I deactivate all WordPress plugins via cPanel File Manager or FTP?
Navigate to /wp-content/ and rename the ‘plugins’ folder to ‘plugins_old’. This immediately deactivates every plugin so you can log back into /wp-admin/, then rename the folder back to ‘plugins’.