Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

Tags:

asp.net

iis

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

like image 576
dean Avatar asked Jul 18 '15 02:07

dean


People also ask

Why can't I access another site on the same port?

Another Web site may be using the same port. In IIS there are duplicate host headers. In the Plesk Control Panel. You may have had an issue deleting domain aliases.

Can another website use the same port as IIS?

Another website may using the same port. I've added the bindings to the IIS default site (for the port number 9680-HTTP & 9643-HTTPS). Whenever I go to click on the start button it could not start and run into an error mentioned in the title above.

What does “this web site cannot be started” mean?

Error: 'This Web site cannot be started. Another Web site may be using the same port.' – GFI Archiver Support Error: 'This Web site cannot be started. Another Web site may be using the same port.' This article describes the issue and its resolution when you are unable to access the GFI Archiver web interface.

Why can't I start a web site in IIS 6/7/8?

Another Web Site May Be Using the Same Port When attempting to start web site in IIS 6/7/8 manually you receive the error message stating This Web site cannot be started. Another Web site may be using the same port. In IIS there are duplicate host headers. In the Plesk Control Panel.


Video Answer


1 Answers

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!

like image 176
vapcguy Avatar answered Sep 23 '22 00:09

vapcguy