Why is Firefox 68 flagging my https site as 'using weak encryption' and says Connection is not secure?
When I navigate to sites we host that have an SSL certificate installed, I get a yellow exclamation point icon over the top of the padlock, clicking it shows the message under CONNECTION.. Connection is not secure and This page uses weak encryption. Clicking into the Connection and choosing more information shows the security details.
Chosen solution
Even the www subdomain is a disaster: https://www.ssllabs.com/ssltest/analyze.html?d=www.channelready.com
I think someone must have made a configuration error on the server at some point. Or hacked.
Read this answer in context 👍 0All Replies (7)
As you can see, your site is using TLS 1.0, which is pretty much considered a broken encryption standard at this point.
You can see a complete list of all the problems with this site's encryption at https://www.ssllabs.com/ssltest/analyze.html?d=dms.channelready.com
and
https://observatory.mozilla.org/analyze/dms.channelready.com
Basically, the site is vulnerable to a multitude of attacks and should be fixed ASAP
Chosen Solution
Even the www subdomain is a disaster: https://www.ssllabs.com/ssltest/analyze.html?d=www.channelready.com
I think someone must have made a configuration error on the server at some point. Or hacked.
Hello Jefferson, I think we know each other from a previous forum called Woody's Lounge :)
I'm having this exact issue with Spiceworks on our internal network. I didn't see a posted resolution, is this a web server configuration issue (in my case Apache)? Interestingly, IE does not exhibit this behavior, and although I can't test with Chrome I suspect it wouldn't either.
Hi Mark, long time.
If you open the Page Info dialog using either:
- right-click > View Page Info
- (menu bar) Tools > Page Info
Then switch over to the Security panel, there is a little summary at the bottom showing the cipher and protocol. Apparently one of those is on the older side and Firefox is warning that it no longer provides good assurances of privacy.
Tyler mentioned that you may see this for TLS 1.0 connections. The current best practice is to use TLS 1.2 as a minimum.
Thank you for the information! Older and wiser, we are. I did some digging on the offending server and found that the Apache httpd.conf file had an entry enabling all TLS versions, which I modified as follows:
SSLProtocol -All +TLSv1 +TLSv1.1 +TLSv1.2
became
SSLProtocol -ALL +SSLv3 +TLSv1.2
I used this reference to verify how to modify the configuration file, problem now resolved after an Apache restart. We're all happy with a green padlock in Firefox now.
Mark, thanks for the update. I sincerely hope none of your browsers still connect using SSLv3!
I hope not either, I'll be removing that SSL entry after hours, I forgot to mention to my boss that I was tweaking the site and it was noticed... no more changes for the duration of the business day!