Bug: PPP passwords (or what) need to match (I found the cause...)
-
I see this posted a dozen+ times, and it's always "Can't Reproduce". Well I can send you the HTML pages the software has rendered- but making any changes to the WAN interface throws errors about the passwords not matching.
NOW- I do believe this is the root cause: Chrome's password manager is sticking in 'admin' and some passwords into the fields. And since pfSense is serving those pages but not rendering them, they get stuck in the (and not visible).
The fix? Going into the Developer Tools and literally deleting all the DIV tags associated with those (PPP, PPoE, etc). Once I did that, the assignment changes worked perfectly.
I hope this is enough to finally be able to reproduce this bug and (perhaps) fix it.
Again, it's if you've saved any passwords for the site that you're on- Chrome will attempt to fill in those fields. The DHCP tab doesn't show the PPP information, but Chrome populates the password fields with the saved password for the pfSense site.
"PPP Password and confirm password must match"
-
I can confirm this. Removing all stored passwords for the firewall UI site from the Chrome autocomplete cache avoided the PPP password mismatch error when trying to configure a new vlan interface.
2.4.4-RELEASE (amd64)
built on Thu Sep 20 09:03:12 EDT 2018
FreeBSD 11.2-RELEASE-p3Chrome Version 86.0.4240.75 (Official Build) (64-bit)
-
@alancdavis said in Bug: PPP passwords (or what) need to match (I found the cause...):
2.4.4-RELEASE (amd64)
Upgrade.
@purduephotog said in Bug: PPP passwords (or what) need to match (I found the cause...):
Chrome
Reserved for 'end-users'.
Most of us have no time to deal with this, as we still suffer from the 'IE' experience. Once is enough ;) -
If I may suggest, don't use chrome, opera, edge, just use Firefox.
-
@AKEGEC said in Bug: PPP passwords (or what) need to match (I found the cause...):
If I may suggest, don't use chrome, opera, edge, just use Firefox.
So.... install a new browser to fix the behavior. That's ... just wrong.
Perhaps pick more unique field names?
-
So you're basically saying Chrome is auto-filling hidden password fields creating the input validation error?
That should be fixed in 2.4.5p1 by this: https://redmine.pfsense.org/issues/9864
So, yeah, upgrade!
Steve