Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

SSL connection error since update of firefox

  • 1 antwurd
  • 4 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan cor-el

iamsbee
iamsbee
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.

Alle antwurden (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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.