3 ms·

I just remarked the other day that I haven't had an automatic renewal work yet with tiny-acme. In theory, it should be ok, but for the first renewal the interme

I just remarked the other day that I haven't had an automatic renewal work yet with tiny-acme. In theory, it should be ok, but for the first renewal the intermediate certificate changed, requiring manual intervention. For the second renewal, the Let's Encrypt terms of service changed, again requiring manual intervention. Alas, I don't really want to use the official client. It seems messy and complex, and docker kind of contributes to that impression. I wish there was a tool that was simple, clean and elegant.

pfg 10y ago
FWIW, both of these issues are acme-tiny-specific quirks. The protocol allows clients to handle both intermediate certificate changes and ToS updates without any user interaction (and without breaking renewal). These things were not implemented in acme-tiny in order to keep the LOC count low from what I can tell. I tend to recommend lego[1] to anyone needing a high-quality ACME client without certbot's complex auto-configuration features. Might be what you're looking for. It's written in go and can be installed by fetching a single binary. [1]: https://github.com/xenolf/lego https://github.com/xenolf/lego