What a WordPress 500 Internal Server Error means
The 500 status is a general server error. Your browser reached the website, but something failed while the server was building the response. The message itself does not identify the faulty plugin, PHP file or server setting, so the useful evidence is normally in the PHP, WordPress or web server logs.
A 500 error can affect the whole site, only wp-admin, one page, an AJAX request or a particular action such as saving a post. That difference matters. If the error began immediately after an update, installation or code change, start there rather than changing unrelated settings.
Before editing files, changing plugins or touching the database, take a full backup of both the website files and database. If your host provides a staging environment, reproduce the problem there where possible.
Common causes of a WordPress 500 error
Plugin and theme PHP errors are among the first things to investigate, particularly after an update. PHP 8.x can expose compatibility problems in older code, including fatal type errors, calls to removed functions and uncaught exceptions.
Other common causes include a damaged or unsupported Apache .htaccess directive, an exhausted PHP memory limit, incorrect file permissions, a failed deployment, or a server module or PHP configuration problem. WordPress also documents plugin conflicts, theme problems and insufficient PHP memory as useful troubleshooting points.
The timing provides valuable evidence. An error that appears only during imports, backups, checkout processing or other heavy requests can point towards memory or execution limits. A failure immediately after changing permalink or security settings makes rewrite rules or access controls more relevant.
How to fix a 500 Internal Server Error in WordPress
- Check whether the error is still present. Test the home page, wp-admin and an affected URL in a private browser window. If you use a CDN or host cache, clear it through the normal control panel rather than repeatedly changing WordPress.
- Undo the most recent change. If the error followed a plugin, theme or code update, roll that specific change back using a known good backup or staging copy.
- Test plugins. If wp-admin works, deactivate recently changed plugins first. If WordPress is inaccessible, use your hosting file manager or SFTP to rename the relevant plugin directory inside wp-content/plugins. If necessary, WordPress documents renaming the plugins directory to deactivate all plugins. Restore the directory name afterwards and reactivate plugins individually to identify the cause.
- Check .htaccess on Apache hosting. Take a copy first. Temporarily rename .htaccess and test the site. If WordPress loads, create fresh rewrite rules by visiting Settings, Permalinks and saving the existing structure. Nginx does not use .htaccess, so this step does not apply to Nginx configuration.
- Read the logs. WordPress debugging can write PHP errors to wp-content/debug.log. On a production site, log errors without displaying them to visitors, investigate the relevant request, then disable debugging and remove or protect exposed log files. Your host's PHP and web server error logs may contain information that WordPress cannot record.
- Check resource limits. An 'Allowed memory size exhausted' entry points to PHP memory exhaustion. Confirm the configured PHP memory_limit and the host's actual account limits before increasing anything. Raising a limit can restore service, but it should not replace finding a plugin, query or process that consumes excessive resources.
When to get help with a WordPress 500 error
Stop making changes if the logs point to unfamiliar PHP code, database damage, repeated failures after rollback, suspicious files or a server configuration you do not control. Avoid replacing WordPress core files or making broad permission changes without establishing the cause.
If you need the incident investigated, our Emergency Fix is £249 per incident with response within 2 working hours. Ongoing WordPress care plans start at £59 a month if you want updates, backups and monitoring handled routinely.