An error occurred during a connection to 10.71.100.16:8009. Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: rahulrx135, Unassigned)
Details
Attachments
(1 file)
|
319.36 KB,
image/jpeg
|
Details |
mozilla_bug.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36
Steps to reproduce:
I have tried to open the local page with URL https://10.71.100.16:8009
Actual results:
Secure Connection Failed
An error occurred during a connection to 10.71.100.16:8009. Cannot communicate securely with peer: no common encryption algorithm(s).
Error code: SSL_ERROR_NO_CYPHER_OVERLAP
Same URL is working with Chrome, IE brwosers but failing in mozilla
Expected results:
It should have navigated to login page
Hi Rahul
Its difficult for me to replicate the issue since your server is local and i can´t access it. Is there any link i could access to replicate the bug on my side?
The error 'SSL_NO_CYPHER_OVERLAP' occurs in Firefox when certain type of encryptions have been disabled either on the browser or in the server side. Mostly, the problem lies with the website or server which doesn't provide proper encryption protocols and forces the browser not to open the website. Or it can even be that firefox is not updated to the lastest version.
Please download Firefox Nightly from here: https://nightly.mozilla.org/ retest the problem and let us know if you still see the issue.
If you still have the issue please create a new profile, you have the steps here:https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager
Lastly test if the issue is reproducible in safe mode, here is a link that can help you:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Regards
Pablo
Marking this as Resolved-Incomplete due to the lack of response from the reporter.
If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information
Description
•