Samsung TV <2015 (no Tizen)

[Arjen]

Dear forum.

Got a server running with Jellyfin (Docker). I managed to download and install the Tizen app for my 2015 Samsung TV Sofar that seems to work (Although something with subtitles but I'll address that later).

I have another Samsung TV. It is pre 2015. It is working fine. I am not willing to buy new when this one is still up and running. I searched the net for a solution but came up empty. Is there a Jellyfin (client) app for pre 2015 (Samsung) TV's? Would love to try that.

It does seem to run Plex, but I prefer (as in PREFER) Jellyfin as it is local and I do not have to register or login to some remote server to watch stuff I have stored locally

Thanks.
Arjen

[TheDreadPirate]

No. If it isn't running Tizen OS, your options are to use DLNA or buy some sort of TV dongle or TV box that runs Android TV or Roku.

[Arjen]

Thank you for your reply.

So I tried and installed minidlna. After a few hours of debugging I finally surmised that jellyfin (docker) and minidlna conflict with each other on port 1900. So I stopped the Jellyfin service and voila, got DLNA on my old Samsung <2015. But this is not the ideal situation. I then stopped minidlna, changed jellyfin from 'bridge' to 'host', installed the DLNA plugin. 

Then the firewall settings were the restricting factor. I just stopped all firewall services just to see whether it would work. However, now I am at a loss. The >2015 Samsung can still play the jellyfin movies/series, but the <2015 Samsung does not detect any DLNA server. My VLC on my PC also does not detect DLNA from jellyfin. What other settings do I have to change to get this to work?

Thanks.

[TheDreadPirate]

What network mode are you using for the docker container?

[Arjen]

I have Yacht installed and Deployed jellyfin through Yacht. The network mode is greyed out, I cannot change it.

And since yesterday late I cannot reach jellyfin anymore. A webbrowser with IP:8096 gives 'Problem loading page' --> Unable to connect.

Jellyfin is running under docker, and when I type:

$ sudo docker ps -all
CONTAINER ID  IMAGE                                COMMAND  CREATED        STATUS        PORTS    NAMES
13539b3dc902  lscr.io/linuxserver/jellyfin:latest  "/init"  23 hours ago  Up 7 minutes                         jellyfin

No ports are mentioned. I disabled the firewall for now.

It was working in 'bridge' mode but I could not get miniDLNA to work because of a port conflict (probably port 1900). If that can be solved I'd be happy too.

Running on an asrock h110m-stx
Fedora server 40 (headless)
Docker installed.

[TheDreadPirate]

Can you share the jellyfin log? That should tell me what network mode it is using.

TLDR; if it is using host networking, the container is running directly on the host NIC. In that configuration, port 1900 on the host firewall needs to be open. Based on miniDLNA working, that shouldn't be the problem. If it is NOT in host networking mode, the container would need to publish port 1900.

[Arjen]

There was no log after I changed it to 'host'. I do not know why, probably crashed.

So I deleted Yellyfin and re-installed it the old fashioned way :-) with a yaml (again in docker). Seems to work and DLNa seems to work as well. However, on my DLNA samsung it shocks now and then and there is no subtitle. I added subtitles as .srt. The Tizen Samsung does pick it up, but in that one I installed the Tizen jelleyfin app, so no DLNA.

I am not familiar with the phrase 'TLDR'. looked it up and it says Too Long Dont Read? Really?

[TheDreadPirate]

TLDR (too long didn't read) is a way of saying "here is a really quick summary if you don't want to read a super long explanation".

As for subtitles in DLNA, it depends on what the client supports and the DLNA profile that it is using. If the profile being used doesn't state support for subtitles, they won't be available. But the default profile include support for subtitles.