Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.
Understand WordPress 500 internal server errors, including plugin issues, theme conflicts, PHP errors, .htaccess problems and resource limits.
Understand WordPress 500 internal server errors, including plugin issues, theme conflicts, PHP errors, .htaccess problems and resource limits.
A WordPress 500 internal server error means the server hit a problem while trying to load the site. The browser cannot show the exact cause, so the fix usually starts with recent changes, error logs, plugins, themes, .htaccess, PHP settings and hosting limits.
The important thing is not to guess. A 500 error can be caused by a small plugin conflict or a broken .htaccess rule, but random changes can make the issue harder to trace.
If the website is live or business-critical, take a backup before editing files, disabling plugins or changing PHP settings.
Start with recent changes, error logs, plugins, themes, .htaccess, PHP memory, file permissions and hosting resource limits.
A 500 internal server error is a general server-side error. It tells you that something failed while the server was processing the request, but it does not explain the exact cause on the public page.
In WordPress, the cause is often a PHP fatal error, plugin conflict, theme issue, broken .htaccess rule, memory limit, permissions problem or failed update.
The fastest way to troubleshoot is to check what changed recently and then review server error logs. Logs usually provide much more useful information than the browser message.
Most WordPress 500 errors come from a small number of areas. Check these before reinstalling WordPress or making large changes to the site.
A fatal PHP error can stop WordPress before the page loads.
A plugin update or conflict can trigger server errors across the site.
Theme functions, templates or updates can cause PHP errors.
A broken .htaccess rule can cause 500 errors before WordPress loads properly.
WordPress may fail if PHP memory limits are too low for the site.
Incorrect file or folder permissions can prevent the server reading required files.
Start with recent changes. If the error appeared after a plugin update, theme edit, WordPress update, PHP version change or migration, that change is the most likely clue.
Next, check the hosting error logs. A 500 error is too broad on its own, but the logs may identify the plugin, theme file, .htaccess rule or PHP error involved.
If the logs are not clear, disable plugins safely, test the active theme, regenerate .htaccess and review PHP memory and permissions.
| Problem | What It Usually Means | What To Check |
|---|---|---|
| 500 after plugin update | A plugin conflict or fatal error. | Disable recent plugins and check error logs. |
| 500 after theme change | The active theme may contain a PHP error. | Switch to a default theme and review theme edits. |
| 500 on every page | Site-wide PHP, .htaccess or server issue. | Check logs, .htaccess, PHP version and memory limits. |
| 500 only on some pages | A plugin, template or page builder issue. | Check page-specific plugins, shortcodes and templates. |
| 500 after migration | Paths, permissions or server settings may differ. | Check permissions, PHP version, .htaccess and config files. |
| 500 during traffic spikes | Resource limits may be reached. | Review CPU, RAM, PHP workers and hosting limits. |
Error logs are usually the most useful starting point. They can show the exact PHP error, plugin file, theme function or permission issue causing the 500 error.
If you contact hosting support, include the time the error started, the URL affected and any recent changes made to WordPress.
WordPress uses .htaccess for rewrite rules on many Apache-based hosting setups. A broken rule, duplicate directive or plugin-added change can trigger a 500 error.
Before editing .htaccess, make a copy of the existing file. You can then test a clean WordPress .htaccess file or regenerate permalinks from the WordPress admin area if access is available.
Plugins and themes are common causes of WordPress 500 errors because they run PHP code during page loading. A single faulty update can affect the whole site.
Disable recent plugins first, then test the active theme. Make changes one at a time so you can identify the actual cause.
A 500 error can feel urgent, but random fixes often make recovery harder. Work from the most likely causes and keep notes as you go.
A 500 error usually blocks the visitor from reaching the page completely. They may see a plain server error instead of your website, contact form, shop or login page.
For business websites, this can mean missed enquiries, failed purchases and reduced trust. Restoring a working page quickly matters, but the fix should still be careful and traceable.
Keep regular backups, update WordPress carefully and avoid making several major changes at the same time.
Review plugins regularly, remove anything unused and check compatibility before changing PHP versions.
For important sites, test updates on a staging copy before applying them to the live website.
A redirect or rewrite rule causes the server to return a 500 error before WordPress loads.
A plugin update introduces PHP code that fails during page loading.
The site hits memory, process or CPU limits and cannot complete the request.
Avoid broad changes that make the original error harder to trace. Focus on evidence from logs, recent changes and controlled testing.
Before editing .htaccess, disabling plugins or changing PHP versions, check the hosting error logs for the exact cause.
Logs can often identify the plugin, theme, PHP file or server limit responsible for the 500 error.
It is a server-side error that appears when WordPress or the server cannot complete the request.
Common causes include PHP errors, plugin conflicts, theme problems, .htaccess issues, permissions and resource limits.
Yes. A plugin conflict or faulty update can trigger a 500 error.
Yes. Broken rewrite or redirect rules in .htaccess can cause server errors.
Check recent changes and hosting error logs before editing files.
Yes. Incorrect permissions can stop the server reading required WordPress files.
Yes. If WordPress runs out of available PHP memory, a 500 error can appear.
Yes. CPU, memory or process limits can trigger errors during busy periods.
Only after checking recent changes and logs, unless urgent rollback is needed.
Keep backups, update carefully, monitor logs and test major changes before applying them live.
If the 500 error is still showing, collect the affected URL, when the problem started, what changed recently and any messages from the hosting error logs.
Work through plugins, theme, .htaccess, PHP version, PHP memory, permissions and resource limits in order.
If the website is business-critical, avoid repeated guessing on the live site. Use a backup, staging copy or hosting support so the fix can be made safely.
Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.