A HTTP 500 Internal Server Error is one of the most common and most vague error messages you’ll encounter as a website administrator. The server indicates that something is going wrong, but not exactly what. Fortunately, there are a limited number of causes that are almost always responsible, and with a structured approach you’ll usually find the problem back within a few minutes.
What exactly does a 500 error mean?
Error code 500 is an umbrella term for server-side errors where the server cannot handle the request. Unlike a 404 (page not found) or a 403 (no access), a 500 doesn’t give a clear direction. The error can originate in your code, in a configuration file, in the database, or even in the server resources themselves.
Because the message is so generic, it’s important to determine through log files what’s really going wrong. Just looking at the error message alone is rarely enough.
Common causes
The most common causes of a 500 error are:
- Faulty .htaccess file β an incorrect rule or syntax error causes an immediate crash.
- PHP errors in theme or plugins β for example, an outdated plugin that isn’t compatible with your PHP version.
- Insufficient memory (memory limit) β scripts that need more memory than allowed.
- Incorrect file permissions β files or folders with permissions that are too strict or too loose.
- Database connection issues β the application cannot reach the database, for example due to incorrect login credentials.
- Exceeded resource limits β too many simultaneous processes on a shared hosting package.
Step-by-step solution
View the error logs
In Plesk, you can find the error logs per domain under the website settings. This often shows exactly which file or line is causing the error.
Check your .htaccess file
Temporarily rename the file to .htaccess_old and refresh the page. Does the site work now? Then the problem was in this configuration and you can rebuild the file.
Deactivate plugins and themes
In WordPress, turn off all plugins via the file manager (rename the plugins folder) and switch back to a default theme. Then activate them one by one to find the culprit.
Increase the memory limit
Adjust the PHP memory limit via Plesk or in your wp-config.php file if the problem is related to insufficient memory.
Check file permissions
Folders should generally have permissions of 755 and files 644. Deviating permissions can block the server.
Restore a recent backup
Can’t figure it out? Then restore a working backup from before the problem occurred and calmly investigate afterwards what went wrong.
Preventing a 500 error in the future
Many 500 errors arise from updates that haven’t been properly tested or from a hosting environment that doesn’t offer enough resources for the website. Make sure you have regular backups so you can always fall back on a working version, and preferably test major updates on a staging environment first.
Not sure if your current hosting package still offers sufficient capacity? Then take a look at the options at webhosting with sufficient resources and NVMe storage. If the problem goes beyond what you can solve yourself, the support team can help via the knowledge base or look into the issue directly with you.
Frequently Asked Questions
Why do I only see a 500 error on certain pages?
This often indicates a problem with a specific script, plugin, or template that’s only loaded on that page, rather than a general server error.
Can a 500 error be caused by the hosting server itself?
Yes, for example due to temporary overload or an outage. In that case, always check first whether the log files report anything about resource limits.
Does a 500 error disappear on its own?
Sometimes, if it’s a temporary spike in server load. If the error recurs frequently, there’s usually a structural problem underlying it that needs to be resolved.
Conclusion
A 500 Internal Server Error is annoying but usually easy to resolve by systematically checking the logs, .htaccess, plugins, memory limits, and file permissions. With a recent backup on hand, you can almost always solve the problem safely.