• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

SSL Shared Hosting

J

joshabts

Guest
I am having some trouble setting up shared hosting and SSL on Plesk 8.1.

I am trying to get it so that when users have a hosting account they all share the same SSL certificate. Obviously when they visit their site securely, it will pop up saying their is a domain mismatch but that isn't a problem. So far the only thing i have been able to find is enabling the shared ssl but I want users to be able to go to https://www.theirdomain.com not https://www.mydomain.com/theirdomain

The only other solution I found to this was putting each on its own IP which again destroys the purpose of shared hosting.

Has anyone done this and how would you configure it?

Thanks,
Joshua Abts
 
You cannot use SSL on sites with the same IP address and port (443 by default). It is known restriction.

We scheduled feature "Allow to manage ports for SSL for domains on the same IP" for Q4'07
 
The next problem I am having, is I put the domains on separate exclusive IP addresses, however now when a client adds a SSL certificate to their domain, it shows up in the other clients domains as well. How can I prevent this?

Maybe my problem with understanding is do I need to attach their certificate to their IP or just have them upload it in their account? I am confused by the IPs each having their own Certificate when you create them.

Thanks,
Josh
 
Seems you added certificates into Server-wide certificate repository which is avaiable for all domains. You should add certificate into each domain certificate repository.
 
We've solved that situation isuing an * certficate. But it's only useful if all your domains belongs to the same subdomain....

i.e.

Certificate: *.domain.com

it's correct for a.domain.com, b.domain.com, etc...
 
Back
Top