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

**URL:** <https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722>\
**Category:** About This Message Board\
**Created:** [December 7, 2018, 12:17am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722 "2018-12-07T00:17:37Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![PastTense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pasttense/32/14550_2.png) [@PastTense](https://boards.straightdope.com/u/PastTense)\
**Post date:** [December 7, 2018, 12:17am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/1 "2018-12-07T00:17:37Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Melbourne](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Melbourne](https://boards.straightdope.com/u/Melbourne)\
**Post date:** [December 7, 2018, 12:18am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/2 "2018-12-07T00:18:26Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\
**Post date:** [December 7, 2018, 12:18am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/3 "2018-12-07T00:18:31Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\
**Post date:** [December 7, 2018, 12:19am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/4 "2018-12-07T00:19:31Z")

</div>

We both just posted about the same thing.

---

<div class="post-metadata">

**Author:** ![nightshadea](https://avatars.discourse-cdn.com/v4/letter/n/7ba0ec/32.png) [@nightshadea](https://boards.straightdope.com/u/nightshadea)\
**Post date:** [December 7, 2018, 12:20am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/5 "2018-12-07T00:20:08Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![nightshadea](https://avatars.discourse-cdn.com/v4/letter/n/7ba0ec/32.png) [@nightshadea](https://boards.straightdope.com/u/nightshadea)\
**Post date:** [December 7, 2018, 12:22am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/6 "2018-12-07T00:22:31Z")

</div>

I just posted a thread on this heh

---

<div class="post-metadata">

**Author:** ![ThelmaLou](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/thelmalou/32/390_2.png) [@ThelmaLou](https://boards.straightdope.com/u/ThelmaLou)\
**Post date:** [December 7, 2018, 12:27am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/7 "2018-12-07T00:27:27Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Bone](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bone/32/407_2.png) [@Bone](https://boards.straightdope.com/u/Bone)\
**Post date:** [December 7, 2018, 12:29am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/8 "2018-12-07T00:29:11Z")

</div>

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

[/moderating]

---

<div class="post-metadata">

**Author:** ![Beckdawrek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/beckdawrek/32/3647_2.png) [@Beckdawrek](https://boards.straightdope.com/u/Beckdawrek)\
**Post date:** [December 7, 2018, 12:30am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/9 "2018-12-07T00:30:26Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![AnalogSignal](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/analogsignal/32/1085_2.png) [@AnalogSignal](https://boards.straightdope.com/u/AnalogSignal)\
**Post date:** [December 7, 2018, 12:31am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/10 "2018-12-07T00:31:42Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [December 7, 2018, 12:35am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/11 "2018-12-07T00:35:25Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [December 7, 2018, 12:40am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/12 "2018-12-07T00:40:14Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![bordelond](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bordelond/32/150_2.png) [@bordelond](https://boards.straightdope.com/u/bordelond)\
**Post date:** [December 7, 2018, 12:42am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/13 "2018-12-07T00:42:50Z")

</div>

> [@Bullitt](#):
>
> Is this a global problem, or a local one? If local, is there something that I need to fix or set?

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

---

<div class="post-metadata">

**Author:** ![Qadgop\_the\_Mercotan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/qadgop_the_mercotan/32/83_2.png) [@Qadgop\_the\_Mercotan](https://boards.straightdope.com/u/Qadgop_the_Mercotan)\
**Post date:** [December 7, 2018, 12:47am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/14 "2018-12-07T00:47:06Z")

</div>

What a PITA.

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [December 7, 2018, 12:51am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/15 "2018-12-07T00:51:56Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Beckdawrek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/beckdawrek/32/3647_2.png) [@Beckdawrek](https://boards.straightdope.com/u/Beckdawrek)\
**Post date:** [December 7, 2018, 12:58am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/16 "2018-12-07T00:58:42Z")

</div>

Surely the PTB are working on it.

---

<div class="post-metadata">

**Author:** ![Qadgop\_the\_Mercotan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/qadgop_the_mercotan/32/83_2.png) [@Qadgop\_the\_Mercotan](https://boards.straightdope.com/u/Qadgop_the_Mercotan)\
**Post date:** [December 7, 2018, 1:00am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/17 "2018-12-07T01:00:04Z")

</div>

> [@Beckdawrek](#):
>
> Surely the PTB are working on it.

Don’t call me Shirley

---

<div class="post-metadata">

**Author:** ![Beckdawrek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/beckdawrek/32/3647_2.png) [@Beckdawrek](https://boards.straightdope.com/u/Beckdawrek)\
**Post date:** [December 7, 2018, 1:05am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/18 "2018-12-07T01:05:44Z")

</div>

Oh, I see, Shirley forgot the squirrel kibble.

---

<div class="post-metadata">

**Author:** ![AnalogSignal](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/analogsignal/32/1085_2.png) [@AnalogSignal](https://boards.straightdope.com/u/AnalogSignal)\
**Post date:** [December 7, 2018, 1:56am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/19 "2018-12-07T01:56:01Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Bullitt](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bullitt/32/5725_2.png) [@Bullitt](https://boards.straightdope.com/u/Bullitt)\
**Post date:** [December 7, 2018, 2:18am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/20 "2018-12-07T02:18:30Z")

</div>

> [@AnalogSignal](#):
>
> It looks like someone just put in a fresh certificate. We should be good. 🙂

We should thank Shirley.

[Next page](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722.md?page=2)
