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!
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
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.
The additional wrinkle here is that Docker creates its own networks behind a little firewall and router that it runs as part of the docker software. So from the point of view of the programs running inside your docker containers, they’re on computers on a totally different network. If you have some way to inspect your list of containers you should probably be able to find out what IP addresses they’re on.
The way this is solved for stuff like Jellyfin is generally by passing through an environment variable that tells it what the IP address of the host machine is. That way it knows what address to serve its content on.