Is it possible to use Let's Encrypt for wildcard certificates?

Follow

Comments

25 comments

  • Avatar
    Chris Eyre

    Let's Encrypt have announced a delay - See https://community.letsencrypt.org/t/acmev2-and-wildcard-launch-delay/53654

    Does the current Let's Encrypt Plesk extension version already include the ability to automatically provide wildcard certificates as soon as Let's Encrypt start to offer them?    Or will there be a new version that I'll need to download sometime in the future?

    Thanks

  • Avatar
    Alexandr Tumanov

    @Chris,

    It may be required to update Let's Encrypt extension to get the support for this feature in future.

  • Avatar
    Chris Eyre

    Hi,

    Thank you for your answers so far.

    I see from the article linked below, that Let's Encrypt wildcard support is now live!

    https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579

    Are there any plans and timetable for wildcard support to be added to the Plesk Let's Encrypt extension?

    Thank you,

    Chris

  • Avatar
    Alexandr Tumanov

    @Chris,

    Yes, we have plans to add the support of wildcards certificates. However, as for now, Plesk Let's Encrypt extension has few limitations that do not allow it to support wildcard certificates. Currently, we cannot provide any ETA.

  • Avatar
    Arnaud

    what is the Plesk priority in roadmap on this ?

  • Avatar
    Alexandr Tumanov

    @Arnaud, currently, it is planned to release the update within one month. However, the release date may be changed.

  • Avatar
    Arnaud

    Great news ! Thanks for having taken this into account in short term roadmap !

    - Arnaud

  • Avatar
    Mark

    Is there an update on this?

  • Avatar
    Alexandr Tumanov

    @Mark, as it previously stated, it is planned within one month. There is no exact date. Just keep an eye on Plesk extension updates.

  • Avatar
    Hisham

    @Alexandr,

    for which Plesk versions will the wildcard support be available. ONYX 17.017, 17.5.3 or higher?
    I'm currently running 17.0.17 and would need to know whether I need to have to upgrade to higher version, so I can prepare upfront.

    Thanks in advance

  • Avatar
    Alexandr Tumanov

    @Hisham, the update will be for Let's Encrypt extension that should be compatible with all Onyx versions, but I cannot guarantee this.

    Therefore, I suggest you upgrading your server up to 17.8

  • Avatar
    Jeffrey Tanuwidjaja

    Is there an update on this?

     
  • Avatar
    Ivan Postnikov

    Hello @Jeffrey! This feature implementation is currently in progress. 

    After it will be implemented, the article will be updated.

  • Avatar
    Julius Huitema

    Hi,

    I know that this feature implementation is currently in progress but could you give me an indication of when this will be usable? Like a couple of days, weeks, months or even years?

    Thank you very much!
    Julius

  • Avatar
    Artyom Baranov

    @Julius Huitema,

    Hello! Unfortunately, we don't have such information :( The implementation of the feature requires a careful testing. It is hard to say for sure how much time it will take.

    I suggest to "Follow" this article to be notified as soon as the new information is available.

  • Avatar
    Nico Dorn

    Hallo,

    geht das denn jetzt wie oben beschrieben? Erstellung WildCard-Zertifikat? Ich habe wie oben beschrieben auf v2 umgestellt, bekomme aber dennoch nicht die Möglichkeit zur WildCard-Erstellung?

  • Avatar
    tomaz

    So how does one currently auto-renew wildcard LE certs? Something we can put in cron?

  • Avatar
    Anzhelika Khapaknysh

    Hello @Nico Dorn!

    I confirm that above instructions are valid.

    In case the option for issuing wildcards certificates still not available, I recommend checking the following:

    1. Make sure that Let's Encrypt extension is up to date: https://support.plesk.com/hc/en-us/articles/115000159173 
    2. Check this article: https://support.plesk.com/hc/en-us/articles/360006833233 

  • Avatar
    Artyom Volov

    Hello @Tomaz!

    Currently, auto-renewal of wildcard certificates is not implemented in any way - not in Plesk or through the command line, so cron here will not work - it is possible to do only through Plesk manually.

    Please vote for implementation of this feature in our UserVoice:
    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/35024611-implement-renewal-of-let-s-encrypt-wildcard-certif

  • Avatar
    Gunnar (Edited )

    I have made the adjustments to be able to get wildcard lets encrypt certificates. I am now amazed to read in the plesk documentation https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/websites-and-domains/advanced-website-security/securing-connections-with-ssltls-certificates/getting-free-wildcard-ssltls-certificates-from-let’s-encrypt.79603/ that subdomains are not supported with this setup.

    Isn't one of the main reasons for installing a wildcard certificate that all subdomains are secured by default? Whats the added value of wildcard over none wildcard letsencrypt plesk integration.

    In my case i need for a customer to have valid mail.domain.com and smtp.domain.com certificates. So far i have a manual workaround which is leading time and time again to unwanted problems.

    Any help is much appreciated. 

    Two days waiting for approval of this post and still no update. ????

  • Avatar
    Ivan Postnikov

    Hello @Gunnar,

    Thank you for the feedback. Indeed, currently, the required certificate needs to be chosen manually (the steps are provided in the documentation and in this article).

    The limitations are expected to be resolved in future updates.

  • Avatar
    Kalin T. (Edited )

    Hi @Ivan, @Nikita,

    I have registered a domain name and I'm trying to issue a wildcard certificate for a website hosted on a private IP using the Plesk Let's Encrypt plugin. Plesk also does not manage the DNS for the domain, I'm using 3rd party name servers. So in my case the http-01 and tls-01 challenges won't work for me. This is why I'm trying to issue the certificate using the dns-01 challenge.

    I have enabled the ACMEv2 protocol in panel.ini and I do see now the option to issue wildcard certificate, but after I click Install, the plugin doesn't show me the page with the required TXT record and instructions (like in the 2nd screenshot of this help article). The plugin directly does a dns lookup and therefore the dns-01 challenge fails.

    Please advise if I'm missing something or there is an issue/bug in the Let's Encrypt plugin.

    I have followed the instructions in the two help articles below:

    1. Getting Free Wildcard SSL/TLS Certificates from Let's Encrypt: https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/websites-and-domains/advanced-website-security/securing-connections-with-ssltls-certificates/getting-free-wildcard-ssltls-certificates-from-let%E2%80%99s-encrypt.79603/

    2. Is it possible to use Let's Encrypt for wildcard certificates?: https://support.plesk.com/hc/en-us/articles/115000490174

     

    The error that I'm getting from Plesk is:

    Error: Could not issue a Let's Encrypt SSL/TLS certificate for XXXXXXX.training.

    Please make sure that your domain is correct and the DNS A record(s) for that domain
    contain(s) the right IP address.
    Details
    Invalid response from
    Details:
    Type: urn:ietf:params:acme:error:unknownHost
    Status: 400
    Detail: No valid IP addresses found for XXXXXXX.training


    identifier  
    type "dns"
    value "XXXXXXX.training"
    status "invalid"
    expires "2018-11-01T10:48:20Z"
    challenges  
    0  
    type "http-01"
    status "invalid"
    error  
    type "urn:ietf:params:acme:error:unknownHost"
    detail "No valid IP addresses found for XXXXXXX.training"
    status 400
    url "
    token "N9SCpFVCSrvxe3gxZr1Pk6Mg1WI0IsBuVFk1pJQPwx8"
    validationRecord  
    0  
    url "http://XXXXXXX.training/.well-known/acme-challenge/N9SCpFVCSrvxe3gxZr1Pk6Mg1WI0IsBuVFk1pJQPwx8"
    hostname "XXXXXXX.training"
    port "80"
    1  
    type "dns-01"
    status "invalid"
    url  
    token "x6dM7J9F3mXnaZYzNirNgu9A42BL7-A1mvPF2nVJiTg"
    2  
    type "tls-alpn-01"
    status "invalid"
    url  
    token "V57HqhatLnWVgLVvDw_imheOEB5TgnOx4MSKW4u3_Nw"

    I would appreciate your immediate attention to this matter.

  • Avatar
    Alexandr Redikultsev

    Hello, @Kalin T.

    The error message you are providing (Detail: No valid IP addresses found for ... ) is actually returned not by the plugin, but by Let's Encrypt itself.

    Usually it means that Let's Encrypt was not able to get an IP address of XXXXXXX.training.

    Issuing wildcard certificates works in the following manner:

    1. example.com -- http-01

    2. *.example.com -- dns-01

    So http-01 challenge should be passed. However, as far as I understand, XXXXXXX.training has some local IP globally like 10.51.*... and Let's Encrypt just could not get there.

  • Avatar
    Nexbit

    Actually this is not entirely true:

    > After clicking the Install button, Let's Encrypt will either add a DNS TXT record on its own (if Plesk server is authoritative DNS for the domain) or will provide with the instructions on how to add this record (if DNS is managed by an external server)

    I don't have the DNS component installed (because I don't need it, and when I don't need something I simply uninstall it), and the Let's Encrypt extension fails with this error:

    Remove DNS record failure: DNS service is not enabled

    The extension should work even if the DNS service is not installed, giving the instructions to add the TXT record as stated in this document.

    Please let me know if there is a workaround, or I need to wait for a fix, if any will be provided. Thx!

  • Avatar
    Ivan Postnikov (Edited )

    Hello @Nexbit,

    Indeed, such an issue is confirmed as a bug of Let's Encrypt extension with ID EXTLETSENC-558:

    At the moment, there is no workaround available.
    Consider following the article to be notified when the bug is fixed - the article will be updated.
     
    Currently, there is no exact ETA.

Please sign in to leave a comment.

Have more questions? Submit a request