Hi,

It sounds like the Bank of America login page isn’t accepting input in the password field when using Firefox. Since it works in Chromium, this points to a Firefox-specific issue, likely related to site compatibility, cached data, or extensions. Here’s how to troubleshoot:

Clear site data for BofA

Go to Settings → Privacy & Security → Cookies and Site Data → Manage Data…

Search for bankofamerica.com and remove its data.

Restart Firefox and try again.

Disable extensions / test in Troubleshoot Mode

Menu ≡ → Help → Troubleshoot Mode.

This disables all extensions and custom settings. If the password field works here, an extension may be interfering.

Check Enhanced Tracking Protection (ETP)

Click the shield icon in the address bar and turn off ETP for the site temporarily.

Some banking sites block certain scripts when ETP is on, which can prevent typing in fields.

Hope this helps!!

I tried all the steps. No luck! At the last one the BoA login page gave me "warning-icon You are using an unsupported browser version". My version is Firefox 142. The BoS supported browsers page https://www.bankofamerica.com/information/supported-browsers/ does not include the Ubuntu Linux operating system.

Hi,

Thanks for trying all the steps and for the additional details.

From what you’ve described, the Bank of America login page is now showing a “unsupported browser version” warning. This is likely due to two factors:

You’re using Firefox 142. BoA’s site may require a newer version of Firefox to be supported.

BoA’s supported browsers page does not list Ubuntu Linux, which likely contributes to the warning and the login page not accepting your credentials.

Because the site explicitly limits supported OSes and browsers, this issue is outside of Firefox itself.

Hope this helps!

How can I upgrade Firefox installed in Ubuntu 24.04 from snap? I can find advice for APT but not snap.

Hi,

Since your Firefox on Ubuntu 24.04 was installed via Snap, updating it works a little differently from the usual APT method. Snap updates Firefox automatically in the background, but you can also refresh it manually if needed.

Here’s how:

Make sure that Firefox is completely closed.

Open the Terminal: Press Ctrl+Alt+T to open a terminal window.

Run the Refresh Command: Type the following command and press Enter

sudo snap refresh

After, it will ask for your password and the command will check for and install any available updates for all your Snap packages, including Firefox.

Hope this helps!!

I updated Firefox which is now version 143. (I had to find a kill two apps that did not go away when I closed Firefox.) I still can't log in to BoA.

Hi,

Thanks for updating Firefox to 143. Since you’re still seeing the login issue with Bank of America, it’s likely caused by Ubuntu/Linux not being officially supported by BoA for their web banking, rather than your Firefox version. The “unsupported browser” warning confirms this.

Try using a supported OS/browser combination (Windows, macOS, or mobile) for BoA web login.

I can log in using Firefox on my Android 10 phone. Also, as I said, using Chromium on my Ubuntu desktop. It used to work not long ago on my desktop in Firefox. I guess we can't consider this a solved problem. Thanks.

Hi,

Thanks for the update. Since Firefox on Ubuntu still isn’t working while other browsers and devices do, it does seem like a compatibility issue between BoA’s site and Firefox on Linux, even though it used to work. Unfortunately, this isn’t something we can fix from the Firefox side.

For now, the safest options are to continue using a supported browser like Chromium on Ubuntu or Firefox on Android for BoA access. You could also consider submitting feedback directly to Bank of America—they may update their site to better support Linux browsers in the future.

Sorry for this issue! I wish I can help more.

Feedback links on the BoA login page are old history. The agent I talked to today had no clue, other than to try a different browser. If you know of a better way I'll be glad to try it.

I think that Mozilla should consider this an issue for them.

Well, I gave you all my suggestions and it didn't seem to work.. So you should file a bug report to Bugzilla so Mozilla engineers can track whether it’s a Firefox compatibility issue.

Please let me know if you need any help in filing a bug report!

You are very kind. The reported bugs at https://bugzilla.mozilla.org/show_bug.cgi?id=572626 and https://bugzilla.mozilla.org/show_bug.cgi?id=1892540 seem relevant. Both are marked a 'resolved' so how would I describe this problem as a new bug? Thanks!

The literal stated purpose of the "modern web" was to remove the "browser wars" and all websites follow the same standards.

google however, has used its monopoly position to create their own standards and force users to switch browsers due to things like this.

You could try changing the user agent string to tell the BOA site that the browser is chrome and not FIrefox.

To do so, go to about:config and then create a new preference of type string with a value of "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36"

If that resolves the problem, Firefox is being directly targeted, possibly by a google api.

A website not working with an up to date Firefox is in violation of the "modern web" which has agreed upon standards to be followed by all browsers.

I do not recommend switching browsers or OS because a website or api is not following the rules.

Submitted Bug 1990072

I am using Bank of America and Firefox 142. I uuse Linux Mint 21.3, and therefore do not use the Snap store. I have had no issue with Firefox accessing secure.bankofamerica.com.

Is it possible that Firefox from Snap is the issue? I update Firefox through my repositories in the Software Center. (I have 143 awaiting installation on my next update.)

I don't think so. I've been using Ubuntu 24.04 with Firefox 142 installed from snap for about a year. I upgraded to 143 two days ago to see if that would fix the problem. I haven't tried the suggestion yesterday from Somebody. Out of curiosity I may do that when I have some time but first let's see what the response is to the bug report. It's better for everyone if Mozilla can fix it.