We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Error connecting to intranet site - ssl_error_illegal_parameter_alert

  • 2 replies
  • 5 have this problem
  • 1 view
  • Last reply by lzzlong

lzzlong
lzzlong
more options

Since updating to Firefox 35, some (not all) of my firm's intranet sites do not load. The most relevant post (https://support.mozilla.org/en-US/questions/1041524) is not helpful since, like the person reporting this issue, our firm only supports IE for internal sites. How can I bypass this error for intranet sites (I no longer see this option)?

An error occurred during a connection to <intranet site>. 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.
Since updating to Firefox 35, some (not all) of my firm's intranet sites do not load. The most relevant post (https://support.mozilla.org/en-US/questions/1041524) is not helpful since, like the person reporting this issue, our firm only supports IE for internal sites. How can I bypass this error for intranet sites (I no longer see this option)? An error occurred during a connection to <intranet site>. 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.

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The website might be using a cipher suit that is no longer considered secure and safe and is blocked in current releases.

You can open the about:config page via the location/address bar and use its search bar to locate this pref:

  • security.tls.insecure_fallback_hosts

You can double-click the line to modify the pref and add the domain to this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). You should only see domains separated by a comma in the value column.

lzzlong
lzzlong Question owner
more options

This did not work; I also tried changing the "network.websocket.allowInsecureFromHTTPS" setting from false to true, but this also did not work.