Web Technician OnlineWhat does this mean?
The critical-error message indicates that WordPress encountered a serious application failure. The visible notice is deliberately general. A plugin, theme, PHP compatibility issue or resource limit can cause it, so choose the next step using logs rather than the message alone.
What should I check first?
Check whether the public site, admin area or both fail and note recent changes. Verify a restorable file and database backup. If WordPress sends a recovery-mode email, treat its link as sensitive and confirm it came through the expected system before using it.
How can I diagnose the cause?
Read the host’s PHP error log at the recorded time. Look for the first relevant fatal error and the component named in its path. Public error display can reveal sensitive details; use deliberate protected logging on staging where possible and do not leave debugging output visible to visitors.
How do I fix it safely?
Use recovery mode or supported hosting controls to disable the specifically implicated component, or restore a compatible version from a verified backup. If PHP changed, confirm compatibility with the host and plugin maintainer. Avoid deleting plugins, altering database values blindly or editing core files as a generic remedy.
Verify the fix and know when to contact your provider
After access returns, test the action that failed plus login, forms and scheduled jobs. Remove temporary debugging and secure or delete its logs. Contact the host for server or PHP restrictions and the component maintainer for code faults, supplying versions and a minimal redacted error example.
Work through these checks in order
- Record whether admin and the public site both fail, then read the matching PHP fatal error. If recovery mode is available, protect its link like an account-access token.
- Use a verified backup and supported controls to isolate the component the log identifies. Confirm PHP compatibility before changing versions or reinstalling unrelated parts of the site.
- Retest the original action and essential functions, then disable temporary debugging and secure its logs. Share only a minimal redacted example with the host or component maintainer.
Which tool can help?
DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.