The WordPress “critical error” message usually means PHP stopped execution because of a fatal error. Do not start deleting random WordPress files: first collect enough information to identify the component that failed.
1. Check the WordPress admin email
WordPress may send a recovery email containing a link and information about the component involved. The official WordPress common-errors guide recommends checking this first.
2. Take a backup before changing files
If you still have hosting access, back up the site/database or create a restore point before troubleshooting.
3. Check error logs
Error logs can identify the PHP file, plugin or theme causing the fatal error. WordPress provides debugging documentation; debugging should be used carefully and detailed errors should not be left displayed publicly on a live site.
4. Isolate a plugin or theme failure
If the error began immediately after an update, that component is a strong lead. Use WordPress recovery mode or hosting/file access to disable the suspected plugin/theme safely, then retest.
5. Check PHP compatibility and memory
A plugin or theme may require a different supported PHP version or exhaust available memory. Check the fatal-error message before changing PHP settings.
6. Restore only when diagnosis is slower than recovery
If the site is business-critical and a known-good recent backup exists, restoration can be faster—but preserve logs or the broken copy if you still need to determine why it happened.
Hostinger also maintains a current Hostinger-specific critical error guide.
Critical-error checklist
Use the symptom to choose the next check instead of changing several settings at once. Make one change, retest the exact URL, and keep a note of what changed.
| Symptom | What it suggests | Next check |
|---|---|---|
| After plugin update | Failure began immediately after plugin change | Use recovery mode / isolate plugin |
| After theme update | Frontend/admin fails after theme change | Switch safely to known-good theme |
| PHP fatal in logs | Log names a file/function | Fix compatibility before raising limits |
| No clear cause | Site is business-critical | Preserve logs and consider known-good backup |
Before you make a risky change
Take a current backup or restore point before editing configuration files, permissions, PHP settings or database URLs. Avoid deleting unrelated DNS, email, security or rewrite rules simply to see whether the problem disappears.
How to confirm the fix
Retest the exact public URL in a private browser window and, where relevant, on a second device or network. A fix is only confirmed when the original symptom is gone without creating a new error elsewhere on the site.
