The most frequent culprit is that the service you are trying to reach has crashed or is in the middle of a reboot. The gateway sees the connection drop or receive a "Connection Refused" and reports it to you as a 502. 2. High Load and Timeouts
System.Net.WebException: The remote server returned an error (502) Bad Gateway. The most frequent culprit is that the service
When the remote server returns a valid HTTP response but with an error status code (>= 400), the WebException is raised with the Status property set to WebExceptionStatus.ProtocolError . You can then inspect the response to retrieve the actual HTTP status code—in this case, 502. High Load and Timeouts System
In the world of .NET development, few things are as frustrating as an unhandled exception that brings your application to a screeching halt. Among the most common and confounding of these is the System.Net.WebException with the message: In the world of