cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

VANGUARD no longer works in FireFox

Julie713
Making moves

As of January 6, 2026, I can no longer get into Vanguard. My correct username and password return as incorrect. Works fine in Chrome.

3 REPLIES 3

tcostin
Making moves

Had the same problem.  The same VALID vanguard userid and Password works in Chrome but gets rejected as invalid by Vanguard in Firefox.  I was using a userid saved in Firefox.  I think the problem is that Firefox is not sending the userid that you see in the box if it is a prefilled value.  If you erase the pre-filled user id and type in the userid manually, then it works.  Firefox might be sending a blank userid to Vanguard instead of the prefilled userid.  I would not trust any prefilled values in Firefox right now. This worked recently. In my opinion, someone made a change to the way Firefox uses saved values to prefill forms and introduced a bug.  The change was not properly tested.  -Tim C

dholbert
Employee
Employee

Hi! I'm able to reproduce this, and my theory is that it's a problem where Firefox is filling the username/password right away as soon as those fields appear in the page, which happens to be before Vanguard is "ready" those fields to get a value (and so Vanguard gets confused because some part of their logic doesn't realize that a username/password has been entered yet, or something along those lines).

 

I found one workaround that works for me - could you check if this works for you as well:

  1. Open Firefox preferences.
  2. Type "password" into the search field in the preferences page.
  3. Uncheck the box for "Fill usernames and passwords automatically"
  4. Now, go to the Vanguard login page, click the username field -- a dropdown menu should appear, and choose the username that you've saved. This should fill the password field as well.
  5. Click "Log in"

This works for me -- does it work for you as well?

dholbert
Employee
Employee

(Also, I filed https://bugzilla.mozilla.org/show_bug.cgi?id=2010147 to track this issue in mozilla's bug-tracker.)