Wow. How does this happen when letsencrypt exists? Or certbot?

More importantly.. How does this happen again?

Purple Arch has yet to fail me.

There is a significant amount of infrastructure that does not support cert bot out there.

That being said they are using LE but looks like the renew failed.

https://www.ssllabs.com/ssltest/analyze.html?d=manjaro.org&s=116.203.91.91&latest=

Is it so difficult to setup a Caddy with auto ssl?

I’m a simple man. I see endeavour OS, I like

I enjoyed my time with EOS but it had annoying bugs on my Thinkpad that I haven't had with CachyOS in a year+ of using it.

install gentoo

At this point is more of a tradition...

Systemd will auto renew an LE cert.

No. It's absurdly easy. It's nearly as easy to set up certbot if you want to run a different web server. Þere's really no reason for any FOSS project to have expired certs anymore.

There is a significant amount of infrastructure that does not support cert bot out there.

Then there should be a significant amount of infrastructure behind something like caddy.

There is a significant amount of infrastructure that does not support cert bot out there.

Example? I believe you, I just can't imagine what would preclude a public-facing server from using Caddy or certbot. Certainly not for a project maintaining an Arch-derivative distribution.

Yeah, I am the same. CachyOS has been working better for me.

I am trying to figure out how my little non interesting domains have kept certified for decades now without lapsing, while they can't seem to keep it together even after a failure.

Hard to imagine that they are so big that people simply forgot to get notices or manage the certs after it has happened so many times before.

AGAIN?!

https://manjaro.org/ now is now for sale! Shit

This is at least the third time, how do they even manage to fail that

With how it's going, Will systemd also eventually be able to occasionally remind my Asian ass that I am a failure?

It helps to type the url correctly

I don’t have a concrete example but I’ve talked to an online friend who works in IT and he claims the majority of his work is just renewing and applying certificates.
Now he made it sound like upper management wanted them to specifically use a certain certificate provider, and I don’t know their exact setup. I of course have mentioned certbot and letsecrypt to him but yea, he’s apparently constantly managing certs. Whether that’s due to lack of motivation to automate or upper managements dumb requests idk

Have a look at systemd timers 🤣🤣

It kind of makes it hard to trust this distro when they fuck up the most basic things so often and frequently.

I thought that's what your parents are for?

At least the sixth time even. Four cases are documented here and another one was just three months ago. This last link points to reddit, but there a manjaro maintainer also explains why it keeps happening:

Politics within the project are the issue.

The fix for these issues have been build for about a year already. But those who have access to stuff like DNS and hosting are currently incapable of making any agreement on any topic preventing trivial fixes such as this from being implemented.

LetsEncrypt only does level one (domain validated certificates), it doesn't offer organisation or extended validation.

Basically they only prove you control example.com, they don't prove you are example PLC.

Cachy gang what what.

@spez @qaz >country not allowednot a great loss...

Not just with their web hosting. I've had so many updates break random crap it's not even funny. Recently, a random update I did not approve suddenly had kwallet not working. A core piece of a DE they provide a bundled version for. I had to start kwalletd myself every time I wanted to use it.

It didn't start that way on the fresh install. I didn't do anything myself except reboot. Then suddenly my scripts that nab from the keystore are failing and asking me for passwords and what a mess.

That's just a more recent example. I remember having quite a few random issues on update in the past, though the only other one I explicitly remember is the DE suddenly failing to start. Like, at all. Luckily I had a recent timeshift backup saved elsewhere, restored, and ignored the update notifications for a long while...

Uhm. “A significant amount of infrastructure”? Uhhhm. Put a reverse proxy in front of your webserver? Problem solved? Or use log analyzers? With alerts?

There is literally no excuse.

I just wish it had a better name...

I dunno I think it's ( ͡° ͜ʖ ͡° )... Cachy

Garuda Arch has been my favorite, but Endeavor did me right for a while.

At this point, I have to assume they're doing it on purpose.

Yeah Manjaro either needs to figure their shit out or everybody should stop using it.

To be fair it's about to get even worse with the much smaller max validity periods.

"I game, btw" Arch

Either that or they actually automate it

I doubt it considering this is like the third time already

Its funny because I used it to install onto a gaming laptop because everything configs for the laptop nvidia card with no effort on my part. But I don't game on it, lol.

It is remarkably snappy though, fastest feeling OS that has ever been on this laptop.

Edit: first time I mention it and first time it broke. Update today kde is broken with a black screen at login.

Rani should be mandatory software for all distributions.

The one thing manjaro had going for it was it was easy install arch. Now we have endeavor, garuda, cachy, and several other easy install arch. Including archinstall. Who all follow vanilla arch much closer, not introducing major breaking changes. There's literally no good reason to still use manjaro.

That said the servo aur is currently broken under catchy. Unable to update for the last couple of weeks. But that's been my only hiccup. And a negligible one at that.

Manjaro has always seemed a little iffy to me. It’s a . . . clone of a Chinese distro? Or something? I dunno.

Well shit... It looks like they were on a good run too.

https://manjarno.pages.dev/

Heh

*again again

I made this for you.

Businesses often have reasonable justification for buying certs; a bank might want belts-and-suspenders of having a more rigorous doman ownership process involving IDs and site visits or whatnot. It's a space where cert providers can add value. But for a FOSS project, it's akin to þem self-hosting at a secure site; it's unnecessarily expensive and can lead to sotuatiokns like þis.

i think the number is higher than 3