Certificate expired! (fixed)

Subject: Certificate expired!
From: Steve Shaw
Date: 06 Nov 22 - 01:29 PM

That's the message I'm getting when I try to log in. It sez that Mudcat's certificate expired on 4 November and issues the usual dire warnings....

Subject: RE: Certificate expired!
From: YorkshireYankee
Date: 06 Nov 22 - 01:41 PM

Yup.

Subject: RE: Certificate expired!
From: Joe Offer
Date: 06 Nov 22 - 01:47 PM

And it's usually safe to ignore the dire warnings if you know the Website. I'm just glad we're back up.

Subject: RE: Certificate expired!
From: Max
Date: 06 Nov 22 - 02:09 PM

Fixed

Subject: RE: Certificate expired!
From: Sandra in Sydney
Date: 06 Nov 22 - 04:00 PM

thanks, Max! you're the greatest!!

Subject: RE: Certificate expired!
From: DaveRo
Date: 06 Nov 22 - 04:08 PM

Joe Offer wrote: And it's usually safe to ignore the dire warnings ...

In the case of a recently expired certificate, yes - so read the error message. In the case of a site which handles no personal or financial data, probably. In other cases, maybe not. 'Knowing' the site is not enough to just ignore a certificate warning.

Subject: RE: Certificate expired!
From: Steve Shaw
Date: 06 Nov 22 - 05:17 PM

I was happy to ignore the warnings, otherwise I wouldn't have posted. Just thought I'd mention it. Cheers for the fix, Max.

Subject: RE: Certificate expired!
From: Tattie Bogle
Date: 06 Nov 22 - 07:22 PM

Glad to know it’s fixed: thanks Max! Couldn’t get in at all before it was, so it wasn’t just a question of ignoring it.

Subject: RE: Certificate expired!
From: Steve Shaw
Date: 06 Nov 22 - 07:47 PM

What I meant was the warnings this afternoon once Mudcat was back up.

Subject: RE: Certificate expired! (fixed)
From: leeneia
Date: 10 Nov 22 - 02:25 PM

Christmas is coming.

Time to think about charitable giving, including to the Mudcat, where we get so much music, information, and social exchange.

Ditto Wikipedia.

Subject: RE: Certificate expired! (fixed)
From: MaJoC the Filk
Date: 11 Nov 22 - 11:14 AM

It's not just the certificate itself that's the problem. Each certificate has a "this is trusted, and I say so" entry from an upstream certification provider; the browser follows this chain of certificates till it arrives at one that the browser itself knows it can trust (there's a table of such authoritative sites somewhere inside the browser). If that chain contains a site which is in yoyo mode, or is overloaded or connected to the Net by a bit of wet string, that's when you'll see intermittent "untrusted certificate" warnings.

Hope this helps. I also hope that the bit of wet string in question doesn't let me down before this reply makes it back to the 'Cat.