Quantcast
Channel: Azure Virtual Machines forum
Viewing all articles
Browse latest Browse all 12545

Load-balanced endpoint using HTTP probe on port 443 not working

$
0
0

I have a cloud service consisting of 2 VMs in an availability set, with an HTTP (80) load-balanced endpoint and an HTTPS (443) load balanced endpoint. Using the default probe type of TCP, it works fine. But when I switch the probe type to an HTTP probe and specify the probe path, only the port 80 gets probed, the port 443 probe does not work.

I configured the port 80 probe to use a path of /status.aspx, and the port 443 probe to use a probe path of /status2.aspx. I have both http and https binding on the Default Website in IIS on both VMs.

In the IIS logs, I can see the probe of /status.aspx on port 80 every 15 seconds:

2015-09-01 00:51:03 10.96.84.21 GET /status.aspx - 80 - 10.96.84.10 Load+Balancer+Agent - 200 0 0 15

2015-09-01 00:51:18 10.96.84.21 GET /status.aspx - 80 - 10.96.84.10 Load+Balancer+Agent - 200 0 0 17

But I do not see any probes to /status2.aspx - 443.

What is going on? I have removed the endpoints from both VMs, shut both down, re-added them, nothing. It seems like the HTTP probe can only use port 80. I've even added an ACL on the https endpoint of Allow 0.0.0.0/0 - no difference.

Thanks,

Paul


Viewing all articles
Browse latest Browse all 12545

Trending Articles