• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

SSL Cert Question: Domain Based vs Server Based

X

XenoDave

Guest
What is there difference, or more importantly the point to Site/Domain based Certificates?
All SSL tickets are assigned by IP address, via the Administrator's Repository.
So Site Level or Site Based Certificates are never used. So why are they there?

Or is there some way to have a set of sites on one IP using one Cert, except for one site I designate using a special Site based Cert?
 
We spent a lot of time banging on this one. The upshot of it was always to use the Server wide certs, not the domain/site specific ones. You set up the server cert., install it by click the Setup checkbox and then adding it an IP.

We have most of our domains on a single ip but do have a cert for that ip for access to Plesk for our clients.
 
Here is the problem.

I have a customer that needs SSL, let's call them customer1.com

But all my other customers are on the same IP.

So anytime they goto https://... they get customer1.com

I guess what you are saying is that customer domain SSL isn't actually an option?
 
I have a shared ip say 100.1.1.1 with several domains on it, including domain1.com and domain2.com. I have a cert for domain1.com installed in the server certificate area. I have that cert applied to that shared ip in the server ip settings. When I go to https://www.domain1.com everything works like you'd expect it too. When I go to https://www.domain2.com I get a warning saying there's a cert mis-match but I can click ok anyway to get through to https://www.domain2.com -- it doesn't redirect to https://www.domain1.com
 
Back
Top