Well, I have the same problem, as many other that use Samsung TV that still should be supported.
For me, it works to set it to unsecure connections, but that is not an option as my server is not on the same network as my TV.
It might be that Samsung has not updated the certificates on our TV, or something, and that might be the problem, as some says, Even though our TVs still should be supported. But it might also be another problem (the last update came around the same time), and I can Play some files still.
But this should Plex, as the developer, fix (or talk to Samsung for a fix), and not just ignore it, as it seems based on the silence from their part.
Hope this is fixed soon, either from Samsung or Plex.
it does not work here. but there are just some episodes that do not work. not all.
mabey there are some place to bug report so they can see that this is a big problem?
the logs instructions are right there in the collect logs link, you should just need the server logs unless otherwise requested, then drag and drop the zip file that comes from plex web directly into a reply in that other thread.
Plex Web > settings > general (not the plex web general)
There are 2 different issues I feel, one is the older TV set cert issue announcement on Sept 30th. But newer sets are effected also just in a different way. The older sets see my servers as being down and they canât connect. New Samsung TVâs can see my servers and see content but get a playback error. Are they all related to the LE issue? I tend to think not judging by what people are seeing. Itâs easy to loop all Tizenâs into that one known issue and pacify the masses with that answer. The reason I say this is because even on an unsecured connection newer sets still exhibit the same playback issue, while older sets can connect and play just fine. Even the forced Subtitles workaround some utilize wonât work on the newer Samsungâs. Itâs easy to point the finger at the other guy, but by doing so you point three back at oneself. I feel the issue fire newer Samsungâs is a Plex app related issue.
Actually⊠Just fixed mine. I allowed insecure connections on my TV app. That didnât fix it, but I manually added my server (docker container) manually in the app and it seemed to resolve the issue.