iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Start by recording the exact error and checking Tools > Site Health. Before changing anything, make sure you have a full backup and a way to restore it. Then isolate plugins and themes one at a time, choosing a method that fits whether you can access the dashboard and whether the site is live.
What to check before changing plugins
Record the symptom
Write down what fails, where it fails (the front end, wp-admin, or both), when it started, and what changed recently. Note plugin, theme, WordPress, or PHP updates, preserve the exact on-screen error, and record relevant timestamps. This gives you a baseline for checking whether a change actually fixed the problem.
Review Site Health
In the dashboard, open Tools > Site Health. The Status tab groups critical issues, recommended improvements, and passed checks. Review warnings about configuration problems, blocked HTTP requests, or debug output. The Info tab provides details about site configuration and installed components, and can export that information. Review an export before sharing it; it may contain details you do not want to disclose. See WordPress Site Health screen documentation.
Back up and confirm a restore path
WordPress’s troubleshooting lesson recommends making a full backup before troubleshooting. Confirm you can restore it before deactivating plugins or editing files, especially on a live site. Make one controlled change at a time, note what you changed, and check whether the original symptom remains. See WordPress.org’s plugin troubleshooting lesson.
Choose a plugin-isolation method
Use the least disruptive option that fits your access and backup situation. A blank page or critical error does not by itself prove a plugin is responsible: possible causes also include PHP errors, memory exhaustion, database issues, and theme conflicts.
| Method | When it fits | Effect and requirements |
|---|---|---|
| Troubleshooting mode | You can log in and want to test plugins or a theme. | Health Check and Troubleshooting mode disables plugins and switches to a default theme for your administrator session; visitors continue to see the normal site. Re-enable components individually and test after each change. |
| Manual deactivation in wp-admin | The dashboard works and you can safely test changes. | Deactivating plugins can affect the live site. WordPress’s lesson describes deactivating plugins, then reactivating them one at a time. |
| Recovery Mode | A detected fatal PHP error has triggered Recovery Mode and you can use its email link. | The failing plugin or theme can be paused for your administrator session. This does not handle every failure type or execution context. |
| Rename a plugin folder | You cannot reach wp-admin, suspect a plugin, and have FTP or hosting file-manager access. | Renaming the suspected plugin’s folder can temporarily deactivate it. The change is reversible, but requires file access. |
These behaviors are described in WordPress.org’s troubleshooting lesson and the WordPress troubleshooting FAQ.
Test plugin and theme conflicts when wp-admin works
Use troubleshooting mode for session-only testing
- Install or open the Health Check and Troubleshooting plugin, then enable Troubleshooting mode.
- Check whether the affected page or action still fails while plugins are disabled and a default theme is active for your session.
- Enable one plugin, then repeat the action that produced the error. Continue one component at a time, keeping notes on each result.
- If the problem returns after enabling a plugin, record its name and the exact steps that reproduce the issue. Test the theme separately if needed by returning to a default theme in Troubleshooting mode.
- When you have identified the likely conflict, exit Troubleshooting mode and decide on a fix, such as updating, replacing, or asking the component’s support team for help.
Because this mode is session-specific, visitors continue to see the normal site while you test. It is useful when you want to investigate without changing the site-wide plugin and theme configuration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use manual deactivation only when its live-site impact is acceptable
If you cannot use Troubleshooting mode, or need to test through the normal site configuration, the WordPress.org lesson describes deactivating plugins in wp-admin and then reactivating them one at a time. Check the failing page or action after each activation. On a live site, deactivation may change what visitors can do or see, so plan the test accordingly and have a restore path.
Rank #3
Regain access after “There has been a critical error on this website”
Try Recovery Mode
Since WordPress 5.2, Recovery Mode can respond when WordPress detects a fatal PHP error during a regular page load. WordPress sends an administrator email with a special login link. After logging in through that link, the failing plugin or theme can be paused for your administrator session, and the dashboard may show notices identifying the component. Address the cause, exit Recovery Mode, and verify that the site works normally. Recovery Mode is not a guarantee for every error, including failures in other execution contexts. See WordPress’s troubleshooting and Recovery Mode documentation.
If the recovery email does not arrive
Check the spam folder and verify the administrator email address. If the link is unavailable and a plugin is suspected, WordPress documents a fallback: use FTP or your hosting provider’s file manager to rename that plugin’s folder. This temporarily deactivates the plugin and may restore dashboard access. Record the original folder name so you can reverse the change, and treat this as a recovery step rather than a permanent fix. If you cannot access the files or are unsure which folder to change, ask your host for help.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use debug logs without exposing site information
WordPress’s Advanced Administration Handbook says WP_DEBUG is assumed false by default and that debugging tools are generally intended for development copies. When debug mode is active, WP_DEBUG_LOG can send errors to wp-content/debug.log or to a configured path. A log can help identify runtime errors, but debugging may also produce notices and warnings unrelated to the fatal symptom.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePrefer a local or staging copy. Do not leave error messages visible on a public site or make a log publicly accessible: debug output can reveal sensitive information. Turn debugging off and protect or remove logs when finished. WordPress’s debugging documentation cautions against using these tools on live sites; Site Health also warns that debug information can be sensitive.
When to contact your host or plugin support
Escalate if Recovery Mode email is missing, wp-admin remains inaccessible, or the problem requires server-level access. WordPress recommends contacting a hosting provider when recovery access fails and points users toward support when Site Health problems cannot be resolved.
To make the request useful, provide the exact error, when it began, recent changes, and WordPress, PHP, and plugin versions where available. Include only a sanitized Site Health export or the relevant excerpt from a protected log; do not send a public link to a debug file. If a conflict appears tied to one plugin or theme, include the steps that reproduce it and what happened when you enabled or disabled that component.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
