SOLVED: Fresh Setup with Container on Synology

SOLVED: Fresh Setup with Container on Synology - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Fresh Setup with Container on Synology (/t-solved-fresh-setup-with-container-on-synology)

Fresh Setup with Container on Synology - Generaldirektor - 2024-11-19

Hi all,

hope someone has an additional idea.

Problem: I am trying to create a fresh setup for Jellyfin using the Container Manager on Synology (which is actually Docker under the Hood, despite the new name)
When accessing the Jellyfin page I see that it offers to connect to the server but it is somehow an old entry since it wont connect. Adding a "new" Server connection works, but it requests a login (not a new registration) and although I have the user's credentials I used on my old setup, the login fails.

I already tried to stop and delete the container and also the image. Re-downloading the image and creating a new container shows the same result.
I then used the CLI (SSH on Terminal to Synology and switching to Root access and Sudo Shell) to dive deep into the docker folder.
Using

Code:
docker volume prune

to remove old subvolumes from previous containers removed a couple which had jellyfin references in it. But even when removing all of them, and then setting up a new container still shows the "old" server and asks for credentials where the credentials used last time, do not work anymore.

Where else can I find the remains of the previous installation to reset everything to a new start?
Or can I otherwise force the web access to show the initial setup wizard?

Best regards,

Generaldirektor

RE: Fresh Setup with Container on Synology - TheDreadPirate - 2024-11-19

Did you run "docker volume prune" while the Jellyfin container was stopped? Also, that command would only work if the Jellyfin /config and /cache volumes were created and managed by docker. If you provided a host volume for /config, it would not get pruned with the prune command you used.

RE: Fresh Setup with Container on Synology - Generaldirektor - 2024-11-19

Sorry, forgot to mention.
Yes, I created both /cache and /config outside of docker and linked them during container creation.
Yes, Container was stopped when cleaning up volumes.

Also, both /config and /cache have been empty when setting up the new container.

RE: Fresh Setup with Container on Synology - TheDreadPirate - 2024-11-19

If that is the case, make sure you clear your browser cache. Jellyfin caches aggressively in your browser.

RE: Fresh Setup with Container on Synology - Generaldirektor - 2024-11-19

Yes, that helped!
Thanks for this tip, didn't think about caching.