Does Plesk Support Shared SSL

[xerex]

Can someone tell me if Plesk 7 support shared SSL, if so how do I set this up.

 

[dragon2611]

i dunno i'm not sure if thats possible i had to use a seaprate ip when i setup ssl for a client.

 

[paddy@]

Aculy this is not a Plesk issue. The problem is with HTTPS. It simple doesn't support shared-ip hosting.

 

[xerex]

How come alot of hosting providers can offer shared SSL.

 

[paddy@]

Originally posted by xerex
How come alot of hosting providers can offer shared SSL.

They cant. Simple as that.
You have to distinglish the SSL sites in one of two ways. Different tcp PORT or different IP. That is the only ways to do it.
You can not have different SSL certs on the same IP/PORT.

 

[xerex]

Well why couldn't you buy an SSL cert. for one IP and setup multiple clients on that same IP, and well'a shared SSL

 

[paddy@]

Becouse the certificate is locked to a single domain - or wildcard domain. Dunno if PSA support wildcards tho.

Read this - it explains it all very good
Simplified SSL - About Secure Sockets Layer and HTTPS

 

[PaulC]

Shared SSL is normally some space and a certificate which you share with other clients. It would normally be hosted under a URL such as

https://ssl.yourhost.com/~username

You would have a username/password to FTP up there.

 

[onaweb]

I'm not sure how to do this with Plesk and W2K3. I';m wondering the same thing. I am doing this on my linux machine with cpanel but would like to offer this service for my windows machine as well. I have one cert for the main domain on the server and everyone's secure url is https://ssldomain.com/~username/ This works great.

 

[DomineauX]

Shared SSl is a REAL solution. All it takes is a valid SSL on an IP based site, and the ability to access the content of other domains on the server through a "preview URL" such as:

https://secure.hostingcompany.com/~username OR
https://secure.hostingcompany.com/~domainname.com

I have yet to see a Windows control panel allow this, but it is sorely missed when EVERY Unix/Linux control panel system allows this (as far as I have seen).

 

[AbsolutelyFreeW]

you may achieve this with plesk if you set a directory under the secure domain to their accounts space from the IIS.

 

[DomineauX]

You would be my hero if you could provide detailed instructions for this...and probably hero to a lot of others as well as Shared SSL is asked for a lot on these forums without ever being answered!

 

[AbsolutelyFreeW]

ok, becoming hero sounds nice so I do this for you but... no reliability taken. do it at your own risk:

1. From plesk make a subdomain. In my example secure.finexe.com
2. Goto IIS/websites/the subdomain/properties/directory security/server communications/server certificate and assign a certificate
3.you can also push directory security/server communications/edit and click require secure channel (this will redirect http traffic to error page)
4. make a page that redirects to https://secure.finexe.com. put it in the errordocs directory of your domain (finexe.com) The permissions are all wrong, you need to set the permissions from the server for your ftp user to be able to put things in the errordocs directory
5. Goto IIS/websites/the subdomain/properties/custom errors you put the 403;4 page to your new redirecting page

now all traffic for http://secure.finexe.com will go to the https port as well

ok the plesk ip is still available for ssl, it is not aware of what you've done. anyone can still enable ssl for their domain, and you dont want that. be aware what I desscribe here will take down your domain a little while. go and enable ssl in your plesk. Since there is already an ssl configured fo that ip IIS will complain, it will shutdown your domain. Go to IIS/websites/finexe.com (in my case) and enable it again.

ok now you want to split the https to other domains:

I. first we need to know the iusr pass for that domain. well, we don't know that, it isn't anywhere in the psa database? so we need to reset it. Go to my comuter/manage/localusers and reset the password for that user. rightclick the iusr_domainname and chooser set password

II. Goto IIS/websites/domain.com/properties/directory security/authentication and access control, and change the password, click apply and ok.

III. goto your secure domain in IIS e.g. IIS/websites/secure.finexe.com, right click and choose new/virtual directory. Choose the httpdocs directory for the domain you want to have shared ssl

IV. right click the new cirtual directory/properties/directory security/authentication and access control. Se the anonymous user to iusr_domainname and password you had changed to. apply and ok.

your new shared ssl:

http://secure.yourdomain.com/virtualdirectoryname

this will mirror all the domain as secuer.. alternatively you can make a webuser maybe to have both ssl and non-ssl in two different directories.

 

[jahsh420]

Has anybody been able to get this setup? We are having problems getting shared SSL for any domains following these instructions. Any help would be greatly appreciated.