Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox refuses to connect to my NAS admin page

more options

I have a (quite old) Iomega 2 NAS in my local network. I have to connect to the admin page to change some settings, but FF responds with SSL_ERROR_UNSUPPORTED_VERSION, with no option to bypass.

It's my own NAS, in my own local network. How can I bypass this (in this case stupid) restriction? I know it's safe, I know no harm can be done, still I can't get to this page.

I have a (quite old) Iomega 2 NAS in my local network. I have to connect to the admin page to change some settings, but FF responds with SSL_ERROR_UNSUPPORTED_VERSION, with no option to bypass. It's my own NAS, in my own local network. How can I bypass this (in this case stupid) restriction? I know it's safe, I know no harm can be done, still I can't get to this page.

선택된 해결법

I think that refers to the NAS's internal web server not supporting TLS 1.2; Firefox stopped connecting with TLS 1.0 or TLS 1.1 some time ago because they are not considered private any more. But you can reenable them if needed.

Unfortunately, Firefox doesn't have a method to only allow insecure protocols on your internal network, the following change will affect your web browsing as well. But maybe you only need it temporarily and then you can change it back?

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.

More info on about:config: Configuration Editor for Firefox. The moderators would like us to remind you that changes made through this back door aren't fully supported and aren't guaranteed to continue working in the future.

(2) In the search box in the page, type or paste security.tls.version.min and pause while the list is filtered

(3) Double-click the preference to display an editing field, and change the value to 1 then press Enter or click the blue check mark button to save the change.

To later restore the default value of 3, you can click the Reset button (left arching arrow) at the right end of the row.

If the device is SO OLD that it doesn't even support TLS 1.0, then you probably need to use Internet Explorer 11 to manage it. (Maybe there's a firmware update available.)

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (2)

more options

선택된 해결법

I think that refers to the NAS's internal web server not supporting TLS 1.2; Firefox stopped connecting with TLS 1.0 or TLS 1.1 some time ago because they are not considered private any more. But you can reenable them if needed.

Unfortunately, Firefox doesn't have a method to only allow insecure protocols on your internal network, the following change will affect your web browsing as well. But maybe you only need it temporarily and then you can change it back?

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.

More info on about:config: Configuration Editor for Firefox. The moderators would like us to remind you that changes made through this back door aren't fully supported and aren't guaranteed to continue working in the future.

(2) In the search box in the page, type or paste security.tls.version.min and pause while the list is filtered

(3) Double-click the preference to display an editing field, and change the value to 1 then press Enter or click the blue check mark button to save the change.

To later restore the default value of 3, you can click the Reset button (left arching arrow) at the right end of the row.

If the device is SO OLD that it doesn't even support TLS 1.0, then you probably need to use Internet Explorer 11 to manage it. (Maybe there's a firmware update available.)

more options

That did the trick, thank you very much!