+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Unable to sign in after creating a new container with the same appdata path (/t-solved-unable-to-sign-in-after-creating-a-new-container-with-the-same-appdata-path)
Unable to sign in after creating a new container with the same appdata path - cavmot - 2025-01-23
I am running an unraid server and I recently added second cache drive to my array for cache mirroring. This had the unfortunate side effect of deleting all of my docker containers. However, I made sure to save everything from the cache drive, so all of the appdata is still there. I just tried redownloading jellyfin as a new container from the unraid apps tab, and pointed the appdata path to the same folder that it was at before. It started up and I can tell it's using the correct appdata folder because all of my theme changes are still there. However, I am unable to sign in with any profile. I had it set so that you could click your profile to sign into it, but none of them are showing anymore, so I have a feeling they aren't there or something. If anyone has a solution to this that isn't starting from scratch, it would be a big help. Thanks.
RE: Unable to sign in after creating a new container with the same appdata path - TheDreadPirate - 2025-01-23
When you say "Docker container", do you mean you use the actual docker functionality built into unRAID to run Jellyfin?
Then you say you added Jellyfin from unRAID's app tab. What I'm wondering is whether the "app" uses the same directory structure and/or the same based Jellyfin image as what you had before.
Because it sounds like you WERE using a different image than what the unRAID "app" uses. The linuxserver image for Jellyfin and the official Jellyfin image have slightly different directory structures and are not 100% interchangable. If this is what is happening then that would explain why it kind of works, but mostly not.
RE: Unable to sign in after creating a new container with the same appdata path - cavmot - 2025-01-23
(2025-01-23, 01:38 PM)TheDreadPirate Wrote: When you say "Docker container", do you mean you use the actual docker functionality built into unRAID to run Jellyfin?
Then you say you added Jellyfin from unRAID's app tab. What I'm wondering is whether the "app" uses the same directory structure and/or the same based Jellyfin image as what you had before.
Because it sounds like you WERE using a different image than what the unRAID "app" uses. The linuxserver image for Jellyfin and the official Jellyfin image have slightly different directory structures and are not 100% interchangable. If this is what is happening then that would explain why it kind of works, but mostly not.
I used the unraid apps tab for my jellyfin container both times. I also made sure to use the same container image that I used before, which is the one marked as official.
RE: Unable to sign in after creating a new container with the same appdata path - TheDreadPirate - 2025-01-23
And you've tried clearing your browser cache? Can you share the jellyfin logs via privatebin.net?
RE: Unable to sign in after creating a new container with the same appdata path - cavmot - 2025-01-23
Actually I have not tried clearing my browser cache so it could be that simple. I will try that later once I get home and if that doesn’t work I will share my logs.
RE: Unable to sign in after creating a new container with the same appdata path - cavmot - 2025-01-24
(2025-01-23, 05:16 PM)TheDreadPirate Wrote: And you've tried clearing your browser cache? Can you share the jellyfin logs via privatebin.net?
Yeah so clearing browser cache didn't do anything. Here is the latest log: https://privatebin.net/?7e586816a16e00a5#HMukmgK4MgomJka92iofU4Tx41H3isMKa31T6uWd3Fr2
RE: Unable to sign in after creating a new container with the same appdata path - TheDreadPirate - 2025-01-24
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).
RE: Unable to sign in after creating a new container with the same appdata path - cavmot - 2025-01-26
(2025-01-24, 01:51 PM)TheDreadPirate Wrote: 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.
RE: Unable to sign in after creating a new container with the same appdata path - cavmot - 2025-01-26
(2025-01-24, 01:51 PM)TheDreadPirate Wrote: 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).
NEVERMIND changing the startup wizard config option did work, there was just some saving desync between my client and server. Thanks!