Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Secure Connection Failed Error code: SSL_ERROR_PROTOCOL_VERSION_ALERT

  • 3 biyano
  • 1 eza na nkokoso oyo
  • 52 views
  • Eyano yasuka ya Paul

more options

I tried to connect to a website and I received the message in the subject. I have been connecting to that web site for months on Firefox with no trouble. I connected without problems using Firefox just yesterday. After the Firefox problem, I connected without problems to the same web address using Microsoft Edge. I don't understand why Firefox suddenly has this problem.

I tried to connect to a website and I received the message in the subject. I have been connecting to that web site for months on Firefox with no trouble. I connected without problems using Firefox just yesterday. After the Firefox problem, I connected without problems to the same web address using Microsoft Edge. I don't understand why Firefox suddenly has this problem.

All Replies (3)

more options

That error would suggest that the server only supports TLS 1.0/1.1 and not newer TLS versions, current releases require TLS 1.2 or 1.3.

What are the security.tls.version prefs set to?

  • security.tls.version.max 4
  • security.tls.version.min 3

You can open the about:config page via the location/address bar. On the warning page, you can click "Accept the Risk and Continue" to open about:config.

more options

I have not checked the security.tls.version prefs. What puzzles me is that I could connect to that web site with no trouble for several months, as recently as yesterday. I made no changes to the security prefs. Perhaps an even greater puzzle is that I tried to connect to the web site again about half an hour ago, and this time the error message did not appear. Again, this happened without me making any changes to Firefox prefs. In any case,the problem has gone away.

more options

Thank you for letting us know.