Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

RapidSSL and GeoTrust paid SSL certificates provided by SSL It! extension are not supporting www and SAN

Avatar
Marc López
Updated
Follow
Plesk for Windows Plesk for Linux kb: fixed kb: bug ext: le ABT: Group B

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Symptoms

  • RapidSSL paid certificate has been issued but it doesn't include www domain version despite the Plesk GUI shows it is supported:

    mceclip0.png

  • GeoTrust paid SSL certificate has been issued but it doesn't include www domain version nor SAN support despite the Plesk GUI shows both are supported:

    mceclip1.png

Cause

Product issue:

  • #EXTPLESK-2047 "SSL/TLS certificates from DigiCert do not support SAN. Fixed the incorrect description that said otherwise."
    Fixed in:

Resolution

Please consider updating your server:

Workaround

If update is not possible for some reason you may try the following

workaround

Note: Contact Licensing and Purchase support to request a refund if necessary

Issue a free Let's Encrypt certificate including www and non-www domain versions or a wildcard certificate

Comments

2 comments

Sort by Date Votes
  • Avatar
    Colin Thompson

    Is a reboot of the server required for this to take effect?  I have auto updates enabled for my server and the situation is the same.  The DigiCert version is showing as 1.9.1-203.

    The workaround is not favorable as I have been down that road before.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Colin Thompson

    The server reboot isn't required here. 

    It's required to reissue a certificate. Please, contact our licensing team and describe the issue.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles