Troubleshooting website display or functionality issues in Edge on Windows 10
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi There
I have the following problem, while accessing a website from a partner
Error Message:
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Unsupported protocol
The client and server don't support a common SSL protocol version or cipher suite.
Google Chrome lets me open the page, but tells me: "Your connection to this site is not fully secure".
I know, that the website uses an "outdated" security configuration. But this partner may not so fastly change that. Is there a possibility to tell Edge kind a list of websites, where he can ignore that? To disable this feature completely is not a solution in my opinion. (to manage a "whitelist also not, but it is the smaller pain)
Other suggestion? (other Browser is also no opinion and with Internet Explorer 11 it does not work :-( )
Kind Regards
David
Troubleshooting website display or functionality issues in Edge on Windows 10
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Many thanks.
Hi. Is there no way to go around this error. the sight that got this had some really important information on and i need to get it back.
thank you.
you can also continue by deleting the s from https:// and leaving just http:// in the address bar
Thanks, it is my ISP. I tried to access the WSJ website from two different ISP's and they both worked.
This is BS. I bought a new MS computer three weeks ago and was logging into my wall street journal account to read the publication on line then out of the blue I started to receive these messages:
Unsupported protocol The client and server don't support a common SSL protocol version or cipher suite.
This does not make any sense. Why would my MS system start to block this website without any prior issues?
Please tell your team to fix this!
CG
It might be your ISP, see my comments in a previous post.