When shopping web sites utilizing Firefox, when you discover a lot of the net hyperlinks blocked, and also you obtain an error code SSL ERROR NO CYPHER OVERLAP, then there’s a downside with one of many SSL / TLS settings in the browser. You must examine on few settings round TLS/ SSL to repair this error in Firefox.
Close all of the tabs you’re engaged on, and save all of your work. Next, open a brand new TAB, and kind about: config to open settings of Firefox. If you get a warning, settle for it. The subsequent display will show all of the configuration settings.
Reset TLS Settings
1] In the search field above the checklist, sort TLS. This will reveal all of the settings which have TLS configuration. TLS stands for Transport layer socket.
2] Search for any settings which have a worth showing in BOLD. If sure, it signifies that the setting has been modified. To restore it again to default settings, proper click on on it, and select Reset.
Reset SSL Settings
1] Repeat the search in about: config with SSL3. Look for configuration which has been modified i.e. they may seem in daring.
2] Right click on on these settings, after which reset it. You also can double-click to revive to default settings. However, the 2 settings wanted to be blocked to enhance safety. Set them to false.
Interesting reality: These two are associated to the favored Logjam vulnerability which appeared three years in the past.
Change TLS Version Fallback
Changing TLS model to bypass is a superb choice, however keep warned that you must do not do it for each web site.
- In the about: config part of Firefox, seek for safety.tls.model.fallback-limit.
- Change the worth to zero.
- Repeat this for safety.tls.model.min and set worth to zero.
- Check when you can entry the web site.
Warning: Changing these values will make your browser much less safe. So do it if it is extremely obligatory. Make positive to reset it later.
Server Side Problem
If that is occurring with one explicit web site solely, its a server facet subject. Only, the server admin can resolve the problem. This principally occurs when a web site continues to be utilizing RC4-Only Cipher Suite, and the settings in the server ‘safety.tls.unrestricted_rc4_fallback’ desire is toggled to false.
We have observed this error reported at instances, for varied web sites together with Cloudfare, Sonicwall, Tomcat, IMGUR, Amazon and so forth.