The fact that not everyone gets those warnings makes me wonder if it could be a weird caching issue. Browser aren’t supposed to cache certificates, but there’s a couple of comments in this thread on Super User that indicates maybe sometimes they do anyway.
I’ve alerted management to this situation again. They were looking at it yesterday. Guess they’re not finished.
Jenny
your humble TubaDiva
Administrator
Latest Chrome, updated Windows 10 Pro, no issues. But I am using a number of security add-ins, Trustwave, Privacy Badger, and Disconnect, which block a lot of malicious stuff.
Awright, which one of you goombahs told Google about the squid and the goat?
Things do appear to have resolved. I think they renewed the security certificate, but don’t quote me on that.
Sorry for the inconvenience.
Jenny
your humble TubaDiva
Administrator
SDMB opened today with no errors. Thanks!
Well, one could consider (insert the name of your favorite thread here) to be an error. But technically it looks to be working better. 
(In chrome) I’m still seeing the “not secure” prefix to the URL, and when I begin creating a post, like this one, it changes to red. Personally, I’m not worried, but others might not be so cavalier about it.
No, Jenny. We are sorry that we inconvenienced you.
Seriously…a big THANK YOU from all of us…for the work you put in every day to keep this place up and running.
(signed,
a couple of thousand Dopers.)
I’m still getting them. Do I have to like clear my cache or something?
Well, shucks. Now I’m getting Sultantheme’s skin AND a Not Secure warning.
I get the unsecured message on Firefox if I attempt login on a page not prefixed with ‘https’.
Actually the Security certificate is a really critical thing, so we did* her *a favor.
But we do appreciate her labors, too.
Maybe I spoke too soon (post #29). The problem now seems to be fixed and I don’t see any “not secure” messages in any color.
Has any of this resolved for you?
If any of you are still having difficulties with the site, please let me know. Say something here or send me an email tubadiva@aol.com
Jenny
your humble TubaDiva
Administrator
I still get the red slash through the lock on a page that doesn’t load as ‘https://’, and Firefox will prevent my login if I try. But if I get to a page that is secure and has a login button, I can and then all pages are secure.
How exactly are you getting to a page that loads as http instead of https?
For me it just seemed to randomly happen–but this was earlier when they were still trying to fix things, so I assumed it was a temporary thing.
As far as I am aware, all of the http vs https issues have been fixed (I don’t personally get to talk to the tech guys though). We shouldn’t be serving up any pages as http at this point. They should all be https.