Page 1 of 1

Board certificate change

Posted: Sun Apr 03, 2016 8:59 am
by Niacin
Help!

I just got this message on Firefox and now cannot access the forum. I can only use my phone

HTTP Strict Transport Security (HSTS) to specify that Firefox only connect to it securely. As a result, it is not possible to add an exception for this certificate.

Re: NOScript causing page reloads on OneDrive

Posted: Sun Apr 03, 2016 1:38 pm
by therube
There was an issue with a Certificate change here at the forums.

Re: Board certificate change

Posted: Sun Apr 03, 2016 2:00 pm
by barbaz
Splitting this to new thread to give it more visibility.

The board used to have a Comodo certificate now it has a Let's Encrypt certificate...
SHA-256 Fingerprint (of the new certificate):

Code: Select all

55:F4:43:31:ED:0E:F0:32:DD:75:7B:92:AD:F5:AB:88:84:79:A6:C4:3F:AE:AC:1A:82:2D:20:A2:32:DE:DA:F7
SHA-1 Fingerprint:

Code: Select all

77:A9:29:52:CF:2E:F0:AB:DB:DA:70:F0:00:73:A4:CA:FA:FF:79:75
(Why do I have no trouble accessing the board? Shouldn't I be hitting this issue?)

Re: Board certificate change

Posted: Sun Apr 03, 2016 4:59 pm
by therube
Maybe you were logged in, or at least had a page loaded from here, prior to the change, so you "session" persisted?

One Profile of mine, I could load the site (& I don't know that the above applied).
Two other Profiles, the regular one I come here with, & another, never visited before, neither could get in.
It wasn't until the Certificate expiration date was (again) changed that those Profiles worked.

Re: Board certificate change

Posted: Sun Apr 03, 2016 5:18 pm
by barbaz
therube wrote:Maybe you were logged in, or at least had a page loaded from here, prior to the change, so you "session" persisted?
No, my computer was shut down and I run SeaMonkey in a sandbox that gets dumped every time I quit. I also never automatically log in.
therube wrote:It wasn't until the Certificate expiration date was (again) changed that those Profiles worked.
Ah, that might explain it - so there was only a short window with a "wrong" certificate, and I likely didn't come here until after a new, correct certificate was put up. Thanks.