Since the beginning of this year, Let’s Encrypt rolled out a new shortlived profile for certificates that make them valid for only 160 hours. The intention, as they say, is to encourage automation and reduce the window of certificate compromise (because revocation is somewhat a flakey thing).
Yet, I haven’t seen a lot of news about it since then. Hence the question: is this shorter cert thingy something you considered and deployed for your homelab?
As for me I’ve set up lego-acme with profile: "shortlived" on my rig. Lego runs on a bihourly cronjob, but only renews when a cert has >=3 days to expiry. It’s been pretty much a set-and-forget experience, although some more monitoring would be nice.
Everyone in here taking about an the automations they’ve done for certs and I just use Caddy. It handles all that for me.
Yeah but if you want to use something different, or may need to use different web servers or proxies from time to time, it’s better to have the cert renewal stuff separated.
Also, for any provider that’s off the beaten path you have to build caddy yourself to include the right plugin and that’s just meh.
Caddy’s fine if you only use one provider and only Caddy all the time but other than that no.
I’m already building a custom image of Caddy with plugins for Crowdsec integration. It’s not hard to do. But I have no reason to use anything other than the default Let’s Encrypt setup.
DNS for let’s encrypt via caddy integration and just have the same definition for all of your caddy servers and whatever you point your domains at will work as expected. Single config and redundancy with certs.
Caddy is a good piece of software.
I’ve been using Nginx for 20 years and don’t really have a reason to switch, so I’m still using it. I use certbot, so it’s just one command to create the certificate initially, and then it auto-renews automatically via a systemd timer.