You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2019. It is now read-only.
acme4j has been updated and there is a pending 2.0 release (currently available as a snapshot release), which will be released in stable form before Let's Encrypt launches their V2 service at the end of February.
Wildcard certificate support has been added in that library, too, but I haven't yet investigated which changes to the DNS responders (if any) are required for it.
@tazjin I'd be interested in helping get this off the ground if you could give me some guidance and point me in the right direction of how to get started 👍
@mansona Hey! As far as I know acme4j (the upstream library this project uses for speaking to Let's Encrypt) has been updated with support for wildcard certificates, so the first step is to update the library version used by the controller.
It'll probably become obvious at that point what needs to be done to support wildcard certificates (most likely some changes to how it decides where to create the verification records etc.)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
These are coming in January 2018 and it would be cool to have support right away: https://letsencrypt.org/2017/06/14/acme-v2-api.html
Gotta see if the ACME lib will be updated or if this is my problem to deal with!
The text was updated successfully, but these errors were encountered: