this post was submitted on 21 Dec 2023
8 points (100.0% liked)
techsupport
2450 readers
16 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The Jellyfin community here is !jellyfin@lemmy.ml
The official forum is at https://forum.jellyfin.org/
What you've got seems to be a truenas specific docker problem.
When you spin up Jellyfin docker, you normally specify a config volume and a data volume, so that as you upgrade, the users and watched lists etc are maintained.
You should be able to save those directories, delete the broken Jellyfin docker instance, and then recreate it pointing at the old volumes.
That way it would bind to the valid IP, but have the old configs and data.
At the command line I could help, but I don't know anything about Truenas sorry.