techsupport

2490 readers

31 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:

You Should Know

Software gore

Recommendations

founded 2 years ago

MODERATORS

GatoB

Jellyfin docker trying to use a nonexistent IP adress (self.techsupport)

submitted 11 months ago by KpntAutismus to c/techsupport

2 comments fedilink hide all child comments

hey guys,

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!

top 2 comments

sorted by: hot top controversial new old

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

There is a jellyfin community on lemmy, you can try to ask there: [email protected]

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

The Jellyfin community here is [email protected]

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.