- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
It’s breaking the access to the website and not a good look for the “app store for Linux”. A lesson in central points of failure?
You must log in or register to comment.
https://www.flathub.org is using Let’s encrypt. Their certs only last 90 days so you need a script to make sure they are updated and pushed to your site. https://flathub.org uses Globalsign which lasts for 13 months. My guess is they don’t have a process for reconciling the two types of end dates.
It’s not hard to automate? I remember when Firefox had this same flub, lol
Even just manually, how hard is it to put a reminder in a calendar somewhere? I’ve never understood how/why this happens, it’s really but difficult.
You don’t even need to automate. Certbot comes with a systemd timer called
certbot-renew.timerwhich does this for you.
Well that instills confidence
FWIW … it is fixed now.
It’s broken on the www.flathub.org domain but not on just flathub.org by itself. Despite browsers trying to get rid of www its still commonly used.
Yeah, it isn’t a good look for flathub. I looked at the certificate and the Subject Alternative Names section was missing the www prefix. Why they’re not using Let’s Encrypt and certbot beats me because this could all be automated.
So basic. Even I had it automated for my personal wedding website. Lol.
I use the DNS-01 challenge to take advantage of wildcard certs. Every 30 days, I have a cron job force a renewal, send a SIGHUP to nginx and I am back in biz. Ez-pezy
Same here, just works!
topkek
It’s not expired for me rn, so is this something that happened before?
Did you go on flathub.org or www.flathub.org? The certs are fine on the former, but expired on the latter.
And it’s still less shit than Snaps. It’s the giant douche and turd sandwich situation with this stuff.
Ummm … oops? 🤷♂️ 😆
