3
I have to bind my IIS website to port 443. No other port is allowed in my case. In IIS Manager I've bound Default Web Site to port 443:
But when I try to start the website it fails with:
However netstat -anob
shows nothing to be listening on port 443. TCPView from SysInternals and Windows Resource Monitor both agree with netstat.
How can I find out what is listening on port 443 and stop it so I can run my website on 443?
I'm using IIS 8.5 on Windows Server 2012 R2.
Update on 30 Mar. 2016 It turns out that I could use a port other than 443 after all. So starting the website is no longer a problem for me. Sorry for wasting everyone's time; there was a communication error. But I'll leave this question open in case anyone else faces a similar problem. It might still be useful to know how to find out what's blocking IIS from starting on a particular port when netstat shows nothing is listening on that port.
1443 is for https – SeanClt – 2016-03-29T12:45:20.193
@SeanClt: I know that's true by convention but does that stop it being used for http? As I said, I have to use 443. – snark – 2016-03-29T13:59:29.133
try changing to https with 443 does it work? – SeanClt – 2016-03-29T14:00:06.227
IIS doesn't let me change it from http. In the
Edit Site Binding
dialog the value for Type - http - is greyed out and no other options are available. – snark – 2016-03-29T15:38:02.3301Why are you trying to use 443? Understand the reason you are attempting to run HTTP traffic on port 443 might assist in helping you solve this problem. – Ramhound – 2016-03-29T16:35:01.673
@Ramhound: You are right. It turns out there was a miscommunication error between the IT security guys and me. I was under the impression I could only use 443 but I was wrong! I'll edit the question to reflect this... – snark – 2016-03-30T14:24:53.410
@snark can you post your solution as an answer? – Burgi – 2016-03-31T12:18:13.263
@Burgi I don't have a solution because it turns out I didn't have the problem I thought I had! But I'm leaving the question open in case other people do have to use port 443. For future reference this link might help - https://helpdesk.stone-ware.com/portal/helpcenter/articles/port-443-80-not-available-on-windows-server (e.g.,
– snark – 2016-03-31T13:18:52.477netsh http show urlacl
).