-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wildcard #8
Comments
It would be cool. Is the wildcard certs nowadays 100% supported by letsencrypt? If so, this addition is more than welcome |
Yes, but there is one problem at Debian/Ubuntu. The cerbot ist not yet ready for renew. You must create every 90 days a new TXT record at your NS to get new certs.
So it is nothing for a renew script. But maybe a option on start.
5. Sep. 2018, 11:33 von notifications@github.com:
…
It would be cool. Is the wildcard certs nowadays 100% supported by letsencrypt? If so, this addition is more than welcome
—
You are receiving this because you authored the thread.
Reply to this email directly, > view it on GitHub <#8 (comment)>> , or > mute the thread <https://github.com/notifications/unsubscribe-auth/AHdGM-vSi-1tgGF07piLpKmng0vB5AfLks5uX5p7gaJpZM4WabIx>> .
|
Why not, if it's something that can be automatized why not adding this feature |
Yeah, but a script could not set the TXT records.
…--
Liebe Grüße
Malte Kiefer
5. Sep. 2018, 12:22 von notifications@github.com:
Why not, if it's something that can be automatized why not adding this feature
—
You are receiving this because you authored the thread.
Reply to this email directly, > view it on GitHub <#8 (comment)>> , or > mute the thread <https://github.com/notifications/unsubscribe-auth/AHdGM8LN0oI3XLdPUsYLD7i65QRDLAOsks5uX6XJgaJpZM4WabIx>> .
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should we update this script to use wildcard certs?
The text was updated successfully, but these errors were encountered: