Let's Encrypt: Active Incident, DNS errors causing service disruption

Re:Let's Encrypt: Active Incident, DNS errors causing servic... by jldugger on Friday April 15, 2016 @01:37PM (#11506169)

By my estimation, Lets Encrypt has at least 16 million dollars in annual sponsorship.[1][2] That's quite a bit of money, but I wonder how much of it goes to operations, versus other overhead of various kinds (legal, marketing, administrative).

Many of our clients are excited about LE, and as we figure out how to support it without disrupting our infrastructure too much, it's concerning to imagine that there's substantial daily risk that 4-5 certs will fail to renew.

I suppose since it's free and automated, you just renew a month earlier than required.

[1] https://letsencrypt.org/sponsors/ [2] https://letsencrypt.org/become-a-sponsor/

[ Parent | on HN ]

Re:Let's Encrypt: Active Incident, DNS errors causing servic... by JonathonW on Friday April 15, 2016 @01:57PM (#11506322)

That's their idea-- the reference client (by default) will renew any certificates expiring within 30 days, and they recommend you script it to run at least daily. That gives it many opportunities to retry in case of network problems or server outages (on your end or on theirs).

[ Parent | on HN ]