Multi-Domain SSL Certificate

[Oizopower]

Hello,

I am about to buy a multi-domain SSL certificate, But i am wondering if somebody has some experience with adding it into plesk.
We can create a multidomain CSR, but i'm not sure how to add this into Plesk 11 and get it working.

SNI is supported and working on the server, we have tested it with several single SSL certificates on the same IP.
But now we want a Multi-Domain EV certificate and i really don't know where to start. can someone point me in the right direction or tell me how this works?

 

[yabado]

Same here, bump.

 

[UFHH01]

Hi there,

I don't see any errors, issues, or even problems. Just create a "certificate request" for one of your domain, as usual and use this request, when you buy your "multi-domain SSL certificate". You then might add the needed crt's over the Plesk Control Panel as usual and you can even choose to install the certificate as a standard for one of your server IPs ( with a different name, because they are unique in Plesk ).

If you experience any issues, please include as well WHAT you did and include as well logfiles and depending configuration files, so that investigations will be easier. It's always a plus, to include your OS and Plesk version as well.

 

[yabado]

OK, using PP12 on Cloudlinux

So if I have a multi-domain wildcard SSL certificate for domains domain1.com, domain2.com and domain3.com

The default main certificate for the entire panel is *.domain1.com

I have another site I own, it is domain2.com

I go into domain2.com hosting settings and check to use SSL, then choose the same certificate as i used for domain1.com

Repeat the above steps for domain3.com

All 3 sites use same IP, all three use same ssl certifictae.

Only domain 1 works. The other 2 just load the default plesk panel certificate..

What part am I doing wrong?

 

[UFHH01]

Hi yabado,

please check as well the IP - based certificate setting, which is in your case the default Plesk certificate.
You can as well install the very same certicate WITH A DIFFERENT NAME on each domain, instead of choosing the IP-based usage, in order to avoid issues. You don't necessarily need a CSR to create the CRTs - just go step-by-step while you are at "Hosting > Configuration & Administration > Web Space > WebSite Configuration > SSL"

Please check as well different articles in the Parallels knowledge base ( http://kb.odin.com/ ), which describe as well possible issues.

Please check your certificates with a "modern" browser, because some old browsers don't support SNI. The best way is to check the certificate at "https://www.ssllabs.com/ssltest/".


Please make sure that your configuration files are rebuild after you changed the certificate, if you are unsure about how to do that, just use the command:

/usr/local/psa/admin/sbin/httpdmng --reconfigure-all​

to rebuild all config - files.

Compare your configuration files after your rebuilds, to make sure, that the changes for the certificates are done as expected.

 

[yabado]

Hi yabado,
please check as well the IP - based certificate setting, which is in your case the default Plesk certificate.

What are you referring to here? The certificate works as it should.

You can as well install the very same certicate WITH A DIFFERENT NAME on each domain, instead of choosing the IP-based usage, in order to avoid issues. You don't necessarily need a CSR to create the CRTs - just go step-by-step while you are at "Hosting > Configuration & Administration > Web Space > WebSite Configuration > SSL"

I am using Plesk Panel 12, that navigation path does not exist?

Please check your certificates with a "modern" browser, because some old browsers don't support SNI. The best way is to check the certificate at "https://www.ssllabs.com/ssltest/".

I get an A- on the domain that actually uses the certificate.

Please make sure that your configuration files are rebuild after you changed the certificate, if you are unsure about how to do that, just use the command:

/usr/local/psa/admin/sbin/httpdmng --reconfigure-all​

to rebuild all config - files.

Compare your configuration files after your rebuilds, to make sure, that the changes for the certificates are done as expected.

Looks like running this command fixes things so domain2 and domain3 can now utilize the primary IP based SSL certificate.

All good!