FatalGuard

Basics

One-tap recovery

Catching a fatal is only half the job. FatalGuard also helps you fix it — from your phone, in one tap, even when wp-admin is unreachable.

How it works

When a plugin causes a fatal, the alert includes a secure recovery link (as a Telegram button):

⬤ Fatal on yourdomain.com
Uncaught Error: call to undefined function acme_init()
/wp-content/plugins/acme/acme.php:42

[ Turn it off & restore the site ]

Tap it and you land on a recovery page that:

  1. Names the plugin that crashed the site.
  2. Offers a Deactivate button for exactly that plugin.
  3. Confirms “Site restored” once it’s off.

No FTP client, no renaming folders over SSH, no editing wp-config.php. The site is back in seconds, and you can investigate the plugin at your own pace.

It’s secure

  • The link carries a signed, single-purpose token — it only ever deactivates the one plugin named in that alert.
  • Links expire; an old one shows an “expired” screen instead of acting.
  • A tampered or forged token does nothing at all.

Recovery is never rate-limited or capped — on the free plan you get unlimited one-tap recoveries. Fixing a downed site is not something we’ll ever put behind a usage meter.

When a theme, core, or mu-plugin crashes

Only plugins can be safely deactivated from a link, so recovery’s one-tap button appears for plugin fatals. When the culprit is a theme, WordPress core, or a must-use plugin, the alert says so plainly and points you to WordPress’s built-in Recovery Mode (the link in your site-admin email) instead of showing a button that can’t help.

Requirements

Recovery links work on public sites reachable from the internet. On a localhost or private-network install the button target isn’t reachable from your phone — that’s a limitation of the network, not the plugin.