Forum Discussion
502 Bad Gateway error for Azure Application Gateway
I am facing a challenge where in App GW can't connect to a backend ubuntu VM when Azure VMSS is being used. When I tested, my python application is responding with 200 status code locally. curl https...
JeremyWallace Thank you for the response. I still get unhealthy response with same message no matter I change the interval to 20 or 30 seconds. I do not think this is a health probe issue.
I found that in HTTP backend settings for CN and SAN as below.
Subject: CN = ai-api-vmss-stage.eastus.cloudapp.azure.com
X509v3 Subject Alternative Name:
DNS:ai-api-vmss-stage.eastus.cloudapp.azure.com
Any other suggestions?
Did you try this part of my previous suggestion to confirm it not being the probe?
In addition to upping the timeout, set HTTP response status code match to 200-600. It didn't look like it was set in your screenshot so just wanted to verify. That part is more key than the timeout.