Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

Upgrading from 35 to 36 caused secure connection failed errors

  • 1 ответ
  • 61 имеет эту проблему
  • 1 просмотр
  • Последний ответ от 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?

Выбранное решение

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

Прочитайте этот ответ в контексте 👍 4

Все ответы (1)

more options

Выбранное решение

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

Изменено richpjr