IIS 7 and Above
Removing HTTPS binding affects other sites?
Last post May 13, 2013 11:28 AM by foxontherock
Jun 05, 2008 11:31 AM|takeos|LINK
Everything worked fine, until I recently added a new site, which exhibited two problems:
The certificate associated with this binding is also assigned to another site's binding. Deleting this binding will cause the HTTPS binding of the other site to be unusable. Do you still want to continue?
Yes No Cancel
I don't know what's wrong with this new site. Apparently the usual setup steps were followed, but now I can't even delete it out of fear of losing the wildcart certificate that is also used by other sites, and I am a bit at loss.
Jun 05, 2008 11:43 AM|anilr|LINK
There are 2 parts of an "SSL binding" - the host:ip:port information that is in applicationhost.config which is unique to each site (eg: webdav1.example.com:443:ip) and the mappings of an ip:port combination to a server certificate in http.sys configuration
which in this case is shared across all your sites using the wildcard certificate - removing the bindings in the UI will remove both those things which will of course make your other sites non-functional - you need to remove just the binding in applicationhost.config
using other means like appcmd/editing in notepad etc.
Jun 06, 2008 05:40 AM|takeos|LINK
Thank you, manual editing of the .config file did it. It allowed me to remove and readd the site, and the other problem is solved as well. Maybe this should be filed as a bug in IIS manager though?
Mar 10, 2010 07:54 AM|cemag|LINK
I have the same problem I can't fix.
So I have a SBS 2008 which after installing the certificate does not allow to start the "default" website because another site (SBS Web Application) is using the same port.
I understood that a manual editing of the config file will solve the problem but I am not sure what I must edit to get it working.
Can you be more specific for a "novice" like me?
Mar 11, 2010 01:23 AM|CarlosAg|LINK
The problem that you are facing does not seem to be the exact same problem. The problem mentioned before was two sites using SSL and Wildcard certificates which when deleted can cause problems in between each other.
If I'm reading correctly your mail it sounds like you just have a port# conflict. You can only have one site with the exact same bindings which it looks like you are having that problem. You should open the IIS Manager (inetmgr.exe) and expand the Tree to
get to the Sites node, see the Bindings column. Probably two sites have the same *:80 binding. You can only start one of them so you'll need to stop the other. If you want to have both running you could either edit the Bindings (click Bindings...) and change
the port # of one of them or use a host name.
Mar 30, 2010 11:45 AMemail@example.com|LINK
SBS Web Applications
Default Web Site
Jul 14, 2010 02:30 PM|foxontherock|LINK
Jul 14, 2010 04:09 PM|CarlosAg|LINK
There is no fix available, correct me if I'm wrong but this should only happen when you delete a binding to a site and my recommendation would be to use maybe AppCmd.exe for that. Or do you see it in other scenarios as well?
Jul 14, 2010 09:49 PM|foxontherock|LINK
Jul 15, 2010 03:43 PM|foxontherock|LINK
Jul 15, 2010 04:43 PM|CarlosAg|LINK
Indeed Microsoft.Web.Administration will have the same effect since IIS Manager is the API that it uses to do those changes. You will need to use either AHADMIN or AppCmd, none of those will have that problem.
May 13, 2013 10:48 AM|nZeus|LINK
Am I right that Microsoft doesn't want to fix this issue?
It's definetly a problem of the IIS Manager.
Notepad/AHADMIN/AppCmd is not a solution, it's a workaround. It's too risky to edit .config file manually.
May 13, 2013 11:28 AM|foxontherock|LINK
There is another issue we found with iis manager + ssl...
We are using a Wildcard certificate from GoDaddy, and we CAN'T add any https binding in the console using that certificat, like if it is invalid!
Seems like the wildcard godaddy ssl certificate contains something that iis management console doesn't like.
But, we CAN in the notepad applicationhost.config file manually!
So now, we must use notepad to remove AND add ssl binding!
Please MS fix these SSL / Wildcard / Binding issues from the IIS management console. (Win 2008 R2)