How Do I Diagnose This SSL Error?

The following steps will help you diagnose the SSL errors you receive in Chrome.Firstly, after going to the site which generates the error, press the F12 key to bring up the Chrome DevTools. Select the Security tab item to see more about the certificate and the SSL connection:If there's a problem, it will be highlighted in Red. In this case, the certificate is signed with the weak, deprecated SHA-1 algorithm:If the error complains about the certificate in some way, you can click on View Certificate to get more information. For example, it's good to check the Certification Path to make sure the certificate appears to be legitimate:If you'd like to learn what effect the different "bad" configurations will have on Chrome, you can explore the sites from Bad SSL:

I followed the suggestions in this discussion for diagnosing a client-side SSL error, but I don't know how to interpret the result.

The openssl command for www.plex.tv returns a good certificate. But when I try to login at Chrome strikes out the https and shows "Not Secure." I get an error message when I proceed to login. This happens on Firefox as well as Chrome, and it happens from any computer on my home network. I am able to login from an android phone over the cellular network.

FYI I ran the SSL command on a Synology NAS which also runs on my home network.

If it was an ISP problem, wouldn't the openssl command return a bad certificate?

·OTHER ANSWER:

I followed the suggestions in this discussion for diagnosing a client-side SSL error, but I don't know how to interpret the result.

The openssl command for www.plex.tv returns a good certificate. But when I try to login at Chrome strikes out the https and shows "Not Secure." I get an error message when I proceed to login. This happens on Firefox as well as Chrome, and it happens from any computer on my home network. I am able to login from an android phone over the cellular network.

FYI I ran the SSL command on a Synology NAS which also runs on my home network.

If it was an ISP problem, wouldn't the openssl command return a bad certificate?