I have a problem similar (but not the same) as mine:
Azure web role - multiple ssl certificates pointing to one endpoint
My azure package contains several sites. Some of these sites are on the abc domain, while others are on the def domain. I need to protect both domains with SSL, but I canβt figure out how (if possible) to do this.
Here is an example of my configuration:
<Sites> <Site name="sub1.abc" physicalDirectory="***"> <Bindings> <Binding name="HttpIn" endpointName="HttpIn" hostHeader="sub1-staging.abc.com" /> <Binding name="HttpsInABC" endpointName="HttpsInABC" hostHeader="sub1.abc.com" /> </Bindings> </Site> <Site name="sub1.def" physicalDirectory="***"> <Bindings> <Binding name="HttpIn" endpointName="HttpIn" hostHeader="sub1-staging.def.com" /> <Binding name="HttpsInDEF" endpointName="HttpsInDEF" hostHeader="sub1.def.com" /> </Bindings> </Site> </Sites> <Endpoints> <InputEndpoint name="HttpIn" protocol="http" port="80" /> <InputEndpoint name="HttpsInABC" protocol="https" port="443" certificate="abc" /> <InputEndpoint name="HttpsInDEF" protocol="https" port="443" certificate="def" /> </Endpoints> <Certificates> <Certificate name="abc" storeLocation="LocalMachine" storeName="My" /> <Certificate name="def" storeLocation="LocalMachine" storeName="My" /> </Certificates>
This configuration gives me the following error:
The same local port "443" is assigned to the HttpsInABC and HttpsInDEF endpoints as ***.
Any suggestions on how I can get around this without having to post them separately?
Based on @JoelDSouza's answer:
Various ports will be used for you.
What are the implications of SSL for ports 444/445/446, etc. on windows azure?
Paul fleming
source share