25.3.14

The Certificate associated with this binding is also assigned to another site's binding.

I faced this problem twice, so I decide to write down some notes to help me and you in case we'll face this problem again (or for the first time).
When I assign the same certificate to two or more websites and after a while I decide to remove, IIS asks the following question:

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?


Well...I think not.

The consequence of this action is the stop of all others applications using that certificate, not quite good for a production environment. So what to do?

Edit C:\Windows\System32\inetsrv\config\applicationHost.config, search for your application name and manually delete the row with the https binding. 

 <binding protocol="https" bindingInformation<binding protocol="https" bindingInformation="*:443:" />"*:443:" />  

Save file and re-open IIS GUI: the binding should be disappeared.

An IIS bug? Maybe or maybe only Microsoft style ;)





7 comments:

  1. Anonymous31/7/15 22:47

    Thanks for posting the file location.

    ReplyDelete
  2. Anonymous17/8/15 17:00

    This helped me out, thanks!

    ReplyDelete
  3. Anonymous16/2/16 13:10

    DONT EDIT WITH NOTEPPAD++ , REGULAR NOTEPAD

    ReplyDelete
  4. For some reason Editing with Notepad++ does not 'apply' the change. I had to use the anonymous advice above and edit with plain Notepad. Only then did they binding disappear.

    ReplyDelete
  5. Anonymous26/4/23 16:46

    Notepad vs Notepad++ is the 32-bit vs 64-bit problem, where the operating system silently swaps folders on you. So you think you are editing a file under directory "System32", but unknown to you, actually you are editing a file under "SysWOW64". Try "SysNative" instead of "System32". This mess is part of a larger Microsoft insanity where they put 64-bit executables into the directory named "32", and 32-bit executables into the directory named "64".

    ReplyDelete
    Replies
    1. Anonymous26/4/23 18:20

      http://msdn.microsoft.com/en-us/library/aa384187%28VS.85%29.aspx

      Delete