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

Apache sends wrong certificate.

Discussion in 'Plesk 11.x for Linux' started by Oswald, Jul 4, 2012.

  1. Oswald

    Oswald New Pleskian

    10
    35%
    Joined:
    Jul 4, 2012
    Messages:
    9
    Likes Received:
    0
    Apache sends wrong certificate

    I have two domains in two webspaces: example.org and example.net.

    When I visit https://example.org, Apache uses the certificate that I have configured for the example.org webspace.
    When I visit https://example.net, Apache uses the certificate that I have configured for the example.net webspace.
    When I visit https://www.example.net, Apache uses the certificate that I have configured for the example.org webspace.

    How do I convince Apache to use the certificate that I have configured for the example.net domain when somebody requests https://www.example.net?

    When I try to add a new Subdomain www to the example.net domain, I get
    When I try to add a domain alias for the example.net domain, I get
    In DNS (also managed using Plesk), www.example.net is a CNAME for example.net
     
    Last edited: Jul 5, 2012
  2. abdi

    abdi Platinum Pleskian

    31
    18%
    Joined:
    May 14, 2006
    Messages:
    2,913
    Likes Received:
    60
  3. Oswald

    Oswald New Pleskian

    10
    35%
    Joined:
    Jul 4, 2012
    Messages:
    9
    Likes Received:
    0
    Yes, they are. On closer inspection, example.net is the CNAME for www.example.net (according to Which is the "CNAME"?).
     
    Last edited: Jul 6, 2012
  4. Oswald

    Oswald New Pleskian

    10
    35%
    Joined:
    Jul 4, 2012
    Messages:
    9
    Likes Received:
    0
    Workaround:

    1. Delete the CNAME entry for www.example.net from DNS.
    2. Create a new subdomain www of example.net. This will automatically create an A entry in the DNS.
    3. Assign a certificate to the www.example.net subdomain the same way you did for example.net.

    I wonder why Plesk is bold enough to automatically create the www.example.net CNAME entry when it cannot figure out the correct certificate to use.
     
Loading...