www alias, subdomains are not included into the issued wildcard Let's Encrypt Certificate

Follow

Comments

12 comments

  • Avatar
    Jan Bludau

    would be really nice if *.example.com i mean wildcard SSL would be working...

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Jan,

    Thank you for the feedback.

    Generally, a wildcard certificate may be issued using this instruction.

    But indeed, currently due to this bug www is not included.

    2
    Comment actions Permalink
  • Avatar
    Zacchary Puckeridge

    Hey guys!

    I couldn't get this work around to function correctly on Plesk Obsidian.

    I'm trying to secure www. on an alias. I can get up to Step 7, but Step 8 appears to be impossible as I am not able to select which certificate the alias should use. Any ideas?

    1
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Hi Zacchary Puckeridge step 8 is for subdomains and it is not needed for aliases. The alias is included in the certificate generated in step 7. Please verify from your side if accessing the alias is done in a secured way.

    0
    Comment actions Permalink
  • Avatar
    Jan Bludau

    Plesk Obsidian does the job really better.

    The SSL IT Extension is really great.

    -1
    Comment actions Permalink
  • Avatar
    Chris Barfitt

    This doesn't help with non www.alias.com domains, it doesn't help with getting example.alias.com to work, when example.main.com works.

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    Hi Chris Barfitt,

    This is caused by a bug which as well. You may find a solution here

    0
    Comment actions Permalink
  • Avatar
    Glenn

    I found a simple workaround. Just add www.domain.com alias in addition to the domain.com alias. It worked perfectly.

    0
    Comment actions Permalink
  • Avatar
    Dr. Koontz

    For step 5 above, according to my experience, and the Plesk article linked below, renaming the certificate will prevent it from being renewed.

    https://support.plesk.com/hc/en-us/articles/213930645--BUG-Let-s-Encrypt-auto-renew-is-not-working-for-domains-or-Plesk-with-renamed-certificates

    Has the auto-renew for renamed certificates been fixed?

    0
    Comment actions Permalink
  • Avatar
    Mikhail Shport

    Hi Dr. Koontz

    Indeed, these two bugs interfere with each other. Thank you for bringing our attention to this fact.

    We will review the article in order to add the warning about the inability to auto-update a renamed certificate.

    Regarding the question, there is no exact ETA for fixing these bugs since they require global changes in the extension. Once the bug is fixed the article will be updated accordingly.

    0
    Comment actions Permalink
  • Avatar
    Dimitri Longo

    hi,

    Seems that issue is related with wordpress multisite subdomain, certificate is not applied to www.mysub.domain.tld. So i try ti test the workaround. But i'm confused

    in step 3 : Issue a wildcard certificate _without_ including the aliases.

    When i click (first checkbox) Protect wildcard domain so automatically it include "Include a "www" subdomain for the domain and each selected alias"

    So how can issue wildcard without including the aliases ?

    0
    Comment actions Permalink
  • Avatar
    Taras Ermoshin

    Hi @Dimitri Longo!

    You need to uncheck all aliases under "Available Domain Aliases", I've highlighted it with red on the screenshot:

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request