Unable to open WebDeploy port (8172) on Azure
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.
azure port firewall webdeploy azure-cloud-services edited Nov 21 at 20:46
Nancy Xiong
2,380116
asked Nov 21 at 6:54
Igor
7719
|
show 4 more comments
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.
azure port firewall webdeploy azure-cloud-services edited Nov 21 at 20:46
Nancy Xiong
2,380116
asked Nov 21 at 6:54
Igor
7719
1
Is the port listening for 0.0.0.0:port when you checknetstat -anboon the windows machine locally?
– Nancy Xiong
Nov 21 at 7:01
@NancyXiong-MSFT could you please explain what you mean? How can I know?
– Igor
Nov 21 at 7:03
Is this the answer to your question? prntscr.com/ll038y
– Igor
Nov 21 at 7:05
Why does it say 8173 in your screenshot? Shouldn't that be 8172 instead?
– evilSnobu
Nov 21 at 7:05
@evilSnobu it is the private port. The public (also on the screenshot) is 8172.
– Igor
Nov 21 at 7:06
|
show 4 more comments
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.
azure port firewall webdeploy azure-cloud-services edited Nov 21 at 20:46
Nancy Xiong
2,380116
asked Nov 21 at 6:54
Igor
7719
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.
azure port firewall webdeploy azure-cloud-services azure port firewall webdeploy azure-cloud-services edited Nov 21 at 20:46
Nancy Xiong
2,380116
asked Nov 21 at 6:54
Igor
7719
edited Nov 21 at 20:46
Nancy Xiong
2,380116
asked Nov 21 at 6:54
Igor
7719
edited Nov 21 at 20:46
Nancy Xiong
2,380116
edited Nov 21 at 20:46
Nancy Xiong
2,380116
edited Nov 21 at 20:46
Nancy Xiong
2,380116
2,380116
asked Nov 21 at 6:54
Igor
7719
asked Nov 21 at 6:54
Igor
7719
asked Nov 21 at 6:54
Igor
7719
7719
1
Is the port listening for 0.0.0.0:port when you checknetstat -anboon the windows machine locally?
– Nancy Xiong
Nov 21 at 7:01
@NancyXiong-MSFT could you please explain what you mean? How can I know?
– Igor
Nov 21 at 7:03
Is this the answer to your question? prntscr.com/ll038y
– Igor
Nov 21 at 7:05
Why does it say 8173 in your screenshot? Shouldn't that be 8172 instead?
– evilSnobu
Nov 21 at 7:05
@evilSnobu it is the private port. The public (also on the screenshot) is 8172.
– Igor
Nov 21 at 7:06
|
show 4 more comments
1
Is the port listening for 0.0.0.0:port when you checknetstat -anboon the windows machine locally?
– Nancy Xiong
Nov 21 at 7:01
@NancyXiong-MSFT could you please explain what you mean? How can I know?
– Igor
Nov 21 at 7:03
Is this the answer to your question? prntscr.com/ll038y
– Igor
Nov 21 at 7:05
Why does it say 8173 in your screenshot? Shouldn't that be 8172 instead?
– evilSnobu
Nov 21 at 7:05
@evilSnobu it is the private port. The public (also on the screenshot) is 8172.
– Igor
Nov 21 at 7:06
1
1
Is the port listening for 0.0.0.0:port when you check
netstat -anboon the windows machine locally?– Nancy Xiong
Nov 21 at 7:01
Is the port listening for 0.0.0.0:port when you check
netstat -anboon the windows machine locally?– Nancy Xiong
Nov 21 at 7:01
@NancyXiong-MSFT could you please explain what you mean? How can I know?
– Igor
Nov 21 at 7:03
@NancyXiong-MSFT could you please explain what you mean? How can I know?
– Igor
Nov 21 at 7:03
Is this the answer to your question? prntscr.com/ll038y
– Igor
Nov 21 at 7:05
Is this the answer to your question? prntscr.com/ll038y
– Igor
Nov 21 at 7:05
Why does it say 8173 in your screenshot? Shouldn't that be 8172 instead?
– evilSnobu
Nov 21 at 7:05
Why does it say 8173 in your screenshot? Shouldn't that be 8172 instead?
– evilSnobu
Nov 21 at 7:05
@evilSnobu it is the private port. The public (also on the screenshot) is 8172.
– Igor
Nov 21 at 7:06
@evilSnobu it is the private port. The public (also on the screenshot) is 8172.
– Igor
Nov 21 at 7:06
|
show 4 more comments
2 Answers
2
active
oldest
votes
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://docs.microsoft.com/en-us/azure/virtual-machines/windows/classic/setup-endpoints
answered Nov 21 at 7:29
Nancy Xiong
2,380116
Changed but still without success. But seems that you are right and I should continue exploring in this direction...
– Igor
Nov 21 at 8:02
Can you telnet 8172 with the public IP of Azure VM when you access the VM outside of Azure VM?
– Nancy Xiong
Nov 21 at 8:20
This is the problem, I can't telnet "Could not open connection to the host, on port 8172: Connect failed"
– Igor
Nov 21 at 8:21
Can you check the firewall or other restrcition on the local machine?
– Nancy Xiong
Nov 21 at 8:22
Firewall is open: i.stack.imgur.com/wm6gZ.png
– Igor
Nov 21 at 8:24
|
show 7 more comments
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
answered Nov 22 at 14:59
Igor
7719
Seem that it's bug, the first time, you can add the same port, then the second time you can not, I have tried it many times. You can regard the floating IP as enabled even it shows the disabled, then you can add another rule with the different port and select the disabled floating IP, save it. And try to add the same port, don't click the floating IP tab, then save it. It works for me.
– Nancy Xiong
Nov 22 at 15:26
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53406693%2funable-to-open-webdeploy-port-8172-on-azure%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
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://docs.microsoft.com/en-us/azure/virtual-machines/windows/classic/setup-endpoints
answered Nov 21 at 7:29
Nancy Xiong
2,380116
Changed but still without success. But seems that you are right and I should continue exploring in this direction...
– Igor
Nov 21 at 8:02
Can you telnet 8172 with the public IP of Azure VM when you access the VM outside of Azure VM?
– Nancy Xiong
Nov 21 at 8:20
This is the problem, I can't telnet "Could not open connection to the host, on port 8172: Connect failed"
– Igor
Nov 21 at 8:21
Can you check the firewall or other restrcition on the local machine?
– Nancy Xiong
Nov 21 at 8:22
Firewall is open: i.stack.imgur.com/wm6gZ.png
– Igor
Nov 21 at 8:24
|
show 7 more comments
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://docs.microsoft.com/en-us/azure/virtual-machines/windows/classic/setup-endpoints
answered Nov 21 at 7:29
Nancy Xiong
2,380116
Changed but still without success. But seems that you are right and I should continue exploring in this direction...
– Igor
Nov 21 at 8:02
Can you telnet 8172 with the public IP of Azure VM when you access the VM outside of Azure VM?
– Nancy Xiong
Nov 21 at 8:20
This is the problem, I can't telnet "Could not open connection to the host, on port 8172: Connect failed"
– Igor
Nov 21 at 8:21
Can you check the firewall or other restrcition on the local machine?
– Nancy Xiong
Nov 21 at 8:22
Firewall is open: i.stack.imgur.com/wm6gZ.png
– Igor
Nov 21 at 8:24
|
show 7 more comments
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://docs.microsoft.com/en-us/azure/virtual-machines/windows/classic/setup-endpoints
answered Nov 21 at 7:29
Nancy Xiong
2,380116
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://docs.microsoft.com/en-us/azure/virtual-machines/windows/classic/setup-endpoints
answered Nov 21 at 7:29
Nancy Xiong
2,380116
edited Nov 22 at 5:02
answered Nov 21 at 7:29
Nancy Xiong
2,380116
answered Nov 21 at 7:29
Nancy Xiong
2,380116
answered Nov 21 at 7:29
Nancy Xiong
2,380116
2,380116
Changed but still without success. But seems that you are right and I should continue exploring in this direction...
– Igor
Nov 21 at 8:02
Can you telnet 8172 with the public IP of Azure VM when you access the VM outside of Azure VM?
– Nancy Xiong
Nov 21 at 8:20
This is the problem, I can't telnet "Could not open connection to the host, on port 8172: Connect failed"
– Igor
Nov 21 at 8:21
Can you check the firewall or other restrcition on the local machine?
– Nancy Xiong
Nov 21 at 8:22
Firewall is open: i.stack.imgur.com/wm6gZ.png
– Igor
Nov 21 at 8:24
|
show 7 more comments
Changed but still without success. But seems that you are right and I should continue exploring in this direction...
– Igor
Nov 21 at 8:02
Can you telnet 8172 with the public IP of Azure VM when you access the VM outside of Azure VM?
– Nancy Xiong
Nov 21 at 8:20
This is the problem, I can't telnet "Could not open connection to the host, on port 8172: Connect failed"
– Igor
Nov 21 at 8:21
Can you check the firewall or other restrcition on the local machine?
– Nancy Xiong
Nov 21 at 8:22
Firewall is open: i.stack.imgur.com/wm6gZ.png
– Igor
Nov 21 at 8:24
Changed but still without success. But seems that you are right and I should continue exploring in this direction...
– Igor
Nov 21 at 8:02
Changed but still without success. But seems that you are right and I should continue exploring in this direction...
– Igor
Nov 21 at 8:02
Can you telnet 8172 with the public IP of Azure VM when you access the VM outside of Azure VM?
– Nancy Xiong
Nov 21 at 8:20
Can you telnet 8172 with the public IP of Azure VM when you access the VM outside of Azure VM?
– Nancy Xiong
Nov 21 at 8:20
This is the problem, I can't telnet "Could not open connection to the host, on port 8172: Connect failed"
– Igor
Nov 21 at 8:21
This is the problem, I can't telnet "Could not open connection to the host, on port 8172: Connect failed"
– Igor
Nov 21 at 8:21
Can you check the firewall or other restrcition on the local machine?
– Nancy Xiong
Nov 21 at 8:22
Can you check the firewall or other restrcition on the local machine?
– Nancy Xiong
Nov 21 at 8:22
Firewall is open: i.stack.imgur.com/wm6gZ.png
– Igor
Nov 21 at 8:24
Firewall is open: i.stack.imgur.com/wm6gZ.png
– Igor
Nov 21 at 8:24
|
show 7 more comments
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
answered Nov 22 at 14:59
Igor
7719
Seem that it's bug, the first time, you can add the same port, then the second time you can not, I have tried it many times. You can regard the floating IP as enabled even it shows the disabled, then you can add another rule with the different port and select the disabled floating IP, save it. And try to add the same port, don't click the floating IP tab, then save it. It works for me.
– Nancy Xiong
Nov 22 at 15:26
add a comment |
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
answered Nov 22 at 14:59
Igor
7719
Seem that it's bug, the first time, you can add the same port, then the second time you can not, I have tried it many times. You can regard the floating IP as enabled even it shows the disabled, then you can add another rule with the different port and select the disabled floating IP, save it. And try to add the same port, don't click the floating IP tab, then save it. It works for me.
– Nancy Xiong
Nov 22 at 15:26
add a comment |
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
answered Nov 22 at 14:59
Igor
7719
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
answered Nov 22 at 14:59
Igor
7719
answered Nov 22 at 14:59
Igor
7719
answered Nov 22 at 14:59
Igor
7719
answered Nov 22 at 14:59
Igor
7719
7719
Seem that it's bug, the first time, you can add the same port, then the second time you can not, I have tried it many times. You can regard the floating IP as enabled even it shows the disabled, then you can add another rule with the different port and select the disabled floating IP, save it. And try to add the same port, don't click the floating IP tab, then save it. It works for me.
– Nancy Xiong
Nov 22 at 15:26
add a comment |
Seem that it's bug, the first time, you can add the same port, then the second time you can not, I have tried it many times. You can regard the floating IP as enabled even it shows the disabled, then you can add another rule with the different port and select the disabled floating IP, save it. And try to add the same port, don't click the floating IP tab, then save it. It works for me.
– Nancy Xiong
Nov 22 at 15:26
Seem that it's bug, the first time, you can add the same port, then the second time you can not, I have tried it many times. You can regard the floating IP as enabled even it shows the disabled, then you can add another rule with the different port and select the disabled floating IP, save it. And try to add the same port, don't click the floating IP tab, then save it. It works for me.
– Nancy Xiong
Nov 22 at 15:26
Seem that it's bug, the first time, you can add the same port, then the second time you can not, I have tried it many times. You can regard the floating IP as enabled even it shows the disabled, then you can add another rule with the different port and select the disabled floating IP, save it. And try to add the same port, don't click the floating IP tab, then save it. It works for me.
– Nancy Xiong
Nov 22 at 15:26
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53406693%2funable-to-open-webdeploy-port-8172-on-azure%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Is the port listening for 0.0.0.0:port when you check
netstat -anboon the windows machine locally?– Nancy Xiong
Nov 21 at 7:01
@NancyXiong-MSFT could you please explain what you mean? How can I know?
– Igor
Nov 21 at 7:03
Is this the answer to your question? prntscr.com/ll038y
– Igor
Nov 21 at 7:05
Why does it say 8173 in your screenshot? Shouldn't that be 8172 instead?
– evilSnobu
Nov 21 at 7:05
@evilSnobu it is the private port. The public (also on the screenshot) is 8172.
– Igor
Nov 21 at 7:06