Expired security certificate

When I try to connect to boards.straightdope.com/sbmd I get the following error from Bitdefender (my antivirus program) displayed in my browser:

This similar error popped up three times in Bitdefender, probably because I had some pages that I had left open for some time:

This happened just a few minutes ago. Obviously, I was able to get past the error to post this message.

BTW, I don’t get the same errors from the Straight Dope main web site (straightdope.com).

The problem seems to have gone away, at least temporarily.

The expired security certificates had a validity from 1/9/2019 to 1/10/2020. The new certificates that I get when I connect without an error have a validity from 1/10/2020 to 1/11/2020. Yes, that’s one day. Does this mean the problem will recur tomorrow?

I just got it too, looks like it expired w/in the last ½ hour. One can get around it by clicking on the “No, don’t do it, it’s dangerous & we don’t recommend it link :eek:” Postpone your membership renewal & then you’re not giving them any secure data anyway as I’d hope our users are smart enough to not reuse signons/passwords on multiple sites.

Just got it too. Using Chrome browser.

Lord, Mozilla don’t wan’t me to come here. I had to click this, except that, just to allow the page to load. Got it done, yay for me? Not trying to be a dick here, but this really never happens with any other site I visit. Like none of them. I understand this place is special, but come on, now, let’s get this together.

It just happened to me, right now. Chrome.

Same here, Firefox.

Yep. Chrome on Android.

I got a fucking clock error on Chrome (Slimjet)

Your clock is ahead
No it’s not, asshole.

A private connection to boards.straightdope.com can’t be established because your computer’s date and time (Friday, January 10, 2020 at 6:56:06 PM) are incorrect.
The time is fucking right, stop saying it isn’t.

To establish a secure connection, your clock needs to be set correctly. This is because the certificates that websites use to identify themselves are only valid for specific periods of time. Since your device’s clock is incorrect,
STOP SAYING THAT!

Slimjet cannot verify these certificates.

And fucking Chrome doesn’t offer a workaround that I can see, had to post this on Firefox.

Seriously, this fucking board is not good for my stress levels.

Yup, Chrome on Windows.

Your connection is not private
Attackers might be trying to steal your information from boards.straightdope.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_DATE_INVALID

Help improve Chrome security by sending URLs of some pages you visit, limited system information, and some page content to Google. Privacy policy
This server could not prove that it is boards.straightdope.com; its security certificate expired in the last day. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer’s clock is currently set to Friday, January 10, 2020. Does that look right? If not, you should correct your system’s clock and then refresh this page.

Proceed to boards.straightdope.com (unsafe)

Yeah, same thing for me, on Chrome. I hate this.

Once you click through it once in Chrome, you should be OK with the Dope for a while.

I did send an alert (report Post) to the Mods to hopefully get their attention a little sooner.

just got this on edge:

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

Firefox for me, got the same ‘is your time wrong’ stuff, but they weren’t fanatic about it and ‘go advanced’ told me it was a certificate problem and let me click through. Still a bit of a bother.

Chrome and Firefox: connection not private.

Or, you can keep getting the damn warning over and over again. . .

The appropriate IT people have been informed. But it is the weekend. (This exhausts the information I have on the problem.)

I’m using Firefox on a Mac, and no issues for me.

Just had the issue Safari on iPad