HELP! Jellyfin docker trying to use a nonexistent IP adress (lemmy.world)

submitted 11 months ago by KpntAutismus@lemmy.world to c/jellyfin@lemmy.ml

5 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 5 comments

sorted by: hot top controversial new old

[-] KpntAutismus@lemmy.world 5 points 10 months ago

I FIXED IT!!!

i went and made a new certificate, told the UI to use the new one, went into network->default route and typed in the ip of my router, and set the Published Server URL of jellyfin in the app settings to 192.168.50.10. now it's accessible again.

thanks for helping with this!

[-] digdilem@lemmy.ml 3 points 10 months ago

Ignoring first warning as a red herring.

The error though - that sounds like Jellyfin is contacting the right IP for Truenas, but Truenas is providing a cert for SSL using its old IP, and Jellyfin is refusing to talk to it since they don't match. ~

Fix might be to get Truenas to regenerate its SSL certs, which I assume are self generated.

Or force Truenas back on the old IP - you really want something like that to be on a static IP, or if it must be DHCP, to have a fixed reservation. Or have automatic DNS so that you don't use IPs at all, but that's usually a lot more faff. If it's not set to a single IP, you'll hit this problem repeatedly.

[-] KpntAutismus@lemmy.world 1 points 10 months ago

it has a fixed reservation, but the router will not let me do 178 at the third segment.

i will try to regenerate the certificates if i can find a tutorial.

to clarify: the old ip is 192.168.178.38, the new one is 192.168.50.9

[-] Voroxpete@sh.itjust.works 2 points 10 months ago* (last edited 10 months ago)

The reason you can't reserve an address with 178 in the third segment is because a) it's not in your DHCP reservation pool and b) it's not even in your network.

Most home routers use /24 networks (as a subnet mask this is given as 255.255.255.0). This describes how much of the IP address is the network, and how much is the device address. Think of this as like the area code in a phone number. Within a particular area code only the last seven digits change, because those are the digits assigned to individual devices. In most home networks, only the last quarter of the IP address changes (ie, everything after the last period). Changing anything in front of that means you're trying to dial an entirely different network, which can't be done without some fairly complicated additional setup.

[-] Rizoid@programming.dev 1 points 10 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.