The website cannot be started, another website can use the same port

Trying to set up a default website in IIS. When I try to start a website, I get the error message: "the website cannot be started and another site may use the same port."

I do not see any other bindings on port 80 in IIS. Is there any way to determine what else the port can use on the machine?

thanks

+9
source share
6 answers

Repeat this problem when I created a new website on port 80. Of course, the default website instance is also on port 80 and is in conflict. I decided that I solved it by going to ā€œEdit Bindingsā€ and changing the ā€œDefault Web Siteā€ port to 81 and leaving my new site to 80. I still could not start my new site. I had to delete and re-create my new website, after which I could start it. Looks like he still thought the ā€œDefault Web Siteā€ was at 80, although this is not the case. Even iisreset , recycling my new application pool and website didn't work. Perhaps if I restarted the site / application pool on the "Default Website", it might work as well, but I didn’t try it - I just deleted / re-created my new site. But that was enough to break through the "Default Website" while holding that port!

+10
source

I also got this error, but it wasn’t due to several sites (my IIS installation had only one site with one binding).

Running netstat -ano nothing while listening on port 8624 .

The problem was that the URL reservation was generated earlier for another web server. I was able to query the ACLs of URLs using the following command in PowerShell as administrator:

 netsh http show urlacl 

To remove it, enter the following (replace the last argument with the reserved URL from the show urlacl request):

 netsh http delete urlacl http://*:8624/ 
+5
source

or, more specifically, go to cmd and type:

netstat -aon | find ": 80"

+3
source

Go to Cmd, then type netstat -a Find the local address or local port at 80 or http

+1
source

I had the same problem. It is established that I need to bind my application in https mode, a certificate is installed on my computer, which by default is bound to port 443 when binding.

0
source

You must set the hostname on FTP sites, even fictitious ones. Than you should use this notation login name hostname | Username

Take a look at this: https://forums.iis.net/t/1196572.aspx

0
source

All Articles