This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Buscar en Ayuda

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

Can't login to usaa.com banking site. FF keeps refreshing login page

  • 6 respuestas
  • 1 tiene este problema
  • 1 visita
  • Última respuesta de jenna

more options

Can't login to usaa.com banking site. keeps refreshing login page Using FF desktop latest ver. / win 7

I enter/submit my USAA username on the login page via a username dialog box. I then expect the password dialog box to open, but when I submit the username, FF flashes, i.e. the password dialog box displays for a split second and reverts right back to the username dialog box.

This happens at usaa.com with my user agent set to Windows/FF v 113. BUT if I set the user agent to Android/phone FF v 113, USAA detects the browser as Android/phone FF and it redirects to user agent to https://mobile.usaa.com where I AM able to enter username/password and login.

So what is wrong with FF? There are multiple threads of users unable to login to banking and other sites on the FF browser.

Can't login to usaa.com banking site. keeps refreshing login page Using FF desktop latest ver. / win 7 I enter/submit my USAA username on the login page via a username dialog box. I then expect the password dialog box to open, but when I submit the username, FF flashes, i.e. the password dialog box displays for a split second and reverts right back to the username dialog box. This happens at usaa.com with my user agent set to Windows/FF v 113. BUT if I set the user agent to Android/phone FF v 113, USAA detects the browser as Android/phone FF and it redirects to user agent to https://mobile.usaa.com where I AM able to enter username/password and login. So what is wrong with FF? There are multiple threads of users unable to login to banking and other sites on the FF browser.

Solución elegida

I had to create a new profile and it worked. TY

Leer esta respuesta en su contexto 👍 0

Todas las respuestas (6)

more options

Here's one potential issue:

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. Some sites pass you back and forth between different servers during login because they have their services spread out over a number of different servers. In those cases, you might be able to submit a form successfully on one page and then the next page says you are not logged in. Frustrating!

You can make exceptions to this feature when needed (for each server that you visit as part of the process of using this company's services). More info in the following articles:

Any difference with USAA or bank sites that have given you trouble?

more options

TY I tried all the suggestions in the articles including disabling ETP and also disabling TCP without disabling ETP. They did not resolve the issue.

USAA is the only banking site I use and its the only site I use that gives me this problem while user agent is in windows (non-mobile device) mode.

Anything else I can try?

more options

You can check the Web Console for relevant-looking (cookie) messages..

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block content (Adblock Plus, NoScript, DuckDuckGo PE, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block content.

Firefox shows a purple shield instead of a gray shield at the left end of the location/address bar in case Enhanced Tracking Protection is blocking content.

  • click the shield icon for more detail and possibly disable the protection

You can check the Web Console for relevant-looking messages about blocked content.


You can try these steps in case of issues with webpages:

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Settings).

"Remove the Cookies" for websites that cause problems:

  • Settings -> Privacy & Security
    Cookies and Site Data: "Manage Data"

"Clear the Cache":

  • Settings -> Privacy & Security
    Cookies and Site Data -> Clear Data -> [X] Cached Web Content -> Clear

Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or if userChrome.css/userContent.css is causing the problem.

  • switch to the Default System theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window
more options

well nothing worked. Below is the console export. Unless something is obvious, I done trying.


Loading failed for the <script> with source “https://s.yimg.com/wi/ytc.js”. www.usaa.com:1:1 Content Security Policy: This site (https://www.usaa.com) has a Report-Only policy without a report URI. CSP will not block and cannot report violations of this policy. logon [NoScript]:0 Prompt Hook installation https://www.usaa.com/my/logon?logoffjump=true&wa_ref=pub_global_log_on log.js:32:13 Some cookies are misusing the recommended “SameSite“ attribute 41 Loading failed for the <script> with source “https://tags.tiqcdn.com/dle/usaa/nw/ent-unified-logon-web.js”. logon:1:1 unreachable code after return statement ShQjblA:1:192936 Use of the orientation sensor is deprecated. ShQjblA:1:164147 Use of the motion sensor is deprecated. ShQjblA:1:164266 InstallTrigger is deprecated and will be removed in the future. ShQjblA:1:100397 WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. ShQjblA:1:73395 asm.js type error: Asm.js optimizer disabled because debugger is active utag.318.js ReferenceError: can't access lexical declaration 'prop' before initialization 1f2786a5-c164-4171-8ab6-df909349f739:131:35 Uncaught DOMException: An exception was thrown

   RpD https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   lPD https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   pDD https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   setTimeout handler*RDD/pDD< https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   jN https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   dN https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   pDD https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   RDD https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   sNSZxjXWHR https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1
   <anonymous> https://www.usaa.com/XW_NUgG3/3Ol/E06/HmtO66s3Zg/OwD7bhz2wN/Qi94XQE/Gkt6/ShQjblA:1

ShQjblA:1 Content-Security-Policy warnings 2 Request to access cookie or storage on “https://d.agkn.com/iframe/9297/?amcid=85050974443661965617743969256703669999&type=1000&che=0.9445161824647351” was blocked because it came from a tracker and content blocking is enabled. ReferenceError: overrideNavigatorData is not defined bb3eae9a-4714-4532-8e9e-64f65f19ada9:4:4 Cookie “TAPID” has been rejected for invalid domain. i.gif [NoScript]:0 Prompt Hook installation https://d.agkn.com/iframe/9297/?amcid=85050974443661965617743969256703669999&type=1000&che=0.9445161824647351 log.js:32:13 Content Security Policy: The page’s settings blocked the loading of a resource at data: (“media-src”). 4 9297 Cookie “TAPID” has been rejected for invalid domain. i.gif Request to access cookie or storage on “https://di.rlcdn.com/api/segment?pid=712517&pdata=Enterprise%3Dent_ent_visit_rtg” was blocked because it came from a tracker and content blocking is enabled. Cookie “TAPID” has been rejected for invalid domain. 2 i.gif Content-Security-Policy warnings 2 Request to access cookie or storage on “https://d.agkn.com/iframe/9297/?amcid=85050974443661965617743969256703669999&type=1000&che=0.1351536444804805” was blocked because it came from a tracker and content blocking is enabled. ReferenceError: overrideNavigatorData is not defined bb3eae9a-4714-4532-8e9e-64f65f19ada9:4:4 [NoScript]:0 Prompt Hook installation https://d.agkn.com/iframe/9297/?amcid=85050974443661965617743969256703669999&type=1000&che=0.1351536444804805 log.js:32:13 Content Security Policy: The page’s settings blocked the loading of a resource at data: (“media-src”). 4 9297 Cookie “TAPID” has been rejected for invalid domain. 2 i.gif Cookie “TAPID” has been rejected for invalid domain. 2 i.gif Content-Security-Policy warnings 2 Request to access cookie or storage on “https://d.agkn.com/iframe/9297/?amcid=85050974443661965617743969256703669999&type=1000&che=0.7288218913768002” was blocked because it came from a tracker and content blocking is enabled. ReferenceError: overrideNavigatorData is not defined bb3eae9a-4714-4532-8e9e-64f65f19ada9:4:4 [NoScript]:0 Prompt Hook installation https://d.agkn.com/iframe/9297/?amcid=85050974443661965617743969256703669999&type=1000&che=0.7288218913768002 log.js:32:13 Content Security Policy: The page’s settings blocked the loading of a resource at data: (“media-src”). 4 9297

more options

This issue can be caused by corrupted cookies or blocked cookies.

You can create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

If the new profile works, you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

more options

Solución elegida

I had to create a new profile and it worked. TY