Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

Upgrading from 35 to 36 caused secure connection failed errors

  • 1 vastaus
  • 61 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja richpjr

richpjr
richpjr
more options

We have a couple of different applications that our customers suddenly are having issues with on a pair of load balanced web servers after they upgrade to version 36 of Firefox. It worked fine in 35 and still works in Chrome and IE. The error only happens on certain pages within the sites. The exact error is this: 

Secure Connection Failed

The connection to the server was reset while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

The exact same apps work fine on other servers with version 36, so I’m guessing it is some kind of a certificate/cipher issue with the server or load balancer. I have searched for this message and see others have similar issues when attempting to upload files but the pages failing don't have any file uploads on them. Any suggestions on what to look at?

We have a couple of different applications that our customers suddenly are having issues with on a pair of load balanced web servers after they upgrade to version 36 of Firefox. It worked fine in 35 and still works in Chrome and IE. The error only happens on certain pages within the sites. The exact error is this: Secure Connection Failed The connection to the server was reset while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. The exact same apps work fine on other servers with version 36, so I’m guessing it is some kind of a certificate/cipher issue with the server or load balancer. I have searched for this message and see others have similar issues when attempting to upload files but the pages failing don't have any file uploads on them. Any suggestions on what to look at?

Valittu ratkaisu

After spending some more time browsing around on the forums, I stumbled on this thread:

https://support.mozilla.org/en-US/questions/1050465

We changed the max parse length parameter to 65535 in our Cisco ACE20-MOD-K9 load balancer and this solved the issue:

parameter-map type http HTTP-PARAM-MAP set header-maxparse-length 65535 length-exceed continue

Lue tämä vastaus kontekstissaan 👍 4

Kaikki vastaukset (1)

richpjr
richpjr Kysymyksen kysyjä
more options

Valittu ratkaisu

After spending some more time browsing around on the forums, I stumbled on this thread:

https://support.mozilla.org/en-US/questions/1050465

We changed the max parse length parameter to 65535 in our Cisco ACE20-MOD-K9 load balancer and this solved the issue:

parameter-map type http HTTP-PARAM-MAP set header-maxparse-length 65535 length-exceed continue

Muokattu , muokkaaja richpjr