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

SSL subdomains

Discussion in 'Plesk for Linux - 8.x and Older' started by Aristo, Aug 26, 2005.

  1. Aristo

    Aristo Guest

    0
     
    Hi,

    Can we access a subdomain using the SSL (HTTPS) address?

    like https://sub.domain.com
    and http://sub.domain.com

    I know that the root site have httpsdoc and httpdocs.

    I also tried the option: Use a single directory for housing SSL and non-SSL content

    for the root site, I restart apache and it still point to the httpsdocs

    So my 2 questions are:
    1. Can I use https for subdomain
    2. Why after checking the single directory for SSL and Non-SSL option it still goes to the httpsdocs folder.

    Thank you!
     
  2. hardweb

    hardweb Guest

    0
     
    1. You can not use https for subdomains.
    2. After you check the option to use httpdocs for SSL, try to execute in command line:

    /usr/local/psa/admin/bin/websrvmng -a
     
  3. poke

    poke Guest

    0
     
    Also, you can create the sub.domain.com as an actual domain, thus giving you the ability to have ssl over wildcard domains.

    :)
     
  4. diesof

    diesof Guest

    0
     
    After all what is the propper solution?
    The command line solution from hardweb - how it works?:confused:
     
  5. poke

    poke Guest

    0
     
    no just create the subdomain as an actual domain in plesk and then use your cert for this subdomain... In the cert section...

    Hope this helps
     
  6. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Hardweb - I am curious as to why you would post that '1. You can not use https for subdomains.' I do it all the time, here is an example of one on my test server you can browse to right now as a test:

    https://plesksub.james-yee.net/

    And I have done it by creating the subdomain either with Plesk, or with 4PSA Total Domains.
     
  7. diesof

    diesof Guest

    0
     
    The solution of jamesyeeoc is working without creating the subdomain as an actual domain in plesk? Because I'm searching for a solution without creating for each subdomain allways a normal domain account.:rolleyes:
     
  8. jamesyeeoc

    jamesyeeoc Guest

    0
     
    I just modified the index pages in each folder (httpdocs and httpsdocs), so if you browse to each one, you will see it is pulling up different pages:

    http://plesksub.james-yee.net
    https://plesksub.james-yee.net

    This is just a test server, so after a couple of days, the subdomains may not be there.
     
  9. diesof

    diesof Guest

    0
     
    Sorry - but I did'nt understand which modification you did in the example index-file so that SSL is working also in the subdomain httpdocs directory.
    My Plesk version is 7.5.4 and and I've selected: Use a single directory for housing SSL and non-SSL content for the full domain. But I've allways a "Not Found" on the screen.:confused:
     
  10. Aristo

    Aristo Guest

    0
     
    I just don't understand how can you use HTTPS in subdomains if you don't have any httpsdocs in your subdomains folder. Also, No options is available for housing ssl and non-ssl webpage as standard domain.
     
  11. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Strange. I do have an httpsdocs folder and it has it's own set of files.

    The 'Use single directory' option will not affect subdomains due to how Plesk has the option setup/coded (short sighted on their part).

    I will do retesting later this week on a fresh test server (continued testing of CentOS 3.x and 4.x), but I do know it works for me. The current test server's 'plesksub' subdomain folders are in a mess right now due to some other testing I was doing.
     
  12. diesof

    diesof Guest

    0
     
    Making the setup for a subdomain under Plesk no httpsdocs folder will be created for the subdomain. I'll try to test it with a manual created httpsdocs folder and will inform you later about the result. I would prefering the nested soloution because I've to run a reservation software and I don't want to split the software for each client in 2 different folders (http/https).

    The test it with a manual created httpsdocs folder in the subdomain directory failed. Maybe jamesyeeoc is using some different conf. files?;)
     
Loading...