Never had that problem on this site but I have on others. I can access them fine with Internet Explorer so I'm guessing it's a Firefox bug.
Well I've had a back-and-forth with the mod and their conclusion was that the problem is somehow on my side. It's not just firefox, it's also Google Chrome. Now, maybe it is possible that I managed to overlook it for a year, but that would be one major oversight. It started happening on the day I posted it and I had not updated anything, added any add-ons, etc. I also have repeatedly been scanning my entire system for viruses, adware, etc, and nothing has been coming up. My only program installations around the date this happened were 1/19/17 (and I logged on many times) and 2/1/17. I fail to see how it could possibly be on my end, in light of that.
The warning I'm getting when logging into https is that although Firefox has blocked some content, part of the page is not secure, such as images. It then sends me to this place for "more info":
https://support.mozilla.org/en-US/k...-secure-affect-my-safety&utm_source=inproduct
(When I say "warning", I'm not talking about something flashing on the screen. I'm talking about the information available when you click on the shield or (i) button in Firefox, immediately to the left of the address. With Google Chrome it's just an (i))
Google chrome says "Attackers might be able to see the images you’re looking at on this site and trick you by modifying them." More info says "This page is not secure". It says the certificate is fine, but there are two warnings.
1. "Mixed Content" The site includes http resources. I can then click "view requests in Network Panel" which tells me there are "4 errors and 20 warnings", but I'm only somewhat skilled with "computer stuff" so I cannot make too much sense of the specific details. ie, if I then click on "Console" menu within this "view requests in Network Panel", I get stuff like: _____________
2index.php:42 A Parser-blocking, cross-origin script,
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/connection/connection-min.js?v=423, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See
https://www.chromestatus.com/feature/5718547946799104 for more details. (anonymous) @ index.php:42 index.php:1 Mixed Content: The page at 'https://www.debatepolitics.com/index.php' was loaded over HTTPS, but requested an insecure script 'http://www.debatepolitics.com/clientscript/vbulletin-core.js?v=423'. This request has been blocked; the content must be served over HTTPS. 2index.php:135 A Parser-blocking, cross-origin script,
https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build/animation/animation-min.js?v=423, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See
https://www.chromestatus.com/feature/5718547946799104 for more details. (anonymous) @ index.php:135 index.php:1 Mixed Content: The page at 'https://www.debatepolitics.com/index.php' was loaded over HTTPS, but requested an insecure script 'http://www.debatepolitics.com/clientscript/vbulletin-sidebar.js?v=423'. This request has been blocked; the content must be served over HTTPS.
______
2. Obsolete Connection Settings The connection to this site uses an obsolete protocol (TLS 1.0), an obsolete key exchange (RSA), and an obsolete cipher (AES_128_CBC with HMAC-SHA1).
I wasn't so much concerned with problems resulting from the site itself. I was more concerned that perhaps someone managed to hack into the site or introduce malware in some way. A disgruntled banned poster, for example. The server upgrade apparently isn't until 2 am on Sunday, so I suppose I'll have to wait and see whether this stuff goes away.
I dunno...
Oh, right. See the separations between lines and paragraphs in this post? Well, when I first posted it, every single thing I had typed was put into one single run-on paragraph. I had to go back in, edit it, and add in lines. None of this stuff seemed to happen before.
(I did update OSX on 2/1/17, 10.11.6, but as you can see above, the OP is from 1/30/17).