I’ve been running a jellyfin server for a while now but barely use it. For some reason I can’t get other devices on my local network to be able to sign into it. One out of ten times it’ll work, but the other nine times it just doesn’t and says it can’t connect. I dunno. Probably a me problem.
Is the computer running it going to sleep and coming back with a new IP address maybe? Or just asleep when you’re trying to use it? Gotta set it to never-sleep, just display off
That too yes, but by denying sleep mode it never changes anyway. My router will give it the same IP after a reboot, but if it’s off for a while it will get a new one. I’m not sure if that’s the same with all routers.
If the DHCP lease has expired while the device is off or asleep it may or may not get the same IP when it reconnects depending on the settings on your router. If the machine is on when the lease expires it can typically renew the lease and retain the same IP. Generally DHCP leases default to 1440 minutes (24 hours).
Best practice is to do what I mentioned before and have your router reserve the IP so if the settings on your device get reset for some reason you won’t have to go hunting the IP. At least though, you should have a range of IPs outside your lease pool so you can assign static IPs on the device without running into a DHCP conflict, but this runs into the aforementioned issue of the device forgetting its settings.
Not entirely. The lease default is usually about 24 hours, that computer would need to be completely offline for a day and the IP address would usually need to be reassigned before the device gets a new IP. Even then, the router would probably try to give it the same.
When I moved I unplugged the Jellyfin server about 4 days before the router and it came back with the same IP. I dunno, maybe I have a good router. 🤷♂️
Other things come into play. If you don’t have leases expire often or dozens of devices coming and going repeatedly like a public wifi may have, it’s also stored in ARP tables, saves it some work later when it recognizes a device.
I’ve been running a jellyfin server for a while now but barely use it. For some reason I can’t get other devices on my local network to be able to sign into it. One out of ten times it’ll work, but the other nine times it just doesn’t and says it can’t connect. I dunno. Probably a me problem.
Is the computer running it going to sleep and coming back with a new IP address maybe? Or just asleep when you’re trying to use it? Gotta set it to never-sleep, just display off
You should be able to tell your router to always assign the same IP to the same MAC for specific machines.
That too yes, but by denying sleep mode it never changes anyway. My router will give it the same IP after a reboot, but if it’s off for a while it will get a new one. I’m not sure if that’s the same with all routers.
If the DHCP lease has expired while the device is off or asleep it may or may not get the same IP when it reconnects depending on the settings on your router. If the machine is on when the lease expires it can typically renew the lease and retain the same IP. Generally DHCP leases default to 1440 minutes (24 hours).
Best practice is to do what I mentioned before and have your router reserve the IP so if the settings on your device get reset for some reason you won’t have to go hunting the IP. At least though, you should have a range of IPs outside your lease pool so you can assign static IPs on the device without running into a DHCP conflict, but this runs into the aforementioned issue of the device forgetting its settings.
That seems like a problem with the router.
Not entirely. The lease default is usually about 24 hours, that computer would need to be completely offline for a day and the IP address would usually need to be reassigned before the device gets a new IP. Even then, the router would probably try to give it the same.
Ah ok. I’d call 24 hours a while ;)
When I moved I unplugged the Jellyfin server about 4 days before the router and it came back with the same IP. I dunno, maybe I have a good router. 🤷♂️
Other things come into play. If you don’t have leases expire often or dozens of devices coming and going repeatedly like a public wifi may have, it’s also stored in ARP tables, saves it some work later when it recognizes a device.
Huh. Neat
I’m unsure. It’s been a while since I tried. I’ll do some troubleshooting when I get a moment.
What is the error/issue I found it really straightforward especially with the QR code for quick connect
Maybe hairpin nat?