Hi, are there any other details to the message? In particular, if you see an error code in ALL_CAPS, that could point toward the problem.

Also, it appears you are using the Beta/Developer release of Firefox 103. Was Firefox 102 able to connect to the router?

Thank you for answer. Yes, Error code: SSL_ERROR_UNSUPPORTED_VERSION No other browsers allow me to access the router. I talked to the internet service provider and they say that the problem is not with them, that they allow access. With previous versions of Firefox (I don't know exactly what number) I was able to access it.

Okay, I have a theory.

Most browsers have discontinued support for two older connection protocols: TLS 1.0 and TLS 1.1. Possibly your router's firmware hasn't been updated to support the TLS 1.2 protocol. If it's not a discontinued product, hopefully there is an update available to resolve the problem. In that case, you can install it to allow access from all of your browsers without reducing security.

The following thread describes how to roll back this security improvement in Firefox, BUT since it is global -- it is not just for one site/device -- it is better not to keep this change permanently after updating your router.

https://support.mozilla.org/questions/1379823

Thank you very much, your answer solved my problem

Remember that it is important for security reasons to keep those older protocols disabled.

TLS 1.0 and TLS 1.1 have been deprecated in current Firefox releases and have been disabled. You can still enable TLS 1.0/1.1 via about:config although this is not recommended and you should only flip the pref when you need to access this device/website and reset the pref to false once you are done with accessing this website.

• about:config => security.tls.version.enable-deprecated = true

See TLS version unsupported:

• https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect

I need a solution that doesn't disable the new TLS standards for all websites. Previously, Firefox would let me choose to access the website anyway, and then created a security certificate for that specific website. Other site were not affected.

I have an Arris Surfboard Gateway, model SBG6700-AC, which is a modem integrated with a 2-port router and wifi. Their website says they have no firmware or security updates. I accessed the Arris Web Manager with a Firefox bookmark for "http://192.168.0.1/home.asp". Now it works only if I go to about:config and roll back the values for TLS.

Firefox needs to restore the feature for creating exceptions. If they think it's unsafe, they should at least allow exceptions to addresses for devices on my Local Network.

That would be Mozilla as Firefox is the name of the desktop web browser.

https://hacks.mozilla.org/2020/02/its-the-boot-for-tls-1-0-and-tls-1-1/

Now it works only if I go to about:config and roll back the values for TLS. Firefox needs to restore the feature for creating exceptions.

I don't think Firefox ever had a feature for creating exceptions to the minimum TLS protocol -- it was never needed before. Firefox allowed and still allows exceptions for certificates that can't be validated, assuming the site doesn't require strict transport security. That's probably what you have in mind.

"I don't think Firefox ever had a feature for creating exceptions to the minimum TLS protocol -- it was never needed before. Firefox allowed and still allows exceptions for certificates that can't be validated, assuming the site doesn't require strict transport security. That's probably what you have in mind."

I may not have described it properly, but such a feature existed. When you received a security warning, Firefox would ask if you wanted to accept the risk and proceed. The button that let you do that has been removed.

"I don't think Firefox ever had a feature for creating exceptions to the minimum TLS protocol -- it was never needed before. Firefox allowed and still allows exceptions for certificates that can't be validated, assuming the site doesn't require strict transport security. That's probably what you have in mind." I may not have described it properly, but such a feature existed. When you received a security warning, Firefox would ask if you wanted to accept the risk and proceed. The button that let you do that has been removed.

It depends on the reason for the problem. Here's an example of a problem where an exception is allowed:

https://self-signed.badssl.com/ (test site, not dangerous)

But protocol and cipher errors come before Firefox even looks at the certificate, so a certificate exception is not applicable.