A WordPress HTTP 500 response means the server could not complete a request. Diagnose PHP fatal errors, plugins, configuration and resource limits without destroying site data.
Symptoms: how to recognize this error
- The public site or wp-admin shows a blank page or HTTP 500.
- The failure starts after a theme, plugin or PHP update.
- Only some URLs fail while others still load.
Why this error occurs
- A PHP fatal error or incompatible extension.
- Plugin/theme conflict or invalid server configuration.
- Resource limits reached during a request.
- File permissions or application bootstrap failures.
Before you begin
Use the least disruptive test first. Record the original result so you can tell whether a change helped. Product interfaces and available options vary by version.
- Create a verified backup of files and database.
- Record the exact failing URL and timestamp.
- Keep WP_DEBUG_DISPLAY disabled on production sites.
Start with Beginner steps. Advanced steps require the indicated permissions and a verified rollback plan. Open the host control panel error logs and match the request time with the first relevant fatal error. If a specific plugin update preceded the failure, rename only that plugin directory to disable it temporarily. Check the current PHP version against WordPress, theme and plugin requirements. Confirm there is no stale `.maintenance` file from an interrupted update; do not remove it during an active update. Test a public page, login and wp-admin separately after each change. In wp-config.php, set WP_DEBUG true, WP_DEBUG_LOG true and WP_DEBUG_DISPLAY false temporarily, then secure and inspect the log. If the error follows a rewrite change, compare `.htaccess` or Nginx configuration against a known-good backup. Use stack traces and plugin/theme version information to identify the failing function, rather than disabling all security controls.Step-by-Step Troubleshooting
Check hosting status and logs
Isolate the latest change
Verify PHP compatibility
Inspect maintenance state
Retest public and admin paths
Enable safe diagnostic logging
Inspect server rules
Trace the failing component
Common mistakes to avoid
- Do not set files or directories to world-writable permissions.
- Do not publish debug logs or stack traces containing secrets.
How to verify the fix
Repeat the original failing operation using the same account, network, device or application context. A successful unrelated test does not confirm the original problem is solved.
- The original failing URL returns a successful response.
- wp-admin works and error logs no longer show the same fatal error.
- Scheduled tasks and critical user journeys continue to function.
Solution Checklist
If the problem continues: rollback and escalation
Restore the previous plugin/theme or server configuration from a known-good backup if a change worsens the error; rotate credentials if compromise is suspected.
If you need vendor or hosting support, provide the product version, exact error, approximate time, affected operation and the steps already attempted. Remove passwords, private tokens and personal data from logs and screenshots.
Prevent recurrence
- Keep supported software and firmware up to date using official sources.
- Record configuration changes and maintain tested recovery options.
- Investigate repeat failures using logs and reproducible symptoms instead of applying multiple unrelated fixes.
Frequently asked questions
Does this error always have one cause?
No. The same code can appear under different account, device, service or software conditions. Match the symptoms and diagnostic evidence before selecting a repair.
Should I reset or reinstall everything?
Usually not as a first step. Try reversible checks first, verify backup availability and use the vendor-supported recovery process only when the evidence points to a damaged installation.
What should I collect before contacting support?
The exact error, software and device versions, the failing operation, time of occurrence, a sanitized screenshot and the outcome of each attempted fix.
For additional guides, see the PRBLEM Solutions directory and choose the matching platform or error code.
Official references
The links above are official documentation entry points or relevant vendor guides. Confirm current product-specific instructions before changing production systems; a matching error message alone does not establish a root cause.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.