New Samsung TV is unable to play some media via Emby

[sobeitjedi 4]

Not sure which corner to look at, but I saw nothing (unless it was too quickly displayed?) - just the spinning ring for a couple of minutes, then the original error message. 

[maxiniedermeier 15]

Didn't See anything too

[maxiniedermeier 15]

Is there any News on this Topic

[Luke 37071]

Have you tried the latest app update?

[SamES 890]

14 hours ago, maxiniedermeier said:

Is there any News on this Topic

Can you please share an example of your issue as I don't know that it is the same issue that sobeitjedi was experiencing.  Thanks

[sobeitjedi 4]

I haven't installed the latest Emby update, but to be honest I lost patience with the media and just deleted it. 

[maxiniedermeier 15]

The Video from the Logs get Transcoded during Playback which would not be needed

The TV Plays this one and other "DVD Rips/MPEG2VIDEO" Fine via USB

Also the Subtitles Plays Fine when enabled and doesn't need Transcoding

Latest Server Version 4.7.11.0 Stable

Samsung Q95A 2021 Modell - Just Updated the App Version to 1.5.5 with the USB install

embyserver.txt ffmpeg-transcode-a7001398-254b-4490-96d9-830b2721b56e_1.txt

[SamES 890]

3 hours ago, maxiniedermeier said:

The Video from the Logs get Transcoded during Playback which would not be needed

The TV Plays this one and other "DVD Rips/MPEG2VIDEO" Fine via USB

Yes, but it is transcoding because the TV's internal player that we use has detected a problem and rejected playback (from the ffmpeg log).  Emby is not transcoding it by choice.

TranscodeReasons=DirectPlayError

It is sometimes possible that what works via USB does not work in the app, although it is rare.

Can you please post a link to me via PM where I can download from you the same file you tested in the logs and I will test it here?  Thanks

[maxiniedermeier 15]

Hello Sam

I will send you the link in a minute

[Brazer 35]

Hi All, is there any further news on this problem. I have 2 users on Samsung TV's complaining of the same issue. But this is on any content. New, old, 265, 264 does not matter. No transcode logs.

UE49MU7070 - Updated to ver 1.5.5 from store version 1.2.6 -> same issue

UE49KU6472

 

embyserver-63821152590.txt embyserver-63821174400.txt

Edited May 31, 2023 by Brazer
no transcode logs

[SamES 890]

10 minutes ago, Brazer said:

Hi All, is there any further news on this problem. I have 2 users on Samsung TV's complaining of the same issue. But this is on any content. New, old, 265, 264 does not matter. No transcode logs.

UE49MU7070 - Updated to ver 1.5.5 from store version 1.2.6 -> same issue

UE49KU6472

 

embyserver-63821152590.txt 8.99 MB · 0 downloads embyserver-63821174400.txt 35.91 MB · 0 downloads

Can you please also post the media info for a sample?  Do you have the user options all turned on to allow transcoding?

[Brazer 35]

4 minutes ago, SamES said:

Can you please also post the media info for a sample?  Do you have the user options all turned on to allow transcoding?

@SamESYes all settings is on. Mediainfo attached for one of the files

2023-05-31 17:53:45.666 Info App: User policy for Chaan. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
2023-05-31 17:53:45.667 Info App: RemoteClientBitrateLimit: 100000000, RemoteIp: host15, IsInLocalNetwork: False
2023-05-31 17:53:45.667 Info App: RemoteClientBitrateLimit: 100000000, RemoteIp: host15, IsInLocalNetwork: False
2023-05-31 17:53:45.668 Info App: RemoteClientBitrateLimit: 100000000, RemoteIp: host15, IsInLocalNetwork: False

 

mediainfo.txt

[SamES 890]

It looks like you're playing from a remote server, is that correct?  Are both TV's having issues remote?

it's a bit hard following the log file as there appears to be playback going on from multiple devices.  Is it possible to get a short log with just a single device trying to playback?

[Brazer 35]

5 hours ago, SamES said:

It looks like you're playing from a remote server, is that correct?  Are both TV's having issues remote?

it's a bit hard following the log file as there appears to be playback going on from multiple devices.  Is it possible to get a short log with just a single device trying to playback?

Yes all remote. Getting a single user test is going to be tricky. I have a couple of users from around the world. Currently there are 6 streams at this moment. 

Edited June 1, 2023 by Brazer

[Brazer 35]

Hi @SamES

 

Got you a debug logfile with UE49KU6472 TV giving the stream error. So if you search for UE49KU6472 in the logfile you should get the correct stream. Please let me know.

 

embyserver.txt

[SamES 890]

I can see for both of those two devices Samsung devices that they have low remote bitrate limits set that will require transcoding the video, but neither video actually starts trasnscoding.

Can you please try increasing the bitrate limit for one/both of those devices and see if the issue persists?

Do these devices work fine when the bitrate limit is low enough to allow DirectPlay?

I can also see that you are using SSL certs.  Who is the certificate issuer?  Is it LetsEncrypt?

[Brazer 35]

Yes, using LetsEncrypt. But I tried on http (8096) only and it does the same thing.

I have not yet found something that works. Every single video does this. I have tried high bitrates that should do direct play low bitrates to force transcoding or muxing but nothing works for this TV UE49KU6472.

The other Samsung TV (QE65QN700BTXXU) plays fine. No issues. that is why I supplied a log containing two Samsung TV's. One working perfectly (QE65QN700BTXXU) and the other one not working at all (UE49KU6472)

[SamES 890]

Then this is your issue.  Last year the LetsEncrypt root certificates embedded in older Samsung and LG TV's expired and they can only be updated by the manufacturer in a firmware update.  I believe this has been addressed in newer models, but firmware updates for older models are rare.

Make sure you have the latest firmware for both TV's.  If this doesn't resolve it then your alternative is to disable https for those devices (which means setting the server to prefer https, but not require it) or use another supported certificate such as ZeroSSL.  If you change the setting on the server, please make yourself aware of any security impact of such a change.  I expect using a reverse proxy you could also redirect external https traffic to the TV using http but I have not tried this.

 

 

 

[Brazer 35]

@SamESas said in my pervious post that my server already accepts both http and https traffic.

Did you even read my entire post?

If it was a SSL issue the app will not connect to the server when you login to the account. This is not the case. The steam does not play on http or https.

Both TV's was working perfectly a three weeks ago. It was a recent change to the server that is causing this issue. The "Proxy Header Vulnerability" that was patched could this not have caused the issue?

Edited June 6, 2023 by Brazer

[SamES 890]

I did read your previous posts, but all I can conclude for now is what I see in the log. It is always possible that the client can connect to the server but that playback isn’t always possible.

While your server does allow both http and https, my recollection from looking at the logs earlier today was that the clients were connecting via https:// on the https port instead of standard http.  It also depends on what your incoming port forwarding/ proxy setup is doing  

Yes, it is possible that recent security changes have caused an issue, but not being aware of the exact dates and nature of the mitigations, I cannot say for sure other than I’m not aware of anyone reporting a similar issue. It actually sounds like your issues started before these changes 

Regardless, this is now the situation we need to deal with

I don’t know your setup, but has anything recently changed on your port forward or proxy configuration ?  Try changing the connection on the tv using http and the http port as defined in your server or port-forward/ proxy config

[Brazer 35]

On 31/05/2023 at 23:44, Brazer said:

Hi All, is there any further news on this problem. I have 2 users on Samsung TV's complaining of the same issue. But this is on any content. New, old, 265, 264 does not matter. No transcode logs.

UE49MU7070 - Updated to ver 1.5.5 from store version 1.2.6 -> same issue

UE49KU6472

 

embyserver-63821152590.txt 8.99 MB · 3 downloads embyserver-63821174400.txt 35.91 MB · 2 downloads

Hi @SamESin this post's logs from Wednesday you can see that TV (UE49MU7070) is connecting to the http port as http://host2:8096.

Nothing has change server side except Emby server was updated.

 

2023-05-31 17:06:49.667 Info Server: http/1.1 POST http://host2:8096/emby/Users/authenticatebyname?X-Emby-Client=Emby for Samsung&X-Emby-Device-Name=Samsung Smart TV (UE49MU7070)&X-Emby-Device-Id=72afac5f-6712-43ad-8e50-25e8fd7bbc28&X-Emby-Client-Version=1.2.6. Accept=application/json, Connection=keep-alive, Host=host10, User-Agent=Mozilla/5.0 (SMART-TV; LINUX; Tizen 3.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/3.0 TV Safari/538.1, Accept-Encoding=gzip, deflate, Accept-Language=en-GB, Content-Type=application/x-www-form-urlencoded; charset=UTF-8, Origin=host16, Content-Length=24
2023-05-31 17:06:49.668 Debug AuthenticationRepository: GetInternalId reportedDeviceId: 72afac5f-6712-43ad-8e50-25e8fd7bbc28
2023-05-31 17:06:49.669 Info UserManager: Authentication request for Chaan has succeeded.
2023-05-31 17:06:49.670 Info SessionManager: Reissuing access token: 02166ebdbb78419ab0f906d50003cbba
2023-05-31 17:06:49.672 Info Server: http/1.1 Response 200 to host15. Time: 5ms. POST http://host2:8096/emby/Users/authenticatebyname?X-Emby-Client=Emby for Samsung&X-Emby-Device-Name=Samsung Smart TV (UE49MU7070)&X-Emby-Device-Id=72afac5f-6712-43ad-8e50-25e8fd7bbc28&X-Emby-Client-Version=1.2.6
2023-05-31 17:06:49.927 Debug Server: http/1.1 GET http://host2:8096/emby/System/Info/Public?X-Emby-Client=Emby for Samsung&X-Emby-Device-Name=Samsung Smart TV (UE49MU7070)&X-Emby-Device-Id=72afac5f-6712-43ad-8e50-25e8fd7bbc28&X-Emby-Client-Version=1.2.6&X-Emby-Token=x_secret13_x. UserAgent: Mozilla/5.0 (SMART-TV; LINUX; Tizen 3.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/3.0 TV Safari/538.1
2023-05-31 17:06:49.927 Debug Server: http/1.1 Response 200 to host15. Time: 1ms. GET http://host2:8096/emby/System/Info/Public?X-Emby-Client=Emby for Samsung&X-Emby-Device-Name=Samsung Smart TV (UE49MU7070)&X-Emby-Device-Id=72afac5f-6712-43ad-8e50-25e8fd7bbc28&X-Emby-Client-Version=1.2.6&X-Emby-Token=x_secret13_x

 

 

 

 

 

Edited June 6, 2023 by Brazer

[Brazer 35]

Hi @SamES

 

I must eat humble pie and apologise to you. Switching UE49KU6472 to http, fixed the steaming issue.

I did test it on UE49MU7070 on the 31st and it did not work. This I tested myself. I will try it again on UE49MU7070 to see if it does not come right. It is very strange that it allows the SSL to authenticate with the cert but not the playback. I have had this issue with the cert before but the app did not want to connect to he server. I was hoping to get rid of the http port being exposed as I move everyone over to https.

Edited June 6, 2023 by Brazer

[SamES 890]

1 hour ago, Brazer said:

Hi @SamES

 

I must eat humble pie and apologise to you. Switching UE49KU6472 to http, fixed the steaming issue.

I did test it on UE49MU7070 on the 31st and it did not work. This I tested myself. I will try it again on UE49MU7070 to see if it does not come right. It is very strange that it allows the SSL to authenticate with the cert but not the playback. I have had this issue with the cert before but the app did not want to connect to he server. I was hoping to get rid of the http port being exposed as I move everyone over to https.

No problem, please let me know how you go with the MU model.

I agree that it is odd that the app loads but does not play, but I have seen that before.   I suspect that the app is happily ignoring expired certificates, but the player refuses accept it.  This is just a theory; I have no proof, but it appears to align with you are seeing.  Either way, this is a 'Samsung' thing and not something we can control in the app.

[rbjtech 4270]

On 06/06/2023 at 11:42, SamES said:

No problem, please let me know how you go with the MU model.

I agree that it is odd that the app loads but does not play, but I have seen that before.   I suspect that the app is happily ignoring expired certificates, but the player refuses accept it.  This is just a theory; I have no proof, but it appears to align with you are seeing.  Either way, this is a 'Samsung' thing and not something we can control in the app.

So I believe the TLS root certs for the built in Samsung TV browser are different to those used by other TV functions (and I guess the samsung player may fall into that category).

If you try and load emby via the Samsung browser (on the TV), does that load ok ?  Do you see a proper TLS connection and Auth in the Emby Logs / Activity log on the dashboard ?

I'm not sure if the browser will play media - I suspect not, but it might ?... (not that this would be useable, just expanding on a theory here ..)

@softworkzFYI - as it's security related.

[softworkz 3335]

6 hours ago, rbjtech said:

So I believe the TLS root certs for the built in Samsung TV browser are different to those used by other TV functions (and I guess the samsung player may fall into that category).

 

6 hours ago, rbjtech said:

If you try and load emby via the Samsung browser (on the TV), does that load ok ?  Do you see a proper TLS connection and Auth in the Emby Logs / Activity log on the dashboard ?

A reasonable assumption and a potentially useful test.

Though, there might be three different security contexts involved:

• Tizen app
• Tizen browser
• Tizen player

I don't know how these correlate to each other and whether two of them might be identical or all three are different. Also it's not for granted that playback in the browser context would be the same the Tizen player used from an app...

That's rather something for @SamESto find out - he knows much more about Tizen than I do.