• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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