Originally created by @leaf-node on GitHub (Nov 29, 2016).
I didn't find this information in your documentation, but from what I can gather, the presence of the plethora of hooks suggests that automation is necessary because each month or two, full DNS verification with hooks is necessary when verifying in DNS mode.
Is this correct? Thanks!
Originally created by @leaf-node on GitHub (Nov 29, 2016).
I didn't find this information in your documentation, but from what I can gather, the presence of the plethora of hooks suggests that automation is necessary because each month or two, full DNS verification with hooks is necessary when verifying in DNS mode.
Is this correct? Thanks!
Whether you use HTTP or DNS verification, Let's Encrypt certificates are valid for only 90 days. So you have to automate re-verifying and issuing new certificates every couple months, plus deploying the new certs to any service that uses them, and restarting the service if necessary.
@whereisaaron commented on GitHub (Dec 25, 2016):
Whether you use HTTP or DNS verification, Let's Encrypt certificates are valid for only 90 days. So you have to automate re-verifying and issuing new certificates every couple months, plus deploying the new certs to any service that uses them, and restarting the service if necessary.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @leaf-node on GitHub (Nov 29, 2016).
I didn't find this information in your documentation, but from what I can gather, the presence of the plethora of hooks suggests that automation is necessary because each month or two, full DNS verification with hooks is necessary when verifying in DNS mode.
Is this correct? Thanks!
@whereisaaron commented on GitHub (Dec 25, 2016):
Whether you use HTTP or DNS verification, Let's Encrypt certificates are valid for only 90 days. So you have to automate re-verifying and issuing new certificates every couple months, plus deploying the new certs to any service that uses them, and restarting the service if necessary.
@leaf-node commented on GitHub (Dec 25, 2016):
Thanks, that clarifies. I wasn't sure whether a static DNS config could be used for later verification.