search

plesk / letsencrypt-plesk

Let’s Encrypt extension for Plesk gives all Plesk users the power to get a free Let’s Encrypt certificate with just a couple of clicks.
https://www.plesk.com/extensions/letsencrypt/
180 stars 25 forks source link

Feature Request: Wildcard subdomain support #192

Open enekochan opened 6 years ago

enekochan commented 6 years ago

Since January 4 2018 Let's Encrypt introduced a public test API endpoint for the ACME v2 protocol and wildcard support:

https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html https://community.letsencrypt.org/t/acme-sh-supports-acme-v2-wildcard-now/49685

Is there any plan on adding this feature for this extension? If so, when could we expect to have it released? Thank you!

rkosolapov commented 6 years ago

Hi, no ETA for now.

mrclschstr commented 6 years ago

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

ioweb-gr commented 6 years ago

This would be very useful to implement. The sooner the better :)

CHfish-ch commented 6 years ago

I agree and hope you allow to use external name servers

enekochan commented 6 years ago

@rkosolapov Can this now be achieved using the command line in some way until it's supported from the Plesk control panel or using the Plesk plugin for Let's Encrypt and the command line are mutually excluding?

mahony0 commented 6 years ago

Any hope for implementing this feature sooner?

rkosolapov commented 6 years ago

@enekochan you can use third-party client to get a wildcard certificate. Plesk will not touch it (there is a little nuance - the name of the certificate should not begin with "Let's Encrypt").

Regarding the feature implementation - first version is planned to be released soon (next month maybe), that release will cover basic scenarios only.

@CHfish-ch, could you describe your case with external name servers? Do you mean your DNS servers are not synchronised with DNS zones in Plesk? Looks like we can't automate this case, the only thing we can do - provide an instruction what DNS record should be added to the zone.

CHfish-ch commented 6 years ago

@rkosolapov Indeed: My providers DNS servers are not synced with Plesk - but I'd be willing to manually add the requested entry to DNS if it is displayed... So thank you for adding such an option!

digitall-it commented 6 years ago

Would fix #197 when on a subdomain.

ghost commented 6 years ago

@rkosolapov what about it ?

enekochan commented 6 years ago

The final announcement of the ACMEv2 release with wildcard support: https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579

Some technical information about ACMEv2: https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578

MrSnoozles commented 6 years ago

Is this feature planned for the Plesk extension?

Patta commented 6 years ago

@MrSnoozles https://support.plesk.com/hc/en-us/articles/115000490174/comments/360000314893

Patta commented 6 years ago

It's in. Check the link above

digitall-it commented 6 years ago

Too bad the domains still do not renew automatically yet.

tamer-hassan commented 5 years ago

wildcard option still broken and the workaround instructions (link below) don't work because you can no longer uncheck the aliases options (they get checked and disabled when checking wildcard option).

https://support.plesk.com/hc/en-us/articles/360008040893-www-alias-subdomains-are-not-included-into-the-issued-wildcard-Let-s-Encrypt-Certificate

would've followed the manual instructions here: https://talk.plesk.com/threads/lets-encrypt-wildcard-certificates.347562/

but unfortunately I have to wait a week now because I got hit by the renewal rate-limit bug described in: https://github.com/plesk/letsencrypt-plesk/issues/207