Score:0

Azure Application Gateway Health Probes are not being resolved correctly by apache/nginx

io flag

I am using Azure ApplicationGateway and have implemented Health Probes. I have a number of health probes, with different domains.

I struggled with Apache for weeks, trying to get a healthy probes, but got nothing but certificate mismatch errors no matter what I tried.

After a lot of pain, and switching to nginx as a test, I've discovered that the probe hostnames are not matching correctly to the right server configuration, but rather are defaulting to the first SSL config as determined by alphabetical filename order.

This means that the health check on Azure passes for whichever config is first in the list and fails with a certificate mismatch error for all the others.

When accessing these urls of the probems via browser, these SSL configurations all work correctly.

Without going into configs etc, my question is this: What could be the possible reason that requests from a probe do not resolve correctly (fails to match 'virtualhost'), yet it's fine in my browser? I've added logging to check the $host name is correct, so that's not the issue. I assume something similar happened with Apache, which could point to something system level? I don't really know how to diagnose this further - I am not finding similar issues on Google. Any help appreciated.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.