Join the AMA (Ask Me Anything) with Firefox leadership team to talk about Firefox priorities in 2024. Mark your calendar! Thursday, June 13, 17:00 - 19:00 UTC.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Chase Account

more options

Firefox not working for one Chase account.

Message "It looks like this part of our site isn't working right now."

Works fine with Chrome.

Firefox not working for one Chase account. Message "It looks like this part of our site isn't working right now." Works fine with Chrome.

Athraithe ag r.zawacki ar

All Replies (1)

more options

Chase uses a lot of different server addresses, so my first thought is:

Firefox recently rolled out "Total Cookie Protection" to more users. This limits how sites can use "third party" or "cross-site" cookies, meaning cookies from different websites than the one you see in the address bar. If you notice that there is a different address in the address bar between the main bank server and the sign-in page, or between the sign-in page and the online banking area, then this cookie restriction could break the connection.

You can make exceptions to this feature when needed by turning off Enhanced Tracking Protection on each different Chase server that you end up getting switched to. More info in the following articles:

Does that work for you?