A WordPress 500 Internal Server Error means the server failed while trying to complete a request, but the browser was not given a more specific explanation. On WordPress sites, the cause is often a plugin or theme conflict, a PHP fatal error, a damaged rewrite rule, exhausted server resources, a cache problem or a hosting-level configuration issue.
If your site is down and you would rather have the problem diagnosed for you, see our WordPress Emergency Fix service. If you want to troubleshoot it yourself first, work through the checks below in order.
What does a WordPress 500 error actually mean?
The HTTP 500 status code is a general server error. It tells you that something failed on the server side, but it does not identify the exact component. That is why randomly changing plugins, themes and server settings can make the problem harder to diagnose.
The best approach is to identify what changed immediately before the error, check the available logs, and then isolate one possible cause at a time.
Before you start: protect the website first
- Take a backup of the website files and database if your hosting panel still allows it.
- Write down what changed before the error appeared: plugin updates, theme updates, PHP changes, migrations, DNS changes or server configuration edits.
- Check whether the error affects the entire site or only one page, wp-admin, checkout, REST API or another specific area.
- Do not overwrite configuration files before making a copy of the current version.
- Make one change at a time and test again so you know which action actually fixed the problem.
1. Check the PHP or server error log first
If your host provides cPanel, Plesk or another hosting dashboard, look for an error log before changing anything. A recent fatal PHP message can point directly to the plugin, theme or file that triggered the 500 error.
Useful clues include messages such as PHP Fatal error, Allowed memory size exhausted, missing function or class errors, permission failures and syntax errors. Focus on log entries created at the same time the website failed. Old warnings from weeks or months earlier may be unrelated.
If WordPress debugging is already enabled, you may also have a wp-content/debug.log file. Do not enable public error display on a live production site unless you understand the security implications; logs are safer than showing errors to visitors.
2. Test for a plugin conflict
A plugin conflict is one of the most common causes when a 500 error appears immediately after an update or installation.
If you can still access wp-admin
- Open Plugins → Installed Plugins.
- Deactivate the plugin that was most recently updated or installed.
- Reload the affected page.
- If the error remains, continue testing likely plugins one at a time.
If wp-admin also returns a 500 error
Use cPanel File Manager, FTP or SFTP and go to wp-content/plugins. Rename the folder of the suspected plugin, for example from plugin-name to plugin-name-disabled. WordPress will no longer be able to load that plugin. Test the site again.
If you do not know which plugin is responsible, renaming the entire plugins directory can temporarily disable all plugins for diagnosis. Restore the original folder name afterwards and reactivate plugins carefully. On ecommerce or membership sites, disabling all plugins can affect customer functions, so use this method cautiously.
3. Check whether the active theme caused the failure
A theme can cause a 500 error after a PHP compatibility problem, a bad code edit or a failed update. If the error began immediately after a theme change, this becomes a strong suspect.
If wp-admin is available, temporarily activate a standard WordPress theme and test the site. If wp-admin is unavailable, you can rename the active theme directory through File Manager or FTP. WordPress can fall back to another installed theme if one is available.
Do not delete the theme while troubleshooting. Renaming preserves the files and gives you an easy way to restore them.
4. Check the .htaccess and rewrite rules
On Apache or LiteSpeed hosting, a damaged or incompatible .htaccess file can cause 500 errors or incorrect routing. This is especially relevant after permalink, security, cache or SEO configuration changes.
Before changing it, download or copy the existing .htaccess. If you suspect the file, temporarily rename it to something such as .htaccess-old and test the site. If WordPress loads again, the problem is inside that file or one of its directives.
If wp-admin is accessible, visiting Settings → Permalinks and saving the current permalink structure can regenerate WordPress rewrite rules. However, do not overwrite custom LiteSpeed, security, redirect or SEO rules without preserving them first. Many WordPress sites legitimately need additional directives beyond the default WordPress block.
5. Check PHP version, memory and compatibility
A WordPress site can fail after the hosting account changes PHP version or when a plugin requires more memory than the server currently allows.
- Confirm that your WordPress core, theme and important plugins support the active PHP version.
- Look in the error log for Allowed memory size exhausted before increasing memory blindly.
- If the problem started immediately after a PHP upgrade, test a supported previous PHP version through your hosting control panel if your host allows it.
- Check whether required PHP extensions are missing after a server migration or hosting change.
Increasing PHP memory can help when the log clearly shows memory exhaustion, but it will not solve a coding error, plugin conflict or broken rewrite rule.
6. Check file permissions and ownership
Incorrect file permissions can prevent the web server from reading or executing WordPress files. Typical WordPress installations commonly use 755 for directories and 644 for files, but the correct ownership and permissions depend on the hosting environment.
If the 500 error appeared after moving files manually, restoring a backup, changing ownership or migrating the site, ask the host to confirm the correct permissions rather than applying broad permissions such as 777.
7. Purge caching after the underlying fix
A server or page cache can continue serving an old error response even after the real problem has been corrected. After fixing the cause, purge your WordPress cache plugin, server cache, object cache and CDN cache if applicable.
Then test the website in a private or incognito browser window. This is important because logged-in administrators and guest visitors can receive different cached responses.
8. Check whether the problem is actually at the hosting level
If disabling plugins, testing the theme and checking WordPress configuration does not change the error, the issue may be outside WordPress. Examples include a server resource limit, PHP-FPM problem, LiteSpeed or Apache configuration, a web application firewall rule, database outage or hosting account restriction.
At that point, provide your host with the exact URL, timestamp of the failure and relevant log entries. This gives support a much better starting point than simply reporting that the website is down.
Quick diagnosis: what changed just before the 500 error?
| What happened before the error? | Check first |
|---|---|
| Plugin update or installation | Plugin conflict and PHP error log |
| Theme update or code edit | Theme files and PHP fatal errors |
| Permalink, redirect or cache change | .htaccess and rewrite rules |
| PHP version changed | Compatibility, extensions and error logs |
| Site migration | Permissions, PHP configuration, database and paths |
| Error fixed but visitors still see it | LiteSpeed, page cache, object cache or CDN cache |
When should you stop troubleshooting and get help?
Stop making changes if you do not have a current backup, the site handles active orders or customer data, the error involves the database, you suspect malware, or each attempted fix is creating additional problems.
For one focused WordPress issue, DevTechi offers a WordPress Emergency Fix service starting from $39. We can troubleshoot 500 errors, critical errors, plugin conflicts, failed updates and other common WordPress failures. Larger recovery, malware, migration or multi-issue work is assessed separately before additional work begins.
Frequently asked questions
Can a WordPress plugin update cause a 500 error?
Yes. An incompatible plugin update can trigger a PHP fatal error or conflict with another plugin, theme or PHP version. Check the error log and test the plugin that changed immediately before the failure.
Is a WordPress 500 error the same as the critical error message?
Not exactly. A critical error is WordPress’s user-facing response to certain fatal PHP errors, while HTTP 500 is a general server-error status. The same underlying PHP problem can sometimes produce either symptom depending on the request and server configuration.
Can I fix a 500 error without WordPress admin access?
Often, yes. cPanel File Manager, FTP/SFTP, server logs and hosting controls can be used to disable a broken plugin or theme, inspect files, review logs and test configuration even when wp-admin is unavailable.
Will clearing the cache fix a 500 error?
Clearing cache can remove a stale cached error after the underlying problem has been fixed, but it usually does not repair the original PHP, plugin, theme or server failure by itself.
How can I reduce the chance of another emergency?
Use reliable backups, test major updates carefully, keep WordPress components maintained and monitor hosting health. Our guide on why website maintenance is cheaper than emergency recovery explains the preventive side in more detail. For ongoing help, see Technical Support & Maintenance.