Closed rwjack closed 9 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I have no idea why I had this issue, but:
AppleTV: 192.168.2.0/24 subnet Jellyfin Server: 10.5.0.0/24 subnet Jellyfin container on the Jellyfin Server: 192.168.128.0/24 subnet ^ This should be a docker internal network
Apparently something got mixed up and devices from the AppleTV subnet couldn't talk to the Jellyfin subnet.
Fixed with: /etc/docker/daemon.json
{
"default-address-pools":
[
{"base":"172.20.0.0/16","size":24}
]
}
Is there an existing issue for this?
Current Behavior
Upon updating to the latest image, Swiftfin stopped working on my AppleTV. This also happened a month ago, but I just reverted to the last working image and restored the config files from a backup, and everything was up and running.
Latest image (the one with issues): https://hub.docker.com/layers/linuxserver/jellyfin/latest/images/sha256-cb0792aaf20e2bd12246bb7dc224335d72791b3bb1a7eb736481b3ce0c309c0c?context=explore
Last working image:
I wasn't so lucky this time round when updating, as I can't get it to work even when restoring the older image and backed up config files.
What's odd is that the latest image works regularly on all my other clients, phone, laptop, desktop, except the AppleTV.
Note that Swiftfin (jellyfin for AppleTV) wasn't updated since March 2023, and because everything was working perfectly with the older linuxserver/jellyfin image, I suspect some changes were made in this image in the past 2 months, that led to something breaking in the Swiftfin client.
With the latest broken image, opening Swiftfin while being logged in and refreshing the home page, I just get a Network timed out. -1,001 error. When reinstalling the app, after being prompted to add a server, absolutely nothing happens after pressing connect, almost as if Swiftfin and the Jellyfin server aren't talking the same language.
In pfsense, I see the packets going through both directions on both interfaces, but nothing seems to be happening on the application layer.
Expected Behavior
No response
Steps To Reproduce
Explained above.
Environment
CPU architecture
x86-64
Docker creation