I host 7 dnn sites under one domain, and 1 site under a different domain.  Sites 1 through 7 are variious versions of dnn raaging up to dnn 4.5.5.  They are configured as https://domainname1/companyname1 through https://domainname1/companyname7.  The sites are used by social service agencies to collect and keep track of clients.  There is an ssl certificate installed for this site for domainname1 on the default ssl port in IIS.

The 8th site is http://www.domainname2.com and this site is a commercial and public site and I only need ot secure the shopping cart.  It has it's own ssl certifiace on an alternate port.  When I try to secure the shopping cart on this site, the browser throws an exception stating that the certificate is not for the domain.  As you probably guessed, DNN is trying to offer the ssl certificate on the default port, which is not the correct certififcate (looking at eh details of the ssl error it hsows the certificate for domainname1 instead of domainname2). 

If I switch site 8 to use the default ssl port then I can secure the shoopping cart, but the 400 users of domain1 sites get the certificate error as their sites are now offering the domainname2 certificate.

 Is there a hack that I could apply to DNN to allow it to recognize non-default ssl ports?

Is there a better way to set up the sites to make ssl and multiple dnn sites coexists in harmony?

Any help is appreciated.

john mott

Thanks for the response.  I just solved my problem last night.  Since we had already purchased two seperate certificates and we needed one of the certificates to acccurately identify the site as the client and not us, we ended up assigning a seperate ip address to the two domains.  Since our colocation provider offered us 13 ip addresses we had plenty to go around.  Each doamin has their own IP, both use ssl port 443, and everything is working great. 

This looks like the cleanest and simplest way to go, and it works very well.