Recover From a WordPress Fatal Error Without FTP
A secret recovery URL that opens before most other plugins and the theme gets you back into a white-screened WordPress site without FTP or a host ticket.
It happens in a second. You update a plugin, refresh the page, and get a white screen—or “There has been a critical error on this website.” Your site is down, the dashboard is unreachable, and the one thing that would fix it—deactivating that plugin—lives inside the admin that just stopped loading. If you don’t have FTP credentials handy (and on managed hosting, who does?), you’re stuck calling support. Unless you set up an airbag beforehand.
The essentials
- A fatal PHP error stops WordPress entirely—the admin can’t load, so you can’t fix it the normal way.
- The module gives you a secret recovery URL that opens as soon as the plugin’s own file loads—before the theme, WordPress’s init step and most other plugins. WordPress loads plugins in alphabetical folder order, so a plugin whose folder sorts before
blaminhor-essentialsand crashes at load still takes the page down; so do a database outage or a must-use plugin failure. - It names the plugin the error file belongs to (in its settings screen and alert email) and deactivates plugins via the database—the files stay intact.
- It can email you the recovery link: at once when PHP can’t run at all, and about 30 seconds after a plugin error, through a scheduled task that first checks your homepage—with de-duplication so it never floods your inbox. That task rides on WP-Cron, so if the site crashes on every request the email may never leave; the URL doesn’t depend on it.
- Unlike WordPress’s own recovery mode, it doesn’t depend on email—the recovery URL works without it, email is just a bonus.
What actually happens during a fatal error?
A PHP fatal error means something in your site’s code is broken badly enough that PHP, the language WordPress runs on, stops executing entirely. WordPress can’t boot, so neither can the admin—and that’s the trap: the interface you’d use to deactivate the broken plugin is itself crashing, on every page, for you and your visitors alike.
The old-school fix is FTP: connect, navigate to wp-content/plugins/, and rename the offending plugin’s folder to force it off. It works, but it assumes you have FTP credentials to hand and know your way around them—which, on managed hosting especially, many owners don’t.
WordPress has had its own recovery mode since version 5.2, but it hinges on receiving an email with a recovery link. And email is exactly what you can’t count on in a crisis—particularly if the plugin that just crashed is your SMTP plugin. You need a way in that doesn’t depend on anything else working.
Here’s how the three ways back into a crashed site compare:
| Recovery mechanism | Depends on | Limitation |
|---|---|---|
| FTP folder rename | FTP credentials and file access | Assumes you have the credentials and know your way around them—rare on managed hosting |
| WordPress recovery mode (5.2+) | Receiving a recovery email | Email delivery isn’t guaranteed—useless if the crashed plugin is your mailer |
| Fatal Error Recovery secret URL | A URL you saved in advance | You must store the URL beforehand, and anyone who has it can switch your plugins on or off and change your theme |
How do you set up fatal error recovery?
Activate the Fatal Error Recovery module in Blaminhor Essentials before you need it, like an airbag. On activation it generates a secret recovery URL you save somewhere safe; it then sits silent until a crash, when that URL opens a recovery page that runs before most other plugins and the theme, and lets you deactivate the guilty plugin. Three steps:
Set up the safety net before the crash: the secret URL only helps if you saved it beforehand.
1. Activate and save the recovery URL. The module generates a secret recovery URL unique to your site. Copy it and store it somewhere you’ll find in an emergency—a password manager, a pinned note, an email to yourself. That URL is your emergency access.
2. Let it sit. It runs silently, registering a lightweight PHP shutdown handler. No performance cost, no admin notices—it just watches.
3. When a crash happens, open your recovery URL. You get a recovery page that opens before most other plugins and the theme load, listing your installed plugins. “Most”, because WordPress loads active plugins in alphabetical order of their folder names: a plugin whose folder sorts before blaminhor-essentials (say advanced-something) and crashes the moment it loads stops the request before the recovery page can run—for that case you’re back to FTP. The module identifies the plugin from the file the error happened in, and names it in its settings screen and in the alert email. Click to deactivate that one—the deactivation happens in the database, so the plugin’s files stay untouched—and your site is back. Now you can investigate, roll back the update, or contact the plugin’s author at your leisure.
Can you rely on the recovery email alone?
No. The email notification (on by default) sends you the recovery link at once when PHP can’t run at all, and about 30 seconds after a plugin error, once a check of your homepage confirms the site is down. That delayed email rides on WP-Cron, WordPress’s task scheduler, which only runs when a request gets far enough—so the saved URL is your way in, the email a bonus.
The immediate email covers a syntax error, exhausted memory, or an error outside a plugin. For an error inside a plugin, the module schedules a check 30 seconds later and emails only if your homepage really is down—so a caught error that leaves visitors unaffected sends nothing. The catch: WP-Cron fires during a normal page load, so if the crash hits every request, that check may never run and the email may never leave (if your host disabled WP-Cron, the module sends at once instead). It’s useful when it arrives: you often learn the site crashed from the email itself.
But here’s the crucial distinction from WordPress’s native recovery mode: the email is a convenience, not a dependency. Your recovery URL works whether or not that email ever arrives. So even if the crashing plugin is your mailer, you still have a way back in.
How does this make hiding your login safe?
Fatal Error Recovery is the natural companion to Hide Login Page: moving your login to a secret URL is good security until you forget the slug and lock yourself out. The recovery page can switch Blaminhor Essentials off, which brings wp-login.php back—the escape hatch that makes hiding your login safe. Hide Login even reminds you to enable it first.
Why set up recovery before anything breaks?
This module doesn’t stop errors from happening; it removes the panic when they do. No hosting call, no FTP client, no renaming folders by hand—just a URL you saved once and a couple of clicks. Pair it with regular backups and you’ve covered both halves of “something went wrong”: roll back the whole site, or just disable the one plugin that broke it.
Fatal Error Recovery is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.
– blaminhor
FAQ
What causes WordPress fatal errors in the first place?
Almost always a code conflict: a plugin or theme update that clashes with your PHP version, another plugin or WordPress core; a bad edit to functions.php; or PHP memory that runs out. The common thread is code that stops PHP dead—which is why the fix is deactivating the offending plugin, never touching your content.
How do I fix the WordPress white screen of death?
The white screen is usually a fatal PHP error hiding its message. If the admin still loads, deactivate plugins one by one until it returns. If it doesn't, that's the trap the Fatal Error Recovery module solves: open your secret recovery URL and switch off the plugin you just updated (the alert email, when it is sent, names the plugin the error file belongs to) from the database.
How do I find which plugin caused the crash?
The module's settings screen and its alert email name the plugin the error came from, based on the file where it happened; the recovery page lists all your plugins so you can switch that one off. Without a tool, you'd deactivate plugins one at a time until the site comes back, which means either dashboard access you may not have, or renaming folders over FTP.
Doesn't WordPress already have a recovery mode?
Yes, since version 5.2—but it depends on receiving an email with a recovery link, and email delivery isn't guaranteed, especially if the crashing plugin is your SMTP plugin. This module's recovery URL works without any email at all; the email alert is a bonus on top, not the only way in.
Does the recovery module slow down my site?
No. It registers a lightweight PHP shutdown handler that only does anything when a fatal error actually occurs. There's no admin nagging, no front-end overhead—it sits silent until the day something crashes, then it's the difference between a two-minute fix and hours of downtime.
What if I never saved the recovery URL—can I still get in?
That's the one weak spot: the recovery URL only helps if you stored it beforehand. Without it, you're back to the old routes—FTP to rename the plugin folder, or your host's support desk. That's exactly why the module urges you to save the URL the moment you activate it, before you ever need it.
Comments