![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Why did I get a TLS error message with Firefox but was successful when switching to Internet Explorer?
I was making an online transaction, pressed "go" (or its equivalent) and received TLS connection failed message.
I switched to Internet Explorer and "go" went ok first time.
Penyelesaian terpilih
Firefox recently removed support for some outdated, insecure versions of TLS. You should contact the owners of the website to ask them to upgrade to a newer version. Other browsers also plan to remove support for these versions in the future as well.
Baca jawapan ini dalam konteks 👍 8All Replies (4)
Penyelesaian Terpilih
Firefox recently removed support for some outdated, insecure versions of TLS. You should contact the owners of the website to ask them to upgrade to a newer version. Other browsers also plan to remove support for these versions in the future as well.
The website may try to fallback to TLS 1.0 in a way that is no longer allowed in current releases or may be using a deprecated cipher suite.
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 full domain (TEXT) 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.
If this helps then you can contact this website and ask them to look into this.
Thank you both for your replies.
My user name of Thickoff was the nearest I could get to Thicko (sadly already taken) in recognition of my limited IT skills and comprehensive capabilities.
As such I can cope with user293's reply but am somewhat in awe of cor-el's reply!
The website in question is that of one of the UK's largest banks - I wonder if they will take any notice of me when I contact them?!
Thanks again for the replies
The website need to fix this and update their security to support TLS 1.2, so you ill have to contact them by email or phone.