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 20, 2020. It is now read-only.
Wildcard support is coming to Let's Encrypt on February 27, 2018. There's one gotcha -- only the DNS validation protocol will be available:
Wildcard certificates will be offered free of charge via our upcoming ACME v2 API endpoint. We will initially only support base domain validation via DNS for wildcard certificates, but may explore additional validation options over time.
That means an end user will have to create a DNS TXT record for both creation and renewals. There are some plugins available to automate this for some providers (e.g. Amazon Route 53, DigitalOcean DNS). Integration with ClearCenter DNS should be possible though.
To investigate further.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Wildcard support is coming to Let's Encrypt on February 27, 2018. There's one gotcha -- only the DNS validation protocol will be available:
That means an end user will have to create a DNS TXT record for both creation and renewals. There are some plugins available to automate this for some providers (e.g. Amazon Route 53, DigitalOcean DNS). Integration with ClearCenter DNS should be possible though.
To investigate further.
The text was updated successfully, but these errors were encountered: