500 Internal Server Error — Causes and How to Fix It

Browser mockup of a 500 Internal Server Error page with a server icon and a warning badge saying the real error is in the server log

Last tested: November 14, 2026 · By Alex A 500 internal server error means the request reached the server, the server started working on it, and then something broke before a valid response could be built. The browser, the DNS and the network all did their part. The failure is inside the server: a crashing

504 Gateway Timeout: How to Fix It Fast

Last tested: October 22, 2026 · By Alex 504 Gateway Timeout means a proxy or CDN waited too long for a response from the backend server 504 Gateway Timeout means a server acting as a gateway or proxy did not receive a response from the upstream server in time. The request reaches the gateway, but

502 Bad Gateway — Causes and How to Fix It

Browser mockup showing a 502 Bad Gateway page with a proxy to upstream connection broken by a red error mark

Last tested: November 8, 2026 · By Alex 502 Bad Gateway appears when a server acting as a gateway or proxy receives an invalid response from an upstream server. The request reaches the gateway, but the backend service fails to respond correctly. The connection may be refused, reset, closed early, or answered with something that

503 Service Unavailable — Causes and Practical Fix

Browser mockup showing a 503 Service Unavailable page with a maintenance cone and a Retry-After 600 badge

Last tested: November 8, 2026 · By Alex 503 Service Unavailable means the server is running but cannot process the request right now. The web server is reachable, but the application or backend service is temporarily unable to respond. Unlike most other 5xx codes, a 503 is often sent on purpose: during maintenance, when account