new install today, working fine, but now admin is not recognized as a user name

I have InfluxDB OSS 2.7.8 just installed earlier today on a Raspberry Pi 64 OS.

Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

It had been working fine but now I've gotten into a state where when I try to sign in to the UI, it says "Could not sign in" in a red box in the upper right. I also noticed in trying to reset the password using the CLI that it says it doesn't recognize the user named "admin" but if I enter in the ID for the user "admin" it does recognize it.

I've tried resetting the password a few times via the CLI. It doesn't work if I user the "--name admin" but when I do "influx user list" it shows admin as the only login. As I said, I can use the ID number associated with the "admin" name and it will let me reset the password using:
influx user password --id

but that password doesn't work in the UI. Likely because it's not recognizing the username admin (edited)

After I installed it, I was able to sign in via the UI several times throughout the day up until this issue arose.

These are the error lines that show up when I check the status of the influx service:
Aug 06 18:55:27 BelfastTideStation influxd-systemd-start.sh[2665]: ts=2024-08-06T22:55:27.279527Z lvl=info msg=Unauthorized log_id=0qrO6lll000
error="token required"
Aug 06 18:55:37 BelfastTideStation influxd-systemd-start.sh[2665]: ts=2024-08-06T22:55:37.231174Z lvl=error msg="api error encountered" log_id
=0qrO6lll000 handler=session error="unauthorized access" (edited)

Somemore info:

"influx list users" returns:
ID Name
0d7642ac0bc52000 admin

"influx list users --name admin" returns:
Error: failed to list users: 404 Not Found: user not found

"iinflux user list --id 0d7642ac0bc52000" returns:
ID Name
0d7642ac0bc52000 admin

So somehow it's gotten into a state where the user name 'admin' isn't recognized despite still be associated with a working ID.

Start with the UI sign-in flow and the CLI `influx user list --name admin` and `--id` behavior, then compare the service's unauthorized logs. Done means the `admin` name resolves consistently and the UI accepts the reset password.

Written by the indexing model from the issue text.