Reputation: 355

website cannot be started another website may be using the same port

Trying to set up a default website in IIS. When trying to start the website I get the error message: "website cannot be started another website may be using the same port."

I don't see any other bindings on port 80 in IIS. Is there a way to determine what else might be using the port on the machine?

Thanks

Upvotes: 18

Answers (8)

atiq 1000

Reputation: 1

to check which web is using port netstat -ano

to check url name - netstat -aon | find ":80"

using url name delete binding with port netsh http delete urlacl http://*:80/

check again

restart server if impact is not visible.

Upvotes: -1

Jerry

Reputation: 21

I had the same issue. In my case there was only one site. Somehow the install of a certificate created a second https binding?! Deleting one of the bindings solved the problem.

Upvotes: 2

domadams

Reputation: 31

After reboot of a system the "Windows Sync Share" service was occupying port 80 and 443. This service needed to be stopped allowing the default website on 80 to start. Changing the "Windows Sync Share" service from "automatic" to "disabled" prevented this from reoccurring.

Upvotes: 3

vapcguy

Reputation: 7537

Ran across an issue like this when I was setting up a new web site on port 80. Of course, the Default Web Site instance is also on port 80, and conflicts. I thought I solved this by going to "Edit Bindings" and changing the "Default Web Site's" port to 81 and leaving my new site on 80. I still could not start my new site.

I had to delete and re-create my new web site, then I could start it.

It's like it still thought "Default Web Site" was on 80, even though it wasn't. Even an iisreset, a recycle of my new site's app pool and web site all did not work. Maybe if I had restarted the site/app pool of the "Default Web Site", maybe that would've worked, too, but didn't try it - just deleted/re-created my new site. But that was enough to break through the "Default Web Site" keeping a hold of that port!

Upvotes: 19

John Rasch

Reputation: 63445

I also received this error, but it was not because of multiple sites (my installation of IIS only had a single site with a single binding).

Running netstat -ano showed nothing listening on port 8624.

The problem was that a URL Reservation was generated previously for a different web server. I was able to query the URL ACLs with the following command in PowerShell as administrator: