Developer
Encoders, converters & dev utilities
500 Internal Server Error
HTTP 500 Internal Server Error. A generic catch-all — the server hit an unexpected condition (usually an unhandled exception) that prevented it from fulfilling the request. Not the client's fault. When to use it: Return when server-side code fails unexpectedly and no more specific 5xx applies. It is a server-error (5xx) status, which means the request was valid but the server failed to fulfil it. (Reference: RFC 9110 §15.6.1.)
A generic catch-all — the server hit an unexpected condition (usually an unhandled exception) that prevented it from fulfilling the request. Not the client's fault.
- When to use: Return when server-side code fails unexpectedly and no more specific 5xx applies.
- How to handle: Inspect server logs/stack traces to find and fix the underlying exception; the client can retry once fixed.
- Reference: RFC 9110 §15.6.1
- Category: 5xx Server Error
Frequently asked questions
What does HTTP 500 mean?
HTTP 500 Internal Server Error: A generic catch-all — the server hit an unexpected condition (usually an unhandled exception) that prevented it from fulfilling the request. Not the client's fault. It is a server-error (5xx) status, which means the request was valid but the server failed to fulfil it. It is defined in RFC 9110 §15.6.1.
What causes a 500 Internal Server Error and how do I fix it?
500 Internal Server Error is a generic catch-all: the server hit an unexpected condition, usually an unhandled exception, that stopped it fulfilling an otherwise valid request. It is not the client’s fault. To fix it, inspect the server logs and stack traces to find the underlying error, fix the code or configuration, and the client can then retry. If the failure is in an upstream dependency, you may instead see 502 or 504.