Unable to open WebDeploy port (8172) on Azure

Question

I'm unable to open a webdeploy port (8172) on my Azure machine.

I added an endpoint on Azure:

Added rules to the Firewall:

Tried even disable the firewall...

No success.

What else can I check?

The problem started from some message about certificate. I am not sure it linked to the problem but I am looking for the problem for two days and have no idea what else I can do...

Thank you.

Answer 1

Seems that this is a Microsoft's bug: https://social.msdn.microsoft.com/Forums/en-US/fc51b3fa-72c1-4e3c-a942-7da26acecd0d/endpoints-with-same-publicprivate-port-error?forum=WAVirtualMachinesforWindows

Answer 2

When you set up endpoints on a Windows virtual machine by using the classic deployment model. You could change the private port to 8172 for webdeploy. It seems that the private port is used by the virtual machine to listen for incoming traffic:

The public port is used by the Azure load balancer to listen for incoming traffic to the virtual machine from the internet. The private port is used by the virtual machine to listen for incoming traffic, typically destined to an application or service running on the virtual machine.

Update

After chatting with you, now you are facing the issue that you cannot change the public and private port to the same due to the floating IP address is enabled. I found there is a note that changing floating IP status takes effect until you save it in the UI. You can first create a test rule like public port 8001, a different private port 8000 because of the current floating IP address is really enabled, and select the floating IP address is disabled, then save it. Now the disabled floating IP address takes effect now. Then you can add the new rule for public and private port 8172. Delete the test rule.

Ref: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/classic/setup-endpoints