Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I already have an SSL binding created for one of my websites in IIS 7.5.

Now I'm adding another website which listens on the same IP and port (443) but uses a different host header.

When I try to assign the binding using this powershell command:

New-WebBinding -Name $siteName -IP "*" -Port 443 -Protocol https -HostHeader $hostHeader 


New-ItemProperty $sitePath -name bindings -value @{protocol="https";bindingInformation=":443:"+$hostHeader}

I get the following error in Powershell.

SSL binding for end point already exists.
    + CategoryInfo          : InvalidData: (:) [New-Item], ProviderException
    + FullyQualifiedErrorId : SSL binding for end point already ex

How can I get rid of this error?

share|improve this question

You get rid of the error by making a more specific binding. You currently have an SSL binding, on another website, bound to all IP addresses.

IIS 7.5 does not support SNI, so this is your only option. Without SNI you cannot have host name headers for SSL; you need one IP address per certificate.

share|improve this answer Would this work? – Ryan Ries Aug 27 '13 at 22:40
Hmm, that's an interesting way of doing it. Yes and no. It still uses the same certificate on multiple sites, with SAN's on the certificate that it can just service the default certificate without thinking about it. I was not aware of this - perhaps this is what the op is trying to do... – Mark Henderson Aug 27 '13 at 23:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.