A 500 error means your server hit a problem it couldn't handle — and every minute it's down, you lose visitors and sales. Below is exactly what it means and how to fix it. If you want it sorted today, send me a screenshot.
🇬🇧 UK-based, fixing sites remotely for the UK & US. US clients: the time-zone gap means a 500 you report tonight is often fixed by your morning. Free 15-min diagnosis, fixed price from £150 (~$190).
.htaccess, exhausted PHP memory, or a failed database connection. The real cause is in your server error log, not on the 500 page. Read the log, undo the last change, and the site comes back.
A 500 Internal Server Error is the web server's way of saying "something broke while building this page, and I can't tell the visitor what." It's deliberately generic for security. The important part: the fault is on the server, so refreshing or clearing your browser cache won't fix it. The detail you need is recorded in the server's error log.
.htaccess — a bad rewrite rule or directive.error_log file in your site folder; on a server, check /var/log/ or your stack's log. This names the exact file and line.plugins folder to disable all plugins. If the site returns, re-enable them one by one to find the culprit..htaccess: rename it temporarily. If the site comes back, a rule in it is the problem.memory_limit = 256M) if the log shows a memory error.If the log points at something you can't safely change, the site is commercial and losing money, or you simply can't find it fast — that's the moment to hand it over. I read the log, find the exact cause, and apply a targeted fix, usually within hours. You get a free 15-minute diagnosis and a fixed price before any work starts — no surprises.
Send me the screenshot and what changed before it broke. I'll diagnose it free, give you one fixed price, and have you back online — usually the same day (overnight for US time zones).
It's a generic server-side error meaning the web server hit a problem it couldn't handle — often a code error, a broken plugin or theme, a bad .htaccess file, exhausted PHP memory, or a failed database connection. The visitor's browser is fine; the issue is on the server.
Read the server error log (cPanel error_log, your host's log viewer, or /var/log). The 500 page is deliberately vague, but the log records the exact file and line. Also check what changed just before it broke — a deploy, an update, or an edited config.
Almost always. Most 500s come from a recent change and are fixed within hours once the error log is read. A free 15-minute diagnosis usually identifies the cause; the fix follows the same day.
Usually not. A 500 is an execution error, not data loss — your database and files are normally intact. The priority is reading the log and reversing the change that triggered it, not wiping anything.