"There Has Been a Critical Error on This Website": How to Fix It

You open your website and instead of your homepage you see one line: "There has been a critical error on this website." It is alarming, but it is also one of the most common and most fixable WordPress problems. In our experience, the vast majority of cases are caused by a plugin, theme or PHP compatibility issue.

Step 1: Check your email

WordPress usually sends the site administrator an email with the subject "Your Site is Experiencing a Technical Issue." It often names the plugin or theme that caused the error and includes a special recovery mode link. Use it to log in and deactivate the culprit.

Step 2: Think about what changed

Errors rarely appear from nowhere. Did you or your host recently update a plugin, the theme, WordPress core or the PHP version? Did someone add custom code? The most recent change is the most likely cause.

Step 3: Enable debugging

If there is no email, enable debug logging by adding these lines to your wp-config.php file:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Reload the page, then check wp-content/debug.log. The error message will point to the exact file and line causing the problem.

Step 4: Deactivate the problem plugin or theme

If you cannot access the dashboard, connect via your hosting file manager or FTP and rename the plugin folder in wp-content/plugins. WordPress will deactivate it automatically. If the theme is at fault, rename the theme folder and WordPress will fall back to a default theme.

Step 5: Check PHP version compatibility

Hosts upgrade PHP versions regularly. Older plugins and themes may not be compatible. Your hosting control panel usually lets you switch PHP versions temporarily while the incompatible code is updated or replaced.

Getting the site back online is step one. Finding out why it broke is what stops it happening again.

Other possible causes

• PHP memory limit exhausted
• Corrupted core files after a failed update
• Database errors or corrupted tables
• Conflicts between two plugins doing similar things
• Malware that has modified core or plugin files

How to prevent it next time

1. Take a full backup before every update
2. Test major updates on a staging site first
3. Update regularly instead of all at once every few months
4. Remove plugins you no longer use
5. Choose well maintained plugins with recent updates
6. Monitor uptime so you know immediately when something breaks

If you would rather not touch server files, that is exactly what our emergency support and care plans are for. We fix critical errors daily, usually within hours.