SOLVED: Jellyfin App on Amazon Fire TV 4K issues

[MTCom]

I seem to have the same problem, although it's not from an upgrade.

I have a Jellyfin server 10.10.6 (Server, Web and Build-Version) running in a docker container on a Raspberry Pi running Ubuntu 24.04.2 LTS. When accessing the server via an iOS app it works just fine. Same via the web-interface.

Since my TV is an old Sony that can't install any apps, I bought an Amazon Fire TV 4K (2nd generation). I downloaded the Jellyfin app and connected to the server via the IP address http://192.168.0.3:8096. While I can see the libraries, I just see empty tiles for the movies/TV shows on the home screen. When going into the movies library, the screen just remains empty.

When I try to run any media, it errors out and doesn't play anything at all.

The app version on the Fire TV is 0.18.5. And I couldn't choose a version, it just installed it automatically.

I'm happy to share log files, but which ones do you need? The ones shown in the web interface, or log files from docker?

[theguymadmax]

Yes, please post your server logs and any ffmpeg logs when attempting playback.

[MTCom]

Here is the log from the server when I try to play something on the TV


[12:24:00] [INF] [33] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[12:26:48] [INF] [51] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[12:29:36] [INF] [31] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[12:33:00] [INF] [31] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[12:35:48] [INF] [20] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[12:38:32] [INF] [29] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for mom. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
[12:38:35] [INF] [3] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for mom. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
[12:38:35] [INF] [18] Emby.Server.Implementations.Session.SessionManager: Playback stopped reported by app Android TV 0.18.5 playing Küsten. Stopped at 0 ms
[12:38:36] [INF] [18] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.


And here are two playback logs:

https://privatebin.net/?1aa37bed5d35b467...1c2Giv7TUn
https://privatebin.net/?606bbd2ed70a91f5...sDwF4ma9JA

[TheDreadPirate]

Do you have a VPN running on the server?

Also, that ffmpeg log doesn't match any log entries in the main jellyfin log.

[MTCom]

Yes, I have wireguard installed on the server.

Here is the log from docker. It started with the container being newly created and I tried to play a TV show episode on the TV:

https://privatebin.net/?b782edd9d6aa1f9f...n3T3oPMYja

This is the latest protocol from the Jellyfin web interface covering the same period:

https://privatebin.net/?3363e1cf7350fc1a...LoFSRsgz9G

When I try to play anything on the TV, it says it has a playback error and eventually gives up.

---

I just tried to stop the wireguard service, but the app on the Fire TV shows still the same behaviour.

[TheDreadPirate]

Is the FireTV on the same network as the server? Are you using a reverse proxy? Do all clients, remote AND local, go through the reverse proxy? Assuming you are using one.

I see this message a lot, which tells me there is some weirdness with your network or some network related config.

Code:

error receiving data: The remote party closed the WebSocket connection without completing the close handshake.

[MTCom]

After some more digging, it seems that the port forwarding I setup on the router was the culprit. After deleting that rule, suddenly the Jellyfin app worked like a charm.

Seems the port forwarding on that shitty, provider supplied router, also interferes on local traffic, not just from WAN to LAN.

Thank you very much for your help.