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
Currently, the various domains use individual TLS certificates, which are cumbersome to renew (only because Let's Encrypt's automated renewal process is not without points of failure).
Overall, maintaining a single wildcard certificate will require less work and carry a lower risk of failure.
The text was updated successfully, but these errors were encountered:
Apparently, wildcard certificates are not trivial to maintain because they require authentication via the DNS-01 challenge type, which means that in order to fully-automate their renewal, it's necessary to be able to update the relevant DNS records programatically.
Additionally, there are risks associated with configuration automated TXT record updates at the DNS provider, which are detailed in one of the replies to this how-to thread:
I suppose we'll need to meditate on this a bit before taking action, but either way, the renewal process, from our end, needs to be made more or less bulletproof.
Currently, the various domains use individual TLS certificates, which are cumbersome to renew (only because Let's Encrypt's automated renewal process is not without points of failure).
Overall, maintaining a single wildcard certificate will require less work and carry a lower risk of failure.
The text was updated successfully, but these errors were encountered: