#letsencryt — Public Fediverse posts

Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best.

Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best.

Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best.

Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best.

Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best.

First batch of short-lived certificates issued for my domains 🎉:
https://crt.sh/?id=23954996810

#Letsencryt recently announced general availability of 6 days certificates (160 hours to be exact):
https://letsencrypt.org/2026/01/15/6day-and-ip-general-availability

I use apache's mod_md which has support for asking a specific profile to opt-in short-lived certificates, but the apache module I use with #OpenVox (previously #Puppet) was missing some parameters, so I opened this PR:
https://github.com/puppetlabs/puppetlabs-apache/pull/2621

@astrid @flohoff
Okay, so weit war mir das zum Glück schon bewusst. Aber außer unmittelbar nach der Installation alle Passwörter neu zu vergeben - welche weiteren Sicherheitsmaßnahmen empfehlen sich?
Ich hatte es auch so verstanden, dass die #letsencryt Ausstellung wohl angegriffen wird oder werden kann. Habe ich das falsch interpretiert?

Does anybody happen to know how difficult it would be to use #certbot to renew certs for a half-dozen websites on a server (and a Prosody #xmpp server)? acme_tiny.py has crapped out on me for the last time while I can't log in to fix things. #letsencryt