SOLVED: Unable to sign in after creating a new container with the same appdata path

[cavmot]

I was hoping you'd have a log file that was created right after starting up the new instance.  Would that have been on the 22nd?  The log you shared is entirely from the 23rd.  And it is definitely re-ingesting your entire library as if it was a new install.

You may need to re-enable the startup wizard to re-set the credentials.

Navigate to where /config is mounted and open /config/config/system.xml.  Change "IsStartupWizardComplete" from true to false, restart Jellyfin.  When you go to Jellyfin it should walk you through the initial setup process.  Set your credentials, skip the rest (click next until done).

Unfortunately that log file is the most recent one I have. I did spin it up on the 22nd but the logs from before the 23rd seem to have been deleted.

I tried changing the startup wizard config as well, but ended up with the same result

At this point, I'm thinking I'll just spin up the container again as if it were fresh then copy over whatever frontend files I can.