Egregoros

@Paradox @prettygood they stopped doing long lived certificates and there's a sunset period in the browsers themselves that hasn't taken effect yet, to start ignoring the expiration of long-lived certificates and consider them expired sooner

@Paradox things are moving in the complete opposite direction, browsers won't accept certs with a life longer than like 270 days right now, and its eventually dropping to like 45 in a few years.

@prettygood @Paradox to be fair, when your webserver is set up right, it'll just do it anymore (apache and iis might be problematic, admittedly i don't know those..)

recently finished the process of moving everything from a script to just having nginx do it and, bar a couple hiccups during setup, it's been really solid

@tidest @Paradox are you using an nginx module or something? I ask because I have a janky shell script that called certbot renew and then does some hinky shit to make things other than nginx work correctly.

@prettygood @Paradox yeah, nginx-acme it relatively recently went mainline(? i think its considered that at least)
and i do use its generated certs for a couple other services, the filenames are static (though, it's undocumented.. iirc think the next major release'll have it change once more, then stay that way (if it hasn't already happened))
then, just a matter of making sure the machine reboots every so often to restart services, which happens anyways for updates in my case

@prettygood @Paradox i can get ya my configs if you're interested :3

@prettygood
Huh.
Ok I just checked my site's cert. It's valid for 3 months, so I guess I have some auto renew thing, prolly courtesy of the web host I pay for.