Application Request Routing Error – 502.4 – Bad Gateway

This articles has been moved to its new home here:

I was setting up an Application Request Routing server and received the error shown in Figure 1 when I attempted to access the ARR URL.

Figure 1, HTTP Error 502.4 – Bad Gateway

The cause was due to the Health Status of the servers being set to “Unhealthy” as shown in Figure 2.  They were set to "Unhealthy" because the Health Tests which I previously configured failed.

Figure 2, Monitoring and Management, Health status set to Unhealthy

To correct this, I first resolved the issues with my Health Tests.  I then selected one of the app* servers and in the Action pain selected “Set Server as Healthy” as shown in Figure 3.

Figure 3, Monitoring and Management, Set Server as Healthy

You should be aware that if the Health Test you configure fails, the server will be set to Unhealthy.


Comments (3)

  1. Anonymous says:

    Hi, I passed the health test but it told me that my server is unhealthy. And the imcoming request gave me a 404 error. Would you mind giving me any suggestions on that?

  2. Anonymous says:

    I've got similar situation :/ sometimes, after IIS restart, my sites works, but only for a while, after few refreshes i get 502.4 error 🙁 I think it could be connected with proxy settings.

  3. Hi, you might get some good response if you ask the same question on the IIS forums here:

Skip to main content