# Straight Dope: Site Not Secure, Invalid Certificate, Expired Certificate **URL:** \ **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:** 2
**Author:** ![AncientHumanoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ancienthumanoid/32/278_2.png) [@AncientHumanoid](https://boards.straightdope.com/u/AncientHumanoid)\ **Post date:** [December 7, 2018, 2:59am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/21 "2018-12-07T02:59:38Z")
Is this some kind of bust, or what? ---
**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, 3:17am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/22 "2018-12-07T03:17:19Z")
Someone flushed the incriminating evidence. ---
**Author:** ![cochrane](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cochrane/32/10441_2.png) [@cochrane](https://boards.straightdope.com/u/cochrane)\ **Post date:** [December 7, 2018, 3:18am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/23 "2018-12-07T03:18:43Z")
> [@AncientHumanoid](#): > > Is this some kind of bust, or what? Nice beaver! ---
**Author:** ![TubaDiva](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tubadiva/32/507_2.png) [@TubaDiva](https://boards.straightdope.com/u/TubaDiva)\ **Post date:** [December 7, 2018, 3:21am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/24 "2018-12-07T03:21:53Z")
I’ve contacted Sun-Times management to let them know about this issue. (Sorry I didn’t see this earlier, I was playing a Christmas concert this evening. 'Tis the season and all that.) Hoping for a quick resolution to this problem. Jenny your humble TubaDiva Administrator ---
**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, 3:35am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/25 "2018-12-07T03:35:44Z")
It’s already fixed. ---
**Author:** ![TubaDiva](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tubadiva/32/507_2.png) [@TubaDiva](https://boards.straightdope.com/u/TubaDiva)\ **Post date:** [December 7, 2018, 3:45am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/26 "2018-12-07T03:45:47Z")
All right then! Jenny your humble TubaDiva Administrator ---
**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, 5:42am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/27 "2018-12-07T05:42:25Z")
> [@AncientHumanoid](#): > > Is this some kind of bust, or what? If you were asking me, umm, no it wasn’t. ---
**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, 6:35am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/28 "2018-12-07T06:35:55Z")
Now I’m left to wonder how it got fixed. If Tuba didn’t contact anyone, how did whoever needed to renew/replace the certificate find out? Are there some tech elves in the background who don’t have an account? Or was the problem actually on the issuer’s side, and the certificate renewal had been paid for, but they forgot to actually renew it? I note the issuer path looks different now, with 5 nodes instead of 3. ---
**Author:** ![Terminus\_Est](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/terminus_est/32/3087_2.png) [@Terminus\_Est](https://boards.straightdope.com/u/Terminus_Est)\ **Post date:** [December 7, 2018, 6:59am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/29 "2018-12-07T06:59:06Z")
If it’s already fixed, why does Chrome still say “Site Not Secure” for me? I don’t get the big scary warning page, but all SDMB still goes to “http” rather than “https”. That is, the URLs still properly say “https” but they all automatically redirect to “http”. ---
**Author:** ![SenorBeef](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/senorbeef/32/2220_2.png) [@SenorBeef](https://boards.straightdope.com/u/SenorBeef)\ **Post date:** [December 7, 2018, 7:17am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/30 "2018-12-07T07:17:01Z")
> [@Melbourne](#): > > 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. What’s the case against HTTPS? ---
**Author:** ![rat\_avatar](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rat_avatar/32/255_2.png) [@rat\_avatar](https://boards.straightdope.com/u/rat_avatar)\ **Post date:** [December 7, 2018, 7:28am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/31 "2018-12-07T07:28:04Z")
> [@SenorBeef](#): > > What’s the case against HTTPS? None really, especially after July of this year as chrome now properly marks _all_ HTTP sites as “not secure”. I would be that several users on here use the same password on this site on other more critical websites. HTTP means you are broadcasting this password to anyone who cares to look. ---
**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, 7:59am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/32 "2018-12-07T07:59:42Z")
> [@BigT](#): > > Now I’m left to wonder how it got fixed. If Tuba didn’t contact anyone, how did whoever needed to renew/replace the certificate find out? Are there some tech elves in the background who don’t have an account? Further up in the thread (post #8 at 6:29 pm) Bone said that he had emailed the tech people. Tuba didn’t show up until 9:21 pm. ---
**Author:** ![Terminus\_Est](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/terminus_est/32/3087_2.png) [@Terminus\_Est](https://boards.straightdope.com/u/Terminus_Est)\ **Post date:** [December 7, 2018, 11:04am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/33 "2018-12-07T11:04:16Z")
> [@Terminus\_Est](#): > > If it’s already fixed, why does Chrome still say “Site Not Secure” for me? I don’t get the big scary warning page, but all SDMB still goes to “http” rather than “https”. That is, the URLs still properly say “https” but they all automatically redirect to “http”. OK, this seems to have fixed itself on my end. ---
**Author:** ![ftg](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ftg/32/2801_2.png) [@ftg](https://boards.straightdope.com/u/ftg)\ **Post date:** [December 7, 2018, 8:29pm UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/34 "2018-12-07T20:29:15Z")
Several references to _Airplane!_ but none to the most natural one? This certificate is no more! It has ceased to be! It’s expired and gone to meet its maker! … THIS IS AN EX-CERTIFICATE! Well, I’d better replace it, then. ---
**Author:** ![TubaDiva](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tubadiva/32/507_2.png) [@TubaDiva](https://boards.straightdope.com/u/TubaDiva)\ **Post date:** [December 7, 2018, 9:15pm UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/35 "2018-12-07T21:15:25Z")
Sorry for the inconvenience; it was in process earlier in the day on Thursday and was thought handled. Not sure what transpired but then it wasn’t and now it is for sure and the system reset. We should be good to go now. Jenny your humble TubaDiva Administrator ---
**Author:** ![AncientHumanoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ancienthumanoid/32/278_2.png) [@AncientHumanoid](https://boards.straightdope.com/u/AncientHumanoid)\ **Post date:** [December 8, 2018, 2:01am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/36 "2018-12-08T02:01:51Z")
Mine wasn’t an Airplane ref. 😉 ---
**Author:** ![Melbourne](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Melbourne](https://boards.straightdope.com/u/Melbourne)\ **Post date:** [December 8, 2018, 4:03am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/37 "2018-12-08T04:03:58Z")
> [@SenorBeef](#): > > What’s the case against HTTPS? Get off my Lawn. Oh, you mean apart from that? I work with small HTTP systems. Moving to HTTPS means moving to a processor that costs 10 times as much, with 100 times as much memory. Out of which we get worthless security and still require a VPN, because actual security would require even more memory, more development costs, and would still be unfit for purpose. It means old web browsers don’t work, which means that old operating systems don’t work. It means that caching doesn’t work. These are trivial objections, but it means that the whole ecosystem, which was working perfectly well, has to be discarded. It’s like being told that your 30 year old car, that you’ve lovingly maintained by hand, has to be discarded because you can’t get replacement windshield wipers anymore. It’s particularly galling because it’s being driven by the big advertising and data mining companies. ---
**Author:** ![DooWahDiddy](https://avatars.discourse-cdn.com/v4/letter/d/e9bcb4/32.png) [@DooWahDiddy](https://boards.straightdope.com/u/DooWahDiddy)\ **Post date:** [December 8, 2018, 4:37am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/38 "2018-12-08T04:37:37Z")
> [@ftg](#): > > Several references to _Airplane!_ but none to the most natural one? > > This certificate is no more! It has ceased to be! It’s expired and gone to meet its maker! … THIS IS AN EX-CERTIFICATE! > > Well, I’d better replace it, then. > [@AncientHumanoid](#): > > Mine wasn’t an Airplane ref. 😉 Neither was his. 😃 ---
**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 10, 2018, 2:50am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/39 "2018-12-10T02:50:59Z")
> [@Melbourne](#): > > Get off my Lawn. > > Oh, you mean apart from that? I work with small HTTP systems. Moving to HTTPS means moving to a processor that costs 10 times as much, with 100 times as much memory. Out of which we get worthless security and still require a VPN, because actual security would require even more memory, more development costs, and would still be unfit for purpose. It means old web browsers don’t work, which means that old operating systems don’t work. It means that caching doesn’t work. These are trivial objections, but it means that the whole ecosystem, which was working perfectly well, has to be discarded. It’s like being told that your 30 year old car, that you’ve lovingly maintained by hand, has to be discarded because you can’t get replacement windshield wipers anymore. > > It’s particularly galling because it’s being driven by the big advertising and data mining companies. It also just adds extra complexity, meaning another thing that can go wrong, just like it did here. It makes sense that you want that for higher security sites, and can make at least some sense on any site with a login. But there are still purely passive, information only sites out there that would work fine on HTTP. The big thing that made me aware was trying what is mentioned in [this xkcd comic](https://xkcd.com/548/). I got an older Kindle that still uses cellular data. But it can’t handle HTTPS. So no Wikipedia for me–not even in read-only mode. I could at least read the Dope, but that’s gone now, too. (I did at least eventually find a few years old dump of Wikipedia available on HTTP, but the URL is annoying long.) I have noticed old browsers not being able to connect not because they don’t have HTTPS, but because they use an older, less secure form. That context doesn’t bother me as much, since you can usually upgrade to a better browser–for now. But when it’s a device, it kinda sucks. ---
**Author:** ![AncientHumanoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ancienthumanoid/32/278_2.png) [@AncientHumanoid](https://boards.straightdope.com/u/AncientHumanoid)\ **Post date:** [December 11, 2018, 2:14am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/40 "2018-12-11T02:14:43Z")
> [@DooWahDiddy](#): > > Neither was his. 😃 I know [Previous page](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722.md?page=1) [Next page](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722.md?page=3)