Forum and site maintenance

Jeremy Collake · March 30, 2015, 07:57:35 PM

There may be sporadic service disruptions as the servers are reconfigured to be more scalable to handle larger loads.

parkd1 · March 31, 2015, 12:58:29 PM

You should check this out. I am running Fire Fox Nightly build 40.0a1 64bit.

Jeremy Collake · March 31, 2015, 01:44:44 PM

We had a temporary misconfig with our renewed SSL cert.

Chrome and IE accepted it fine. No warnings of any kind. All valid. Locked. So, I didn't think to check Firefox.

Apparently Firefox has become more strict given recent SSL vulnerabilities. This is all very interesting to me, as I would not expect 1 of 3 major browsers to fail, while the others succeed with flying colors.

ANYWAY, it should be fixed now. Please verify. This was the last thing I needed (downtime or lost traffic), but I had to renew the SSL cert. Naturally, after verifying with everything BUT Firefox, I went to sleep. Murphy's Law.

parkd1 · March 31, 2015, 02:28:01 PM

Ok that seems to work. Thanks.

edkiefer · March 31, 2015, 03:42:26 PM

ok, this might sound like dumb question, but i to got the above message, I ok'ed "i know the risk" and it added a extempt somewhere .

now if I want to put back what do I do ?
I looked at security certs and under server there is one bitsum listed under trustwave and is up to date, under authorities there is a bisum which is expired (2013) under bitsum tech , I assume delete this or is it somewhere else ?

Jeremy Collake · March 31, 2015, 03:44:56 PM

No action necessary, I dont think. It probably did not install any new root CA, or add any permanent exemption, it just let you on through to bitsum.com.

parkd1 · March 31, 2015, 03:49:07 PM

Did that too and then deleted what your talking about and seems to be fine.

Jeremy Collake · March 31, 2015, 03:59:13 PM

Yea, it's definitely good, but if there was a permanent exemption added - well, first, it'd still show the site as insecure at the top - but please tell Ed where he can find said setting if you get time. I'm no Firefox user, so don't know off-hand.

edkiefer · March 31, 2015, 04:28:07 PM

ok, well I will delete the old one as it says expired .

I don't get the warning any more, just one time .

Edit: Ok ,deleted old cert and seem fine.
restarted Palemoon (FF based ) , all good .

parkd1 · March 31, 2015, 06:40:18 PM

I did not not check to see if it was an old one. I just added when ask the deleted it. Ok go to options the click on advanced on the left of the screen. Then there will be tabs on the top of the screen and click on certificates. Then you will see a tabs called view certificates. That will pull up a window and you I looked at security certs and under server there is one bitsum listed under trustwave and is up to date, under authorities there is a bisum which is expired (2013) under bitsum tech , I assume delete this or is it somewhere else. That is where I found it too. Think we had the same one maybe. I deleted it like you did and it is working fine.

edkiefer · March 31, 2015, 06:56:54 PM

Yes, I am not sure that was cause , but can't hurt to remove old one that expired .

Jeremy Collake · April 01, 2015, 02:00:13 PM

Thank god this didn't persist for too long. Man, yearly SSL certs, and all other certs, are being monopolized these days. Symantec has bought out up most all of the root cert signers, which means they'll then increase prices even higher than they are now. We pay a lot for our code signing, in addition to SSL.

edkiefer · April 01, 2015, 02:12:48 PM

I don't think it was very long time , I always have this site up if I am running anything , so i noticed it .

Jeremy Collake · April 03, 2015, 09:52:32 AM

It was certainly less than 12 hours.