This thread was archived. Please ask a new question if you need help.
why all of sudden is Firefox saying my bank configuration is not secure and won't let me in?
two complaints that I have and hope to get them solved before I leave.
First issue is this, I have used Wa Trust bank always even before Firefox and just yesterday it came back saying their website is not secure. This problem is obviously a Firefox problem!!( and I had to go to Internet Explorer to log into Wa Trust to pay my bills.A totally frustrated day I had.
Secondly Fire fox will not let use my Amazon Prime to watch movies which is another total frustration , there must be a way to fix that. It would be these two issues that will cause me to go to another Web Browser. Hope to hear back from you with Good News of your fixing these issues Thanks Rose
All Replies (2)
Hi Rose, your browser mentioned that it was running on a very old version of Windows (NT 4.0) that Firefox can't run on. If your Firefox is set to use compatibility options, can you turn those off, then exit Firefox and test the problem sites again? Here's where you do that -- either:
- Desktop shortcut: right-click the icon, choose Properties
- Pinned taskbar icon: right-click the icon, right-click Mozilla Firefox, choose Properties
Windows normally will select the Shortcut tab. Click the Compatibility tab. For best results, make sure no checkboxes are checked here. (Example screenshot attached.)
I have used Wa Trust bank always even before Firefox and just yesterday it came back saying their website is not secure. This problem is obviously a Firefox problem!!
First, I just want to clarify: when Firefox cannot form a secure connection with a server, that is not an indication that a site is unsafe, it is an indication that the server failed to prove to Firefox's requirements that it actually is the site you want to reach. It could be a fake, or it could have obsolete security which Firefox considers insecure, or there could be a "man in the middle" reading all your communications with that server. You should never need to make exceptions for well run sites.
Okay, now, to figure out what the problem is. Could you copy/paste the text from the error page in a reply. If there is an Advanced button, please click that and copy the more technical explanation there, too.