HTTPTools

HTTP 500 Internal Server Error

The server-side crash: your request was fine, but something broke while processing it.

What HTTP 500 means

HTTP 500 Internal Server Error is the generic “something went wrong on our side” response. The request reached the application, the application failed — an unhandled exception, a misconfiguration, a dead dependency — and the server had nothing better to say.

For visitors a 500 is not their fault and rarely fixable from the browser. For developers it always corresponds to a server-side log entry; the fix starts with finding that stack trace.

Common causes of 500 errors

  • An unhandled exception in application code (null references, type errors, failed assertions).
  • Misconfiguration: broken .htaccess or nginx directives, wrong file permissions, missing environment variables.
  • A dead or timing-out dependency: database down, migrations missing, external API failing without a fallback.
  • Resource exhaustion: out of memory, PHP/worker limits, full disk.
  • A bad deployment: missing packages, incompatible library versions, syntax errors in production code.

How to fix it as a visitor

  • Reload once after a short wait — many 500s are transient deploy or overload blips.
  • Come back later; the site's team usually knows before you can tell them.
  • Clear cookies only if the error persists for you specifically and not for others.

How to fix it as a developer

  • Read the server error log — the stack trace is the answer (nginx/apache error log, application log, APM).
  • Roll back the latest deploy first if the errors started with it.
  • Reproduce with the exact failing request from access logs; add error tracking (Sentry & co.) if you have none.
  • Never expose stack traces to users in production — log details, show a friendly page.

Example response

HTTP/1.1 500 Internal Server Error
Content-Type: text/html

<!doctype html>
<title>Something went wrong</title>

SEO impact

Sustained 500s make search engines slow their crawl and, if prolonged for weeks, can drop affected URLs from the index. Brief incidents are harmless — Google retries before deciding anything.

FAQ

Is a 500 error my fault as a visitor?

No. It is a server-side failure. Waiting and reloading is about all you can do.

Where do I find what caused a 500?

In the server's error log or your error-tracking service — every 500 corresponds to a logged exception or config error.

Do 500 errors affect SEO?

Short outages do not. Days or weeks of 500s reduce crawling and can temporarily drop pages from the index.