500 Error
WordPress 500 internal server error — diagnosed and fixed.
The actual causes, in the order you should check them. Plus same-day recovery if you'd rather just have it fixed.
HTTP 500 is the server's way of saying "something went wrong and I can't be more specific". It can be triggered by a single typo in .htaccess, a fatal PHP error, a plugin trying to use a function that no longer exists, or your host's PHP version being upgraded under your feet.
The good news: it's almost always quick to fix once you know where to look.
What you get
1. Check error_log
First port of call. Your host's error_log will name the file and line that died.
2. Regenerate .htaccess
Corrupted .htaccess causes a surprising chunk of 500s. Rename and re-save permalinks.
3. Increase PHP memory
Add WP_MEMORY_LIMIT to wp-config.php — bump to 512M for diagnosis.
4. Disable plugins
Rename /wp-content/plugins via FTP. Site back? Re-enable one by one.
5. Switch theme
Rename your theme folder. Fallback to Twenty Twenty-Four. Isolates theme vs plugin.
6. Check PHP version
Hosts sometimes upgrade PHP without warning. Older plugins die on PHP 8+. Roll back via hosting panel.
Get a free quote
Tell me about your project.
A few quick questions and I'll come back with a tailored quote — usually within one working day.
Step 1
What service do you need?
Book a call
Free 30-minute consultation
Walk through your project, get honest advice, leave with a clear plan. No pressure, no waffle.
FAQs