A 500 error is a server-side failure, not a specific WordPress diagnosis. The useful evidence is in the HTTP response, server/PHP logs and the exact request that fails.
Symptoms
- The browser shows “500 Internal Server Error” or a blank server error page.
- Only wp-admin, AJAX, REST API or specific frontend URLs fail.
- The error started after changing PHP, .htaccess, plugins, server rules or a deployment.
- Hosting logs show 500 responses, PHP fatals, permission errors or resource-limit failures.
Common causes
The same visible WordPress error can have several causes. A reliable fix starts by matching the symptom to logs, request behavior and recent changes.
- PHP fatal errors or incompatible code.
- Invalid .htaccess or rewrite directives.
- Incorrect file ownership or permissions.
- PHP memory, execution-time or process limits.
- Broken server modules, security rules or plugin-generated configuration.
Safe diagnosis
- Identify whether every request fails or only a specific path such as /wp-admin/ or admin-ajax.php.
- Read the web-server and PHP error logs for the exact timestamp of the 500 response.
- Validate .htaccess changes and WordPress rewrite rules.
- Check permissions, PHP version and resource limits before changing application code.
Production safety: create a recovery point before changing code, plugins, database values or server configuration. Business-critical WooCommerce sites should avoid random deactivate/update experiments during active traffic.
How the issue is fixed
- Correct the fatal PHP error or restore the incompatible component.
- Replace invalid rewrite rules with a known-good WordPress configuration.
- Fix ownership/permission problems without making files world-writable.
- Adjust server limits only when logs show a genuine resource ceiling, then investigate what consumes the resources.
Avoid this shortcut: Avoid chmod 777 as a “fix.” It can create a security problem while masking the real permission or ownership issue.
When to request expert WordPress bug fixing
Professional troubleshooting is useful when the site is business-critical, the error returns after a temporary fix, wp-admin is unavailable, the failure began after a complex update/migration, or you cannot identify the responsible code from logs. WP•FIX focuses on the smallest safe change that restores the failing path and explains the root cause.
FAQ
Is a 500 error a hosting problem?
Sometimes, but WordPress code can also trigger it. Server logs usually distinguish application failures from infrastructure errors.
Can .htaccess cause a 500 error?
Yes. Invalid directives, unsupported modules or malformed rewrite rules can produce an immediate 500 response on Apache/LiteSpeed servers.
Why does only wp-admin return 500?
Admin-specific hooks, plugins, PHP requests or security rules can fail while cached frontend pages continue to load.
Can you fix a 500 error if the site is completely down?
Yes. Diagnosis can start from hosting/SFTP access and logs even when WordPress itself is unreachable.
Need this WordPress issue fixed?
Send the URL, error message and what changed immediately before the problem started.
Request troubleshooting