This thread was archived. Please ask a new question if you need help.
Firefox not supported by financial institutions on Mac?
I learned the hard way about a month ago that my main bank will not work with firefox. I've now received notices from two other banks that state they only support safari on Mac. I have run into issues with some others that will either give errors but still allow me to pass through or others that state I have an unsupported browser but still allow me to log into the site - for now.
With this wide a net, this seems to be specific to the security issues in the Mac browser. Is this already being looked into? Is this specific to the new OS and firefox integration?
While I basically trust Safari, I certainly don't want to use it unless I have to and I generally use firefox exclusively on all my Macs and PCs. Can someone shine a light on this? Is there an upgrade or update planned?
All Replies (9)
The only thing I had to do was set an Exception in Enhanced Tracking Protection for my financial institution -
Visit the site Click on the shield icon at the left end of the address bar Set the switch near the top to Off
If you save cookies and site data for the site this exception will be retained for future visits.
Thanks, but nope. Tried it. This isn't FF blocking the site - it's the site blocking FF function. As mentioned above other site will give errors but continue. This site just plain stalls as though the API is dead.
I'm going to attempt contacting someone at the bank who might know something (if I can work through their maze of support) to see if they have an answer. Don't even want to install it, but might try chrome to at least see if it works.
Try to install the 'User agent switcher' addon and introduce yourself as Chrome or safari on these websites.
Thanks for the suggestion but that did not help either. Did test it with an email client (which broke the login) so I know that it was working. MIght be useful in future for some things but not this.
Tried several combinations of browsers and restarted firefox several times as well. With two combinations it did give me an error code from their website instead of stalling, so that's something at least.
I completely agree. My curiosity lies in why they accept the Win version of Firefox but not Mac? I can't imagine that there's that much of a difference. I realize that Apple likely has some part (if not a large one) to play in this issue.
As it turns out, it just randomly started working again this afternoon after not connecting for three weeks. So something was sorted out. Again, not so much Mozilla's fault or issue, but I'm still curious why it might be one OS and not the other.
Seeing as it happens every once in a while and then seems to self-correct, and I'm getting these notices from the banks, It would be interesting to know why at the very least.
Thanks for chiming in.
Same here, I had to turn off ETP to access Synchrony Bank in Firefox. For Discover and WellsFargo Firefox works fine.
Modified by jonzn4SUSE
While Discover and Wells also still work for me, Discover and I believe Citi specifically sent a notice that excluded using firefox on Mac. I've had issue with Synchrony accounts from time to time and had to switch back to safari to access them when firefox would not work. 53 Bank works sporadically and will work at one time of the day and then stall or throw and error again later (or vice versa).
I don't have connection issues and it's not as though I'm doing any specific blocking from the machine or FF I'm using at the time.
Again, I'm more curious at this point why banks would single out FF on Mac vs FF on PC, or why it would run into issues - whether it was FF or related to the banks' coding.
I have raised this with our developers and it is something that they are aware of. The issue is not widespread and it is difficult trying to track it down.
Would you be interested in running some software on your computer that may help with this? It will not involve a remote connection or anyone taking control of your computer, but help to find what we need to resolve this issue.