WordPress Repair — Fix “There has been a critical error”

1 Free check — what’s wrong?

Enter your site address. We’ll look at what’s publicly visible. No password required.

2 Connect to fix it

Your safety:

Credentials stay in memory only — never saved to disk, never logged, and wiped when you disconnect.
Every change is backed up on your own site and can be undone with one click.
We never download or copy your content. Read the full safety details →
Tip: create a temporary FTP account for this and delete it afterward.

3 Diagnose & repair

Connected

Optional: make a safety copy first

Before any invasive repair, we can duplicate your plugins, themes and mu-plugins into a wp-repair-backups/snapshot-… folder on your own site, so you always have an untouched copy to fall back on.

Honest note: FTP has no server-side “copy” command, so each file is read and written straight back to your site. It passes through our server only momentarily, in memory — nothing is ever stored here.

Turns on logging, disables plugins, then finds the exact culprit — all reversible.

Plugin health check

Once your site is back up, see which plugins are out of date, abandoned, or no longer in the WordPress directory — the ones most likely to crash it again.

Share a repair report

Create a clean, printable summary of what we found and fixed — handy for a client, a host, or your records.

Locked out of wp-admin? Create an emergency administrator

We'll stage a one-time helper on your site that creates (or promotes) an administrator account, then deletes itself the next time any page on your site loads. Your database password is never read — this only adds a login. Afterwards, sign in at /wp-admin and change the password.

Get alerted if it breaks again

Opt in to free uptime checks — we'll email you if your site goes down (a server error or the WordPress critical-error page), and again when it recovers. We only store the address and email you give us; nothing else.