i have an old pc running truenas scale and a jellyfin app/docker at home. And i have recently replaced my router. Due to this, the IP adress of my truenass install changed, and i’m fine with that. But the Jellyfin docker tries to start up, but there’s only a couple lines in the shell:

„WARNING: Your user does not have sudo privileges so /usr/local/bin/k3s command will run on your behalf. This might cause permission issues.

Error from server: error dialing backend: x509: certificate is valid for 127.0.0.1, 0.0.0.0, 192.168.50.9, not 192.168.178.38“

the second line is what really concerns me. It seems that jellyfin is trying to use its old IP adress, but Truenas is telling it it can’t. I cannot interact with the docker through truenas’ shell and i am by no means an expert on linux-based stuff.

Is there a way to point it to its new IP adress, or am i better off making a new jellyfin install. I’d like to avoid the latter, because last time it took at least 5 hours to et it up and scann all of the files.

if you have a community that this post would fit better in, feel free to tell me.

Thanks for your help in advance!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 11 months ago

I've had similar issues with TrueNAS over the years. My solution was always to just remake the container but that is a hassle. I did that probably 3 or 4 times while I used TrueNAS which eventually led to me switching to a standard Ubuntu server install.