Firefox Troubleshooting
Error Codes
SSL_ERROR_NO_CYPHER_OVERLAP
This is the same as ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome or EdgeHere's the output of sslscan for a website that was throwing this error...
sslscan thestudiopiercing.co.uk
Connected to 81.130.111.239
Testing SSL server thestudiopiercing.co.uk on port 443 using SNI name thestudiopiercing.co.uk
SSL/TLS Protocols:SSLv2 disabledSSLv3 disabledTLSv1.0 disabledTLSv1.1 disabledTLSv1.2 disabledTLSv1.3 disabled
TLS Fallback SCSV:Connection failed - unable to determine TLS Fallback SCSV support
TLS renegotiation:Session renegotiation not supported
TLS Compression:OpenSSL version does not support compressionRebuild with zlib1g-dev package for zlib support
Heartbleed:
Supported Server Cipher(s):Certificate information cannot be retrieved.
Here's the output for a site that was working...
sslscan superuser.com
Connected to 151.101.129.69
Testing SSL server superuser.com on port 443 using SNI name superuser.com
SSL/TLS Protocols:SSLv2 disabledSSLv3 disabledTLSv1.0 disabledTLSv1.1 disabledTLSv1.2 enabledTLSv1.3 disabled
TLS Fallback SCSV:Server supports TLS Fallback SCSV
TLS renegotiation:Session renegotiation not supported
TLS Compression:OpenSSL version does not support compressionRebuild with zlib1g-dev package for zlib support
Heartbleed:TLSv1.2 not vulnerable to heartbleed
Supported Server Cipher(s):Preferred TLSv1.2 128 bits ECDHE-RSA-AES128-GCM-SHA256 Curve 25519 DHE 253Accepted TLSv1.2 256 bits ECDHE-RSA-AES256-GCM-SHA384 Curve 25519 DHE 253Accepted TLSv1.2 256 bits ECDHE-RSA-CHACHA20-POLY1305 Curve 25519 DHE 253Accepted TLSv1.2 128 bits ECDHE-RSA-AES128-SHA256 Curve 25519 DHE 253Accepted TLSv1.2 256 bits ECDHE-RSA-AES256-SHA384 Curve 25519 DHE 253Accepted TLSv1.2 128 bits ECDHE-RSA-AES128-SHA Curve 25519 DHE 253Accepted TLSv1.2 256 bits ECDHE-RSA-AES256-SHA Curve 25519 DHE 253Accepted TLSv1.2 128 bits AES128-GCM-SHA256 Accepted TLSv1.2 128 bits AES128-SHA Accepted TLSv1.2 256 bits AES256-SHA
Server Key Exchange Group(s):TLSv1.2 128 bits secp256r1 (NIST P-256)TLSv1.2 192 bits secp384r1 (NIST P-384)TLSv1.2 260 bits secp521r1 (NIST P-521)TLSv1.2 128 bits x25519TLSv1.2 224 bits x448
SSL Certificate:Signature Algorithm: sha256WithRSAEncryptionRSA Key Strength: 2048
Subject: *.stackexchange.comAltnames: DNS:*.askubuntu.com, DNS:*.blogoverflow.com, DNS:*.mathoverflow.net, DNS:*.meta.stackexchange.com, DNS:*.meta.stackoverflow.com, DNS:*.serverfault.com, DNS:*.sstatic.net, DNS:*.stackexchange.com, DNS:*.stackoverflow.com, DNS:*.stackoverflow.email, DNS:*.stackoverflowteams.com, DNS:*.superuser.com, DNS:askubuntu.com, DNS:blogoverflow.com, DNS:mathoverflow.net, DNS:openid.stackauth.com, DNS:serverfault.com, DNS:sstatic.net, DNS:stackapps.com, DNS:stackauth.com, DNS:stackexchange.com, DNS:stackoverflow.blog, DNS:stackoverflow.com, DNS:stackoverflow.email, DNS:stackoverflowteams.com, DNS:stacksnippets.net, DNS:superuser.comIssuer: R3
Not valid before: Feb 13 13:16:03 2023 GMTNot valid after: May 14 13:16:02 2023 GMT
The first problem here seems to be that an SSL connection is made based on the client listing available ciphers and the server picking one. If there is no match then we can't make the connection to see which ciphers the server supports. One workaround for this is to use the SSL Labs Server Test to retrieve the list of available ciphers.
Let's see which ciphers our client has...
openssl ciphers -s -stdname
So, the issue would appear not to be with the ciphers available... so why do browser connections and sslscan fail?
In this case the site was blocked by plusnet Safeguard (although I have no explanation why it caused this error rather than the standard "blocked by Safeguard" message).