Cannot log into webConfigurator from Firefox/Linux after fresh install
- Install pfSense 2.4.2 from scratch.
- Assign interfaces, configure an IP address and DHCP server for the LAN interface.
- Open webConfigurator from a PC on the LAN network (via HTTP and the IP address).
- The login page appears.
- When I enter the default credentials and click Sign In, the text boxes are cleared and I get the same login page again; no error message is displayed.
- The system beeps and reports a successful login on the console.
- webConfigurator loading after supplying correct credentials.
- Server side: pfSense 2.4.2, AMD 64, serial console, installed via USB Memstick installer on ALIX hardware
- Client side: Ubuntu MATE 16.04, Firefox 58.0.2
- When I enter an incorrect password, the login page displays Username or Password incorrect in the top bar; this does not happen with the correct credentials. Also, login attempts with incorrect credentials are logged as such on the console.
- I was able to log into webConfigurator from a Windows 7 PC, also running Firefox 58.0.2.
- I then restored the configuration from my previous 2.2.6 setup, which contains SSL certs and blocks HTTP access to webConfigurator. After that, login from the Linux machine worked as well.
#3 Updated by Michael von Glasow over 1 year ago
I would agree about this being a client side issue if logins were to fail for every web site I visit. However, this is not the case—pfSense so far has been the only place which had this issue.
Most likely the cause lies somewhere in the interaction between the two systems. Maybe the response from pfSense is botched and other browsers are just more tolerant of it, or maybe it is indeed a bug in the browser. Or something in between—we just don’t know until we investigate.
Would it help if I filed a bug for Firefox?
#4 Updated by Jim Pingle over 1 year ago
Until it's proven to be a bug on pfSense (after discussion on the forum, subreddit, etc) then it doesn't belong here. It's not clear if it's a Firefox issue, specifically, either.
We use lots of Linux desktops and VMs internally and use new installs constantly for testing. If it was broken in this way, there would be many, many instances of failure that we could reproduce. It is undoubtedly something local to you, but you need to discuss it in a discussion platform to narrow down possible causes.