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

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

Learn More

Secure Connection Failed since update 36.0.1

  • 1 ответ
  • 2 имеют эту проблему
  • 1 просмотр
  • Последний ответ от guigs

more options

Since the update to Firefox 36.0.1 on Windows 7 i'm getting the generic error 'Secure Connection Failed' when logging in to a website. It's an ASP.NET website that posts the form to the current page itself, only thing that the request is containing is a querystring parameter that contains a URL, analytics cookies and the two fields containing username and password (just alphanumeric characters).

The website is using a certificate expiring in 2017, 2048-bit key (saw that 1024-bit was deprecated in this release) using SHA-256 with RSA, TLS1.0 and the RC4 cipher. Also removed the cert8.db from the AppData-folder, like mentioned in the mozilla kb. The corporate network uses a firewall + virusscanner, to rule this out as cause i've tried it on a standalone environment without any of these and there it also shows the very same error. I've also the nightly build of 3/9/2015 and this one shows the same behaviour.

Anyone got some ideas how I can fix this issue?

Since the update to Firefox 36.0.1 on Windows 7 i'm getting the generic error 'Secure Connection Failed' when logging in to a website. It's an ASP.NET website that posts the form to the current page itself, only thing that the request is containing is a querystring parameter that contains a URL, analytics cookies and the two fields containing username and password (just alphanumeric characters). The website is using a certificate expiring in 2017, 2048-bit key (saw that 1024-bit was deprecated in this release) using SHA-256 with RSA, TLS1.0 and the RC4 cipher. Also removed the cert8.db from the AppData-folder, like mentioned in the mozilla kb. The corporate network uses a firewall + virusscanner, to rule this out as cause i've tried it on a standalone environment without any of these and there it also shows the very same error. I've also the nightly build of 3/9/2015 and this one shows the same behaviour. Anyone got some ideas how I can fix this issue?

Изменено ThomPuiman

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

more options