Seems fine for me now. In fact it looks like they switched to Let’s Encrypt for certification so maybe they learned something from last time.
Perhaps the looming prospect of having to do it every 47 days was enough.
oh my god AGAIN?!
They gotta be trolling the entire linux userbase at this point.
No this did NOT happen again. OP is just trolling Manjaro.
The page works fine: https://manjaro.org/The certificate for manjaro.org was renewed only a few hours ago. Given Manjaros track record, they probably let the cert expire (again) and fixed it since the original screenshot was taken.
The screenshot seems to be taken at 1:50 utc, and the new certificate was valid from 00:18 utc. It is possible though that they just.enrolled the cert too late.
I’m shocked it even has any users tbh.
It was part of my linux journey long ago, and TBH I bet many still run into in from historical recommendations and popularity.
But I think CachyOS is taking over their “preconfigured arch with the most SEO” spot.
Honestly, I installed it on my 2nd laptop and workstation because I really wanted the AUR, but got tired of Arch unstable update process 15 years ago and left Linux for personal use for MacOS. It still has everything I want on my main laptop, home brew and a terminal with tmux.
It just works and I just couldn’t be arsed reinstalling, but yeah, if I would, I would just use Arch again now.
I use EndeavourOS (from Manjaro a lifetime ago) no complaints.
Well, Manjaro popped up when a lot of people cannot install Arch on their own. Same thing with Ubuntu and Debian. Once a userbase formed, people follow suit I guess.
I mean they have their own repos and take a position of “hardened updates” that are two weeks older than the bleeding edge ones of Arch. I used it briefly out of curiosity a couple years ago. It seemed generally fine, although I seem to remember having issues with some AUR stuff. That’s kinda to be expected and could even just be general fuckery on the part of the package maintainers, not manjaro. It could also be on manjaro’s fault lol.
I’ve just stuck to Arch since then. Garuda and endeavour OS are both cool but I don’t feel like I’m gaining much by using either. And Garuda includes a bunch of packages that I don’t even want.
I’m more interested in what manjaro can do in the mobile phone sphere. If they can build something viable yet fun to tinker with in the next few years that has a rolling release schedule, it could make for a cool Linux phone. Ubuntu touch is probably the more stable choice tbh, but that’s the beauty of Linux.
It was a selling point for Manjaro at some point but people really shouldn’t use AUR with it. That’s just an invitation to a disaster. I think Manjaro is stable if you don’t mix it with AUR. Used it for 6 years and the worst I remember was their Nvidia cataclysm, mostly it was fine.
Not sure if I would want to use cutting edge on mobile though. I tried PostmarketOS and Ubuntu Touch a couple years ago and Ubuntu Touch was actually daily drivable-ish. Really loved SXMO too, it’s a way different mobile experience.
Manjaro was more unstable than Arch ever was, for me.
My experience was:
-
They would mess with Arch packages and muck things up.
-
It relied on AUR some, which also messed things up.
-
3rd party repos or AUR didn’t work, as its not in sync with upstream arch.
-
…Holding back packages didn’t fix anything anyway. It just delayed fixes. I found myself trying to install upstream Arch packages.
It turns out Arch Linux is more tested and “held back” than people give it credit for. There’s little to gain from forking like that, instead of just contributing to upstream arch testing.
Not to mention the cert thing. Manjaro really did let certs expire many times. When I was new to linux, that took me forever to figure out.
I found myself trying to install upstream Arch packages.
You realize that’s how you broke, right? It’s like installing Debian packages on Ubuntu.
It relied on AUR some, which also messed things up.
How does it rely on AUR?
3rd party repos or AUR didn’t work, as its not in sync with upstream arch.
What 3rd party repos?
AUR works perfectly fine… when it works. AUR is a mess of its own. It’s chock full of malware as we speak and it’s not accepted as a reference on Arch or any other Arch-based distro. Saying an Arch distro “doesn’t work with AUR” is completely irrelevant at the best of times.
Not to mention the cert thing. Manjaro really did let certs expire many times. When I was new to linux, that took me forever to figure out.
Did you spend a lot of time reading the webpage, or?.. Because that’s the only cert that expires, the mirros and the forums never did. What exactly were you figuring out?
Whoa nellie.
This was many years ago, when I didnt know much about linux, and yes many lessons were learned. Though I distinctly remember instances where I couldnt update Manjaro packages because of expired certs.
To clarify some points:
-
On packages/AUR, I was desperate, because upstream Arch had some critical fixes that werent shipped to Manjaro yet. Clearly this didnt work out well.
-
AUR specifically breaks with Manjaro because AUR targets upstream arch as a base. When a dependant Arch package updates, the AUR package immediately updates to that new dependecy if its being maintained. But since Manjaro delays the upstream updates, this AUR package will break if its updated.
-
Yes, I know AUR is filled with malware now.
AUR specifically breaks with Manjaro because AUR targets upstream arch as a base. When a dependant Arch package updates, the AUR package immediately updates to that new dependecy if its being maintained. But since Manjaro delays the upstream updates, this AUR package will break if its updated.
Again, using the AUR as the standard for evaluating any Arch-based distro is really not cool.
Leaving that aside, the exact thing you’ve mentioned can happen on vanilla Arch, if the AUR package you are trying to install is based on Arch packages that you haven’t received yet. So you’d have to upgrade your system every time you’re trying to update or install an AUR package to be sure.
since Manjaro delays the upstream updates, this AUR package will break if its updated.
It won’t break, it will either succeed compiling or not with the older packages. If it succeeds, no harm done. If it doesn’t, you still have the previous version.
The unlikely corner case is that the new AUR package version relies on new API/features that only exist in newly released Arch packages and you absolutely must have the latest version right now. But then you’re using the wrong distro for that.
I was desperate, because upstream Arch had some critical fixes that werent shipped to Manjaro yet.
Manjaro ships critical updates out of band, without waiting for regular batch updates.
-
-
The website cert is the one that expires. It doesn’t impact anything else about the distro. The package mirrors are on different hosts (and certs). It’s a good distro, wish they’d sort out the kerfuffle with the founder (who’s the one holding them back).
we know and no it is no good distro. fucking leechers
lmao, what’re they up to now, 8 times?
No OP is is trolling, the page is absolutely fine.
https://manjaro.org/
I like a distro with problems that I can relate to.
Bad memory/routines? We have to be related. Since that feels like me.
Replaced ff with floorp several months ago, pretty happy with it so far
Not sure why you’re getting downvoted, the browser used for the screenshot is sufficiently on topic for a meme sub, especially a FOSS browser for Linux on a Linux meme sub. Floorp is a pretty ridiculous name though.
I have no idea either
This is just a Manjaro hater post.
Reminding they made this mistake last year.
IT did NOT happen again!!The date shown in the error message is yesterday.
Are you sure? The screenshot shows a certificate expiring yesterday at 8:50 CDT, which is 23 Aug 13:50 GMT, and their current certificate has a validity “Not Before Mon, 24 Aug 2026 01:18:47 GMT”, so there’s a gap of around 11 hours.
I was wrong, and I deleted my posts, because they were misleading.
I thought the devs were supposed to be taking back the project. I’m guessing that didn’t happen.
It was a whole forum thing and deadline before they would fork it - have not kept up with any updates personally
The new e.V. formed in late June, but as far as I understand, they don’t actually have control over any of the infrastructure.
Well, it’s always been Manjaro either way.
I can’t see the URL for that error message?
But the Manjaro main page works fine:
https://manjaro.org/Just set your device clock to a day before 8/23, problem solved.
1/1/1970
Not to wreck your joke, but certificates have a starting date on them too, so the epoch also won’t work.
(that was the intended joke; they did say ‘pick any date’ :p)
Like, when you… “get” the certificate… Doesn’t it say… “on it” exactly which date it expires? So maybe set a thing in your calendar or an alarm on your phone or some shit? How hard can this be?
You could proactively take care of it with a reminder on the calendar. Or alternatively, just let the community inform you when you need to renew it. Both are effective methods.
The second alternative is a bit of a gamble with trust though eh 😅
Since I have never used the distro but have seen threads like these popping up every time the cert expires, I don’t think it takes much trust.
Also it’s pretty fucking hilarious.
It really is starting to become pretty laughable.
They use LetsEncrypt. There is literally a bot you can install to automate the renewal process daily on a cron schedule and notify you if it fails.
They’re just fucking morons managing the infra for their domain.
Yes there is an easy fix that will make the problem go away. At this point you know it’s deliberate.
I personally think it’s hilarious.
LetsEncrypt also gives you a month to update certificate, you don’t even have to do it yourself, just run a script once a week in cron. That’s such a level of incompetence I wonder why anyone will trust them with a distro when they can’t even do such a simple task.
yes, but the people who want to implement that are held back and sabotaged by the guy who owns the shit. this is not about incompetence.
Incompetent managers are worse than incompetent devs
They still in this gripe? Didn’t see how their uprising ended, any updates?
Dunno… Lack of collaboration skills in a Linux distro seems a lot like incompetence to me…
I feel like the end result is the same and the distinction is irrelevant.
The funniest thing about this is that it needs a single Bash script and a cronjob to solve (unless they got a REALLY bad hoster).
That bash script probably exists a bazillion times already… so even an LLM could spit it out for them.
Their organisational structure must be abhorrent for nobody to feel even remotely responsible for this.
Most web server have ACME support built-in nowadays, setup is a matter of minutes, no scripting required. This has been a solved problem for years, any sysadmin who can’t handle this basic task has no business running public-facing servers.
Yeah, caddy automatically renews certs by default, as does traefik as far as i can tell, and certbot installs a timer for this.
Yeah sure but in significantly distributed environments I’m sure there’s more complexity to it than that
Sure but that’s a solved problem as well.
And if they can’t handle distributed systems, they’re the worst possible choice to maintain a distro - a massive distributed system of PCs
And my friends wonder why I recommend against Manjaro…
HOW THE FUCK DID THEY MANAGE IT AGAIN
Why set a reminder when an expiration will do the same job
They have embraced the meme
They managed this again by not actually managing it… again.
A little stability and consistency in the world, manjaro always delivers when it comes to this.
We’re gonna sse the year of the linux desktop long before we see the year of default ACME lmao
