Case 10 · WordPress troubleshooting
Getting a 500 Internal Server Error? Finding and Fixing the Root Cause
Short answer
A 500 Internal Server Error means the server failed while building the page but did not say why. In WordPress the usual causes are a corrupted .htaccess file, a plugin or theme PHP error, an exhausted PHP memory limit or wrong file permissions. The server error log almost always points to the exact cause.
The challenge
This is a typical scenario based on the kinds of challenges WordPress site owners bring to us. Names and details are illustrative.
A manufacturer’s website has worked well for years. One afternoon a team member installs a redirection plugin to fix a few old links. Within minutes, every page, including the admin area, shows “500 Internal Server Error”. The team assumes the hosting company is having problems and waits. Two hours later, the site is still down.
The server’s error log tells a different story: the new plugin wrote rules into the .htaccess file that the server could not understand. Every request now fails before WordPress even starts. Because the admin area is also behind the same rules, the plugin cannot be switched off from the dashboard.
Warning signs to look for
- Pages show 'HTTP ERROR 500' or '500 Internal Server Error'.
- Only some pages fail, for example the admin area, checkout or a specific form.
- The error appears after installing a plugin, changing permalinks or editing settings.
- The site works for some visitors and fails for others at busy times.
Common causes
- Corrupted .htaccess file
- A plugin, security tool or manual edit writes an invalid rule into .htaccess, and the web server refuses every request.
- PHP fatal errors
- A plugin or theme calls a function that does not exist in your PHP version, or two plugins declare the same function.
- PHP memory or execution limits
- Heavy pages, imports or reports run out of memory or time and the server ends the process.
- Wrong file permissions or ownership
- After a migration or manual upload, the server cannot read or execute files it needs.
- Server-level problems
- Misconfigured hosting, a failing PHP handler or resource limits on shared hosting.
What it costs your business
A 500 error looks broken and untrustworthy to visitors, and if it affects checkout or contact forms, it silently blocks revenue. Repeated server errors also make search engines crawl the site less and can affect rankings if they persist.
Our approach
- 1
Locate the failing requests
We check which pages and actions return 500, and when it started, to narrow the search to a change, a page type or a time of day.
- 2
Read the server error log
The hosting error log and the WordPress debug log usually show the precise file and line that failed, or a memory or permissions message.
- 3
Rule out .htaccess
We back up the current .htaccess, replace it with the default WordPress rules and test. If the site returns, we rebuild the custom rules carefully.
- 4
Isolate plugins and the theme
If logs point to code, we deactivate the plugin or theme responsible, or test them one by one on a staging copy, to confirm the culprit.
- 5
Fix and harden
We update or replace the faulty component, raise PHP limits only where justified, correct file permissions and confirm every affected page works.
Services delivered
WordPress Maintenance
- We read logs and isolate the cause instead of guessing, so fixes are permanent.
- Every change is backed up first, so it can be undone safely.
- Monitoring catches recurring server errors early.
- Monthly reports flag plugins that are falling behind PHP compatibility.
The outcome
Restoring the default WordPress rules brings the site back within minutes. The longer-term fix is to rebuild the redirects properly, and to make sure risky server-level changes are always made with a backup in place and someone who can read the logs.
How to prevent it happening again
- Make changes to .htaccess and server settings only with a backup and a quick way to undo them.
- Keep plugins compatible with your PHP version and remove plugins you no longer use.
- Watch PHP memory use on heavy pages and stores before it becomes a crash.
- Use staging for new plugins and major updates.