Server overload: the server ran out of resources and crashed, triggering an HTTP error 502.

The most likely causes of the 502 Bad Gateway are: These indicate that the request was accepted, but the server prevented the fulfillment of the request.Ĭheck Out Our Video Guide to Fixing Different Types of 500 Errors What Causes the 502 Bad Gateway Error? There are many different types of 500 status error codes ( 500, 501, 502, 503, 504, 508, 520, etc.) which all have slightly different meanings. “502 Server Error: The server encountered a temporary error and could not complete your request”īad Gateway: The proxy server received an invalid response from an upstream server It’s basically the servers way of notifying you that something has gone wrong, along with the code on how to diagnose it. Typically an HTTP status code isn’t seen unless something goes wrong.

The web server receives and processes the request, and then sends back the requested resources along with an HTTP header and HTTP status code.

The 502 (Bad Gateway) status code indicates that the server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.Įvery time you visit a website your browser sends a request to a web server. The Internet Engineering Task Force (IETF) defines the 502 Bad Gateway error as: The 502 Bad Gateway error specifically means that the server received an invalid response from an inbound server.

Palia free instal