HTTP 500 Internal Server Error

What HTTP 500 means

500 Internal Server Error is the catch-all server error. The request was fine, but something broke while handling it — most often an unhandled exception in the application code. The response body rarely contains useful detail by design (to avoid leaking internals), so diagnosis happens in the server logs.

Common causes

• An unhandled exception in application code
• A database connection failure or query error
• A misconfiguration (missing env var, bad credentials)
• A bug introduced in a recent deploy
• An out-of-memory or resource-exhaustion condition

Example JSON error response

{
  "error": "Internal Server Error",
  "message": "An unexpected error occurred. Please try again later.",
  "status": 500
}

Raw HTTP response

HTTP/1.1 500 Internal Server Error
Content-Type: application/json

How to troubleshoot HTTP 500

• ✓ Check the server logs for the stack trace or exception
• ✓ Look for an unhandled exception in the request path
• ✓ Verify database connectivity and configuration
• ✓ Check whether a recent deploy introduced the error
• ✓ Reproduce with a minimal request to isolate the cause

500 vs 502 vs 503 — what's the difference?

500 Internal Server Error is a generic failure inside the application handling the request. 502 Bad Gateway means a proxy got an invalid response from an upstream server. 503 Service Unavailable means the server is temporarily overloaded or down for maintenance. 500 points at your app code; 502 and 503 point at infrastructure or upstream services.

Handling a 500 in client code

A 500 is a server-side fault, so a single retry can be reasonable (the error may be transient) — but only with backoff and a cap, and never for non-idempotent operations you can't safely repeat. Surface a friendly message rather than the raw error:

const res = await fetch('/api/report');

if (res.status >= 500) {
  // transient server fault — retry GET with backoff (not POST/PATCH blindly)
  return retryWithBackoff(() => fetch('/api/report'), { max: 3 });
}
if (!res.ok) { /* handle 4xx — do not retry */ }

Don't leak stack traces in the JSON body

A frequent security mistake is returning the raw exception and stack trace in the 500 response body. That exposes file paths, library versions, SQL, and sometimes secrets to anyone who can trigger the error. Return a generic message to the client and keep the real detail in your server logs (with a correlation/request ID the client can quote to support):

{
  "error": "Internal Server Error",
  "message": "Something went wrong. Contact support with this ID.",
  "request_id": "req_8f3c2a",
  "status": 500
}