What would make TrueNAS Core correct passwd not work?

Im noob with TrueNAS, but not noob with this kind of stuff. What could possibly make root passwrd not work for a few hours?

Im running TrueNAS Core on a Supermicro with two NICs. One NIC is for webUI the other is for everything else. Im accessing the webUI through reverse proxy on pfSense with an advanced setting of “timeout tunnel 1hr” and directly to the server using its IP address. I had 2FA enabled but my phone with GA, TrueNAS, and pfSense were all synced to the second using pfSense as NTP server on my LAN. I was trying to access on LAN and tried multiple computers (keyboards) since my 8 character password had $ @ in it. I tried logging in over IPMI on command line and webUI. I had console disabled without password so I couldnt reset root passwd. I restored from back up, no dice. I finely accepted the fact that I had to start over and went to reinstall a second time but it failed. I tried my passwd 3 more times out of anger in the command line and the 3rd time it let me in so I tried the webUI with 2FA and that also opened up for me leaving me scratching my head.

When I got inside all settings looked correct except for that webUI was set to wildcard instead of my 2nd NIC but Im not 100% sure I set that up before the backup was taken.

Anyone else had something like this happen?

Now after a reboot, 2FA enabled itself again, console is disabled again without login and my password doesnt work. WTF?

edit: OK figured it out. When I thought I reinstalled I really booted into a previous boot environment named initial-setup where I wasnt locked out which is why i could login. Then I restored with a back up and everything was good… but when I rebooted it reverted back to the locked out environment.

My 1st time with ZFS.

I haven’t seen so many issues like this. I don’t want to be that guy and say you misspelled your password wrong. If your password was the same and you tried it 3 times and it eventually worked then that has to be the only conclusion.

If you find that isn’t the case then you might have better luck submitting a ticket to ixsystems with all the logs with a detailed step by step to reproduce the issue.