Home > Error > 500
500 Internal Server Error
The server encountered an internal error and was unable to complete your request.
Either the server is overloaded or there is an error in the application. Please contact the system administrator if the problem persists.
Possible causes
- An unhandled exception in the application code
- A misconfigured environment variable on the host
- An upstream service required by the page returning an unexpected response
- A failed database query or missing migration
- Temporary resource pressure (high CPU or memory)
- A corrupt cache entry being served to the handler
- A bug introduced in the most recent deployment
Sample error log
[14:14:33] ERROR request_id=req_91ac handler=dashboard
[14:14:33] panic: runtime error: invalid memory address or nil pointer dereference
[14:14:33] goroutine 42 [running]:
[14:14:33] at /app/handlers/dashboard.go:148
[14:14:33] at /app/server/http.go:62
[14:14:33] at /app/middleware/recover.go:33
[14:14:33] HTTP/1.1 500 Internal Server Error
Diagnostic information
Status:500 Internal Server Error
Method:GET
Request URI:/dashboard
Server:apache/2.4 (Linux)
Worker:web-7
PID:14282
Request ID:req_91ac-2008-de31
Trace ID:tr_4f02-aa12
Time:Tue, 19 May 2026 14:14:22 GMT
Notice: More information about this error may be available in the server error log. Please include the request ID req_91ac-2008-de31 when reporting the issue.
Related status codes
| Code | Meaning | Server side? |
|---|
| 500 | Internal Server Error | yes |
| 502 | Bad Gateway | yes |
| 503 | Service Unavailable | yes |
| 504 | Gateway Timeout | yes |
What to do next
- Refresh the page in a minute or two — many transient issues self-resolve
- Clear your browser cache and try again if the error persists
- Visit the status page to check for ongoing incidents
- Contact the administrator with the request ID above
- If you are a developer, check the application logs first
For developers: Most 500 errors are caught by the application's recovery middleware. Search your logs for the request ID to find the originating exception.
apache/2 — running at host.example — IPv4/IPv6 — server time 14:14:22 GMT