Backend service works fine through browser, but shows unhealthy in the Azure Application Gateway

Question

1. There is a hello world service run in Azure Container Service, its address is http://52.168.172.165, can access this address and get response successfully in browser.
2. Create an Azure Application Gateway using default setting and public IP

HTTP Setting: HTTP 80 <appGatewayBackendHttpSettings> Listeners: HTTP 80 <appGatewayHttpListener> Rules: rule1: < appGatewayHttpListener> - <appGatewayBackendHttpSettings> -<appGatewayBackendPool> Backend pools: appGatewayBackendPool Associated Rule: <rule1> Targets: 52.168.172.165 The issue is in the backend health, the status is unhealthy of 52.168.172.165:80. Since no backend service works, so when I access address of Application Gateway, it shows 502 error.

But actually I can access the service http:// 52.168.172.165:80 in browser, my question is why the status is unhealthy in Application Gateway and how to correct it?

BTW, I had done some research for the issue, like following article https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-troubleshooting-502

For my backend service,

1 a browser request to the backend service is serviceable.

2 no timeout

3 30 seconds is enough for the probe interval

So what the issue is that show unhealthy?

Answer 1

配置后端池以使用 IP 地址和 FQDN 进行健康检查对我来说非常有用。不知道为什么没有作为答案输入。