Differnt SSL certificate for Multi websites

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
5/11/2010 6:51:39 AM
Gravatar
Total Posts 17

Differnt SSL certificate for Multi websites

Dear All,

We want to know if we can implement multiple certificate on one domain.

For example If we have two multi website running on same domain, can we have two different SSL Certitificate implemeneted seperately for each sub website:-

www.domainname.com/1/Default.aspx
www.domainname.com/2/Default.aspx


Regards,


5/11/2010 1:35:22 PM
Gravatar
Total Posts 18439

Re: Differnt SSL certificate for Multi websites

Hi,

For folder based web sites there is only 1 domain and it can only have 1 SSL certificate because SSL certificates are tied to a specific domain. So you can use the same SSL certificate for all sites in a multi sites installation based on folders. 

When you have multiple sites based on host names, then you run into a problem because only 1 SSL certificate can bind to a particular ip address on port 443 (the SSL port). Therefore you have to make a separate IIS web site in this case and use a different ip address, however it can still point to the same physical installation folder as the first site.

Hope it helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.