Straight Dope: Site Not Secure, Invalid Certificate, Expired Certificate

I just got a message coming to this site using Firefox and had to add an exception.

I see that your HTTPS certificate expired today.

Personally, I’d prefer to have HTTPS disabled, and return to HTTP, but I understand that the big advertising company is controlling the browsers most people use.

This just started happening. Is anyone else getting these errors? I’ve tried in Chrome, Edge, and Firefox, and I get the same error on all three.
Is this a global problem, or a local one? If local, is there something that I need to fix or set?

We both just posted about the same thing.

and its not letting me get to the site unless I click ob details and where it says go on to thye web page
heres the page I get :
This site is not secure

This might mean that someone’s trying to fool you or steal any info you send to the server. You should close this site immediately.


Go to your Start page
Details
The website’s security certificate is not yet valid or has expired.
Error Code: DLG_FLAGS_SEC_CERT_DATE_INVALID
Go on to the webpage (Not recommended)

I just posted a thread on this heh

Yeah, Kaspersky freaked out and I had to slip the guard a fifth of vodka to get past him into the Dope.

So like, did a certificate expire or something? I merged like 4 threads together to consolidate and have emailed folks behind the scenes.

[/moderating]

Same here. I emailed somebody thinking I need to change my password. Whomever can disregard that.

The certificate just expired 30 minutes ago. The site admin needs to get a new certificate to resolve this.

Yeah, the certificate expired. Ed got one that lasted a year from last year, rather than the shorter autorenewing ones.

I’m actually quite concerned about the site given how it seems that it seems tech support is completely uninterested in working on anything, even simple changes. It was one thing when Ed’s hired support was busy with other changes, but now?

The certificate on the main site is still valid, and used Let’s Encrypt, which sets up those smaller, auto-renewing certificates. I do not know why the board is using a different certificate authority.

FWIW, it is in fact a global issue. Also affects how the site displays on some browsers.

What a PITA.

What’s really bugging me is that on Chrome, it’s not doing what it did on another site. It keeps periodically bringing back up the warning message, even though I chose to bypass it. Before, it’s always just let me keep using the site without question.

I don’t want to have to turn off certificate validation in general. And signing my own certificate for the site seems complicated.

Surely the PTB are working on it.

Don’t call me Shirley

Oh, I see, Shirley forgot the squirrel kibble.

It looks like someone just put in a fresh certificate. We should be good. :slight_smile:

We should thank Shirley.