Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

SSL connection error since update of firefox

  • 1 回覆
  • 4 有這個問題
  • 1 次檢視
  • 最近回覆由 cor-el

more options

Since upgrading to firefox 37, navigating to URL www.jncb.com/internetbanking.php?RetailLogin results in the error below being displayed:

Secure Connection Failed

An error occurred during a connection to retail.ncbelink.com. SSL received a record with an incorrect Message Authentication Code. (Error code: ssl_error_bad_mac_read)

I am a member of staff at the company that runs the website and seeking ant clues as to what is required to resolve the issue permanently for users.

Since upgrading to firefox 37, navigating to URL www.jncb.com/internetbanking.php?RetailLogin results in the error below being displayed: Secure Connection Failed An error occurred during a connection to retail.ncbelink.com. SSL received a record with an incorrect Message Authentication Code. (Error code: ssl_error_bad_mac_read) I am a member of staff at the company that runs the website and seeking ant clues as to what is required to resolve the issue permanently for users.

所有回覆 (1)

more options

The website may try to fallback to TLS 1.0 in a way that is no longer allowed in current releases.

  • Connection Encrypted (TLS_RSA_WITH_AES_256_CBC_SHA, 256 bit keys, TLS 1.0)

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.

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.