This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Is there a way to add a website to SSL 3.0 trust?

  • 1 freagra
  • 9 leis an bhfadhb seo
  • 3 views
  • Freagra is déanaí ó cor-el

more options

I use Tomato firmware on my Linksys router and recently I started getting the following error when I attempt to access my routers web interface using Firefox 32 and 33: ________________ Secure Connection Failed An error occurred during a connection to 192.168.1.1. SSL peer rejected a handshake message for unacceptable content. (Error code: ssl_error_illegal_parameter_alert)

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

________________ Tomato uses a self-signed SSL - Tomato Firmware v1.28.1816.

I use Tomato firmware on my Linksys router and recently I started getting the following error when I attempt to access my routers web interface using Firefox 32 and 33: ________________ Secure Connection Failed An error occurred during a connection to 192.168.1.1. SSL peer rejected a handshake message for unacceptable content. (Error code: ssl_error_illegal_parameter_alert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. ________________ Tomato uses a self-signed SSL - Tomato Firmware v1.28.1816.

All Replies (1)

more options

Issues with connecting to secure sites in Firefox 31 and later can be caused by switching to libPKIX.

Support for the security.use_mozillapkix_verification pref to disable PKIX has been removed in Firefox 33.