500 Internal Server Error
A 500 error is your server saying "something broke, and I'm not telling you what."
It's the least helpful error on the web — deliberately vague so visitors don't see your internals. The real story is written in the server's error log, and reading that log is most of the fix.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
HTTP 500 means the server tried to build your page and crashed partway — the code threw an error, ran out of a resource, or hit a configuration it couldn't obey. The browser page is a privacy curtain; the actual cause is recorded server-side, in the error log, usually with a line number attached.
That's why 500s feel random but almost never are. Something changed — an update, a plugin, a config edit, a resource ceiling — and the log knows which. Diagnosis is the art of reading it before touching anything.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
A plugin or theme update that went wrong
The overwhelming WordPress favorite: an update ships code that fatals on your PHP version or collides with another plugin. The site often breaks minutes after an auto-update nobody watched.
A corrupted or misconfigured .htaccess
One bad rewrite line takes the whole site down. Common after security plugins, migrations, or hand edits.
PHP memory or execution limits
The page needs more memory or time than the server allows — often surfacing on admin pages and imports first.
PHP version mismatch
The host upgraded PHP, and code written for an older version fatals. Frequently arrives with the host's 'we've upgraded your server!' email.
File permissions or a failed deploy
Half-uploaded files or wrong ownership after a migration — the server literally can't read its own code.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Reload once, then check whether it's everywhere
One page or every page? Front end or wp-admin too? A 500 on one URL points at that page's code; site-wide points at config, .htaccess, or a fatal in something global.
- 2
Check your host's status page and error log
Most hosting dashboards expose the error log. The last few lines usually name the failing file — a plugin path is your culprit in plain text. You don't need to understand it; note it.
- 3
If it started after an update, note exactly what updated
The dashboard's update history (or the timing of the auto-update email) is diagnostic gold. Don't start deleting — knowing which suspect walked in last is enough.
Stop and call when…
- The log names a file and you're tempted to edit code live on the server
- You're considering restoring a backup over the current site without knowing what broke
- It's a store or lead-generating site and every hour is costing you money
From there it’s our job: same-day look, flat quote, and the $229 flat repair covers most cases of exactly this.
Single Error Fix — buy it now, skip the hunt.
One error, hunted down and fixed — 500s, white screens, redirect loops, broken pages.
Covers one specific error or broken behavior on one site. Diagnosis, the fix, and a plain-English note on what happened. If we can't fix it, you get a full refund.
Questions we hear a lot.
Will refreshing or waiting fix a 500 error?
Rarely. Unlike a 502/503, a 500 usually means code is failing the same way every time. If it comes and goes, that points at resource limits under load — still a diagnosable cause, not weather.
Can I just disable all my plugins?
It's the classic move, and it works as a blunt instrument — but doing it via FTP renames while the site is live can create its own mess, and it tells you 'a plugin' without telling you which or why. The error log gives the same answer without the demolition.
Why does my site work but wp-admin shows a 500?
Admin pages load more code — updates, editors, cron. A memory limit or an admin-only plugin conflict shows there first. It's actually a useful clue: the failing code is in the admin-only set.
What does the flat-price fix cover?
Diagnosis from the logs, the repair itself, and a plain-English note on what broke and why — $229, refunded in full if we look and can't fix it. Deeper damage (a hacked site, a failing migration) gets an honest scope before anything is spent.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
- White Screen of DeathThe 500's silent twin — same family, different symptom.
- Database Connection ErrorWhen the crash is the database's fault instead.
- Stuck in Maintenance ModeThe other way updates take a site hostage.
- Emergency RepairSite down and bleeding? This lane starts today.
- Website RepairThe full bench, flat quotes, any platform.
Ten minutes of log-reading beats a day of guessing.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.