[ButThreeLeftsDo]

I found one of the links where Jim explains the issue.

“The problem is that Google, and now possibly Firefox, are “deprecating” their support for industry standard SHA-1 certificates:

https://security.googleblog.com/2016/11/sha-1-certificates-in-chrome.html

John will eventually install a new SHA-2 certificate after he works out a couple other pressing issues, meanwhile, our SHA-1 certificate is current and is still valid (despite Google’s warning message) and our secure server continues to encrypt our transactions as before.

You can click “Advanced” at the bottom of the warning message and override Google’s erroneous “Not secure” message.

Or you can try a browser like Edge (default browser delivered with windows 10) and it works fine without the warning message.

Thank you very much.”

http://www.freerepublic.com/focus/bloggers/3531442/posts?page=7#7

[ConjunctionJunction]

Thanks!

[Jamestown1630]

Thanks for that. It has only happened that one time, when I used Firefox. Hasn’t happened, to me, with any other browsers.