搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Is anyone else experiencing problems with their https connection to their Hardware. I am getting false positives stopping access to Hardware TLS

more options

Accessing some of my Hardware to make changes has become impossible with the latest attempt to secure TLS or Weak SSL certificates. I cannot access my Modem via https://192.168.1.1 as FF is not accepting the certificate from the device. This change is very new and not quite refined correctly yet I believe.

Accessing some of my Hardware to make changes has become impossible with the latest attempt to secure TLS or Weak SSL certificates. I cannot access my Modem via https://192.168.1.1 as FF is not accepting the certificate from the device. This change is very new and not quite refined correctly yet I believe.

被選擇的解決方法

Hmm, it sounds similar to:

You might have to use a different browser with the device for the time being. That also might make it easier to diagnose the situation, because the other browser probably can provide full certificate and connection details.

從原來的回覆中察看解決方案 👍 0

所有回覆 (5)

more options

Which of the many possible SSL error messages are you getting?

Also, to aid in searching for past threads, it would be great to know:

  • if an error code is indicated in parentheses on the error page, which code is it?
  • what kind of device is it (e.g., Linksys) if you're willing to disclose that?
more options

Secure Connection Failed

An error occurred during a connection to 192.168.1.1:1000. The server certificate included a public key that was too weak. (Error code: ssl_error_weak_server_cert_key)

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the web site owners to inform them of this problem.
more options

選擇的解決方法

Hmm, it sounds similar to:

You might have to use a different browser with the device for the time being. That also might make it easier to diagnose the situation, because the other browser probably can provide full certificate and connection details.

more options

Yes I am using a different Browser to solve the problem. From the small image below, sorry I cant capture much info here, you can see that the certificate store has accepted the certificate correctly. My mistake, I thought it wasnt there that said, if the certificate has been accepted, I cant understand why access isnt granted

more options

That's in Firefox's Certificate Manager dialog?

I'm not sure making an exception (or importing a certificate) in Firefox resolves every objection. I haven't run across any sites like this to experiment on.