1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Shared SSL Cert

Discussion in 'Plesk for Linux - 8.x and Older' started by chrisl@, Sep 25, 2006.

  1. chrisl@

    chrisl@ Guest

    0
     
    Hello,

    I have a server that we used before purchasing Plesk that we had setup a shared SSL Cert so people could use it for SSL instead of purchasing a individual cert.

    Has anyone got a how to do this with Plesk for Linux? I am trying but not having much success. I am running into issues with the suexec and other minor things.

    Any ideas?

    -chrisl
     
  2. jwdick

    jwdick Guest

    0
     
  3. chrisl@

    chrisl@ Guest

    0
     
    This is an interesting aproach but not what I was thinking. It also has problems because the one peice of software I use (shopsite) has protected directories. My current setup is something like this:

    https://secure.mydomain.com/<useraccount1>
    https://secure.mydomain.com/<useraccount2>
    https://secure.mydomain.com/<useraccount3>
    https://secure.mydomain.com/<useraccount4>
    etc.....

    Then I create an Alias line in the vhost.conf under the secure domain to point to the users httpsdocs directory so they have ftp access to upload the files. This works really great on my old server but with Plesk when you try running scripts it does not. The scripts are run under suexec and since they are not owned by the secure.mydomain.com account they give a 500 error as expected.

    What I was hoping to do is keep the same shared SSL setup but either have suexec deffined by each alais or create a different Apache install for this web server. I was hoping to be able to do it within Plesk with custom vhost.conf file(s) but so far everything I have tried has failed. Has anyone done something like this? Anyone have any suggestions?
     
  4. webignite

    webignite Guest

    0
     
    2 domains -

    securedomain.com
    clientdomain.com

    in securedomain.com in /httpsdocs create a symlink to /vhosts/clientdomain.com/httpdocs and name it clientdomain.com

    chown client: pcacln

    Direct any ssl requests through https://securedomain.com/clientdomain

    Any time you need to ad another domain to the shared SSL, simply create the symlink in httpsdocs folder within securedomain.com.

    May be better/easier way, but I've had no trouble with it.
     
  5. chrisl@

    chrisl@ Guest

    0
     
    Okay I get what your doing but I am wondering if this works with cgi scripts. I am trying to get ShopSite installed and the scripts from the secure server are failing because of the suexec problems with file ownership. The files owned by the client and not the share ssl fail. Any suggestions are you having a problem?

    -chrisl
     
  6. webignite

    webignite Guest

    0
     
    Without seeing your permissions on such files/directories I'm unsure why you'd have ownership problems.

    The files in your SSL domain (meaning the symlinks) should be owned by your nonSSL domain.
     
Loading...