This was my fault. Apparently letsencrypt changed their email notifications so this refresh was missed. Of course we’re not gonna run a large python program like certbot on the server serving binaries, which makes this somewhat more complicated.
Luckily we recently started hosting DNS ourselves so we can run certbot in DNS mode on a separate machine. That’s done now (which is why it took a while to renew this morning), so hopefully this will not be an issue in the future, though I need to finish fully automating it today.
As for acme.sh, last I checked it was also a rather large codebase to audit, plus shell scripts downloading things is also pretty scary. In any case, DNS remotely is good.
On Nov 28, 2019, at 10:53, Stadicus ***@***.***> wrote:
Thanks for fixing, works like a charm again. Issue can be closed, unless you want to track some follow-up work.
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Deutsche Bank (DB) believes cryptocurrencies could replace fiat by 2030 as the “forces that hold the fiat money system together” begin to unravel. The bombshell was dropped in a report Thursday by the...
Good news – in collaboration with our newest EUR funding partner, Liechtenstein-based Bank Frick, we have added our newest fiat asset, the Swiss franc (CHF). This is the sixth currency that Kraken wil...