Sudden Inability To Play (2 users)

[suttyd0lt 2]

After some help, two family members on Samsung Tizen TVs (various models, one being a UE65NU8009 on Tizen 4.0) have reported playback failing. App works fine for browsing, but when they hit play they get a playback error straight away.

Looking at the server logs, everything appears correct from Emby's side - PlaybackInfo returns 200, but then the app immediately calls ActiveEncodings/Delete. Server never receives a request for any video segments. The whole sequence takes less than a second

2026-01-22 12:41:52.500 Info SessionsService: POST http://host1/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby for Samsung&X-Emby-Device-Name=Samsung Smart TV (UE65NU8009)&X-Emby-Device-Id=0ce457dc-1d2e-4eba-a713-079266017c00&X-Emby-Client-Version=2.2.5
2026-01-22 12:41:52.501 Info SessionsService: http/1.1 Response 204

2026-01-22 12:41:55.737 Info MediaInfoService: POST http://host1/emby/Items/80551/PlaybackInfo?UserId=xxx&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=30000000&X-Emby-Client=Emby for Samsung
2026-01-22 12:41:55.740 Info MediaInfoService: http/1.1 Response 200

2026-01-22 12:41:57.853 Info MediaInfoService: POST http://host1/emby/Items/80551/PlaybackInfo?UserId=xxx&StartTimeTicks=0&IsPlayback=true&AutoOpenLiveStream=true&AudioStreamIndex=1&SubtitleStreamIndex=-1&MediaSourceId=mediasource_80551&MaxStreamingBitrate=30000000
2026-01-22 12:41:57.857 Info SessionManager: Adding playSession 95195596fc4d40d8b362fae0c345aef3
2026-01-22 12:41:57.857 Info MediaInfoService: http/1.1 Response 200

2026-01-22 12:41:59.242 Info MediaInfoService: POST http://host1/emby/Items/80551/PlaybackInfo?UserId=xxx&StartTimeTicks=0&IsPlayback=true&AutoOpenLiveStream=true&AudioStreamIndex=1&SubtitleStreamIndex=-1&EnableDirectPlay=false&EnableDirectStream=false&AllowVideoStreamCopy=false&MediaSourceId=mediasource_80551
2026-01-22 12:41:59.252 Info MediaInfoService: http/1.1 Response 200

2026-01-22 12:41:59.297 Info HlsSegmentService: POST http://host1/emby/Videos/ActiveEncodings/Delete?deviceId=0ce457dc-1d2e-4eba-a713-079266017c00&PlaySessionId=95195596fc4d40d8b362fae0c345aef3
2026-01-22 12:41:59.298 Info HlsSegmentService: http/1.1 Response 204

2026-01-22 12:41:59.515 Info MediaInfoService: POST http://host1/emby/Items/80551/PlaybackInfo?UserId=xxx&StartTimeTicks=0&IsPlayback=true&AutoOpenLiveStream=true&AudioStreamIndex=1&SubtitleStreamIndex=-1&EnableDirectPlay=false&EnableDirectStream=false&AllowVideoStreamCopy=false&AllowAudioStreamCopy=false
2026-01-22 12:41:59.523 Info MediaInfoService: http/1.1 Response 200

2026-01-22 12:41:59.569 Info HlsSegmentService: POST http://host1/emby/Videos/ActiveEncodings/Delete?deviceId=0ce457dc-1d2e-4eba-a713-079266017c00&PlaySessionId=af5b28aa53034b1cbf6eaa9fc5653ce4
2026-01-22 12:41:59.570 Info HlsSegmentService: http/1.1 Response 204

2026-01-22 12:42:00.195 Info PlaystateService: POST http://host1/emby/Sessions/Playing/Stopped
2026-01-22 12:42:00.196 Info SessionManager: Playback stopped reported by app Emby for Samsung 2.2.5 playing Tom and Jerry - S1950, Ep18 - The Duck Doctor. Position: 0 ms

You can see the app tries progressively more restrictive playback options (disabling direct play, then direct stream, then video copy, then audio copy) but aborts each attempt almost immediately without ever requesting a segment.

What's odd is this was working fine, then stopped for one user around the 16th Jan, another on the 20th. No server-side changes on my end between those dates. Running Emby 4.9.3.0 behind nginx reverse proxy, users are on app version 2.2.5.

I've tried a few things already - different SSL certs (ZeroSSL and Let's Encrypt), adjusting TLS ciphers and protocols on the reverse proxy, users have power cycled TVs and reinstalled the app. No joy.

All other devices are playing fine, only these two samsung tv's appear to be having the problem. 

[Luke 42077]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[suttyd0lt 2]

If you look from 15:18:02 - that is a recent attempt, I've also attached two screenshots, one appears to be more detailed than the other, but from a server log perspective identicial. 

embyserver.txt

[Luke 42077]

@SamES

[SamES 1056]

20 hours ago, suttyd0lt said:

I've tried a few things already - different SSL certs (ZeroSSL and Let's Encrypt), adjusting TLS ciphers and protocols on the reverse proxy, users have power cycled TVs and reinstalled the app. No joy.

You mention SSL certs, etc, but from the log it doesn't look like it's connecting to a https address

Is the server setup correct in the client?

20 hours ago, suttyd0lt said:

2026-01-22 12:41:55.737 Info MediaInfoService: POST http://host1/emby/Items/80551/PlaybackInfo?UserId=xxx&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=30000000&X-Emby-Client=Emby for Samsung
2026-01-22 12:41:55.740 Info MediaInfoService: http/1.1 Response 200

2026-01-22 12:41:57.853 Info MediaInfoService: POST http://host1/emby/Items/80551/PlaybackInfo?UserId=xxx&StartTimeTicks=0&IsPlayback=true&AutoOpenLiveStream=true&AudioStreamIndex=1&SubtitleStreamIndex=-1&MediaSourceId=mediasource_80551&MaxStreamingBitrate=30000000
2026-01-22 12:41:57.857 Info SessionManager: Adding playSession 95195596fc4d40d8b362fae0c345aef3
2026-01-22 12:41:57.857 Info MediaInfoService: http/1.1 Response 200

2026-01-22 12:41:59.242 Info MediaInfoService: POST http://host1/emby/Items/80551/PlaybackInfo?UserId=xxx&StartTimeTicks=0&IsPlayback=true&AutoOpenLiveStream=true&AudioStreamIndex=1&SubtitleStreamIndex=-1&EnableDirectPlay=false&EnableDirectStream=false&AllowVideoStreamCopy=false&MediaSourceId=mediasource_80551
2026-01-22 12:41:59.252 Info MediaInfoService: http/1.1 Response 200

 

 

[suttyd0lt 2]

SSL terminates at the reverse proxy and then http:// internally. It is only these two tizen users with the problem (out of 10 people). Everyone else can play fine. 

(Recent log entry to show it working for others, this was the Emby app on an apple tv) 

11:08:45.317 - GET http://host1/emby/videos/441687/master.m3u8?DeviceId=E7473C13-EB68-4940-A821-4AF21B62DC23&MediaSourceId=mediasource_441687&PlaySessionId=348d609df1d44e68b45b066f387fc4a8&api_key=x_secret24_x&VideoCodec=h264,mpeg2video,hevc&AudioCodec=ac3,eac3,mp3,aac&VideoBitrate=24360000&AudioBitrate=640000&MaxWidth=1920&AudioStreamIndex=1&TranscodingMaxAudioChannels=6&SegmentContainer=ts&SegmentLength=3&MinSegments=1&BreakOnNonKeyFrames=True&FillEmptySubtitleSegments=true&hevc-profile=Main,Main10&TranscodeReasons=VideoResolutionNotSupported → 200 11:08:45.718 - GET http://host1/emby/videos/441687/main.m3u8?... → 200 11:08:46.228 - GET http://host1/emby/videos/441687/hls1/main/0.ts?PlaySessionId=348d609df1d44e68b45b066f387fc4a8 → 200 11:08:48.211 - GET http://host1/emby/videos/441687/hls1/main/1.ts?PlaySessionId=348d609df1d44e68b45b066f387fc4a8 → 200 11:08:49.126 - GET 

Edited January 23 by suttyd0lt

[SamES 1056]

21 hours ago, suttyd0lt said:

UE65NU8009 on Tizen 4.0

What's the other model that has stopped working? Are these both up to date with firmware updates?

Are all the other TV's that work newer models?

[suttyd0lt 2]

This is the day it broke for them (it was the 19th) This shows that tizen 4.0 TV sucsessfully playing and transcoding before later that day failing, It also shows another Tizen 8.0 TV playing and transcoding (who has yet to be impacted). 

The other TV, hers is a UE50TU7100KXXU Tizen 5.5 emby app 2.2.5, the logs have dropped out the UI, let me see if I can find them and I will update the post. 

embyserver-63904464000.txt

Edited January 23 by suttyd0lt

[SamES 1056]

So the Tizen 4.0 TV was successfully playing and transcoding the day before, but then stopped.  Did anything change?  Server or client updates?

[suttyd0lt 2]

I can't see any changes in Emby app version between working and not working. Server side nothing was touched, and here is the odd thing - The first user to have the issue was on the 16th, while that was happening, the user who you've got the logs for now, was happily playing/transcoding (as seen in the log)

I don't know about TV firmware updates, I've dropped them both a message, I suspect one of them won't have a clue, but hopeful the other one will know. 

Edit, server logs only appear to go back to the 19th, so I don't have the other example with the transition to working / not working. 

Edited January 23 by suttyd0lt

[suttyd0lt 2]

Further information, the TV you had logs for was last updated in early December, so predates all of these problems. They've also upgraded to 2.3.0, but unfortunatley no joy. 

I am going to test without the reverse proxy and allow them to direct connect with ip:port, if that works then I know its something with the server, although with the staggered way the problem has presented, plus other TV's being not impacted I don't see why it would work, but its worth testing. 

Edited January 23 by suttyd0lt

[suttyd0lt 2]

Final update for the night, direct ip:port works, so it has to be seomthing to do with TLS or the reverse proxy itself. I tested without any headers, so its not there.

It has to be something specific to my configuration, I can't be the only person using https://github.com/ZoeyVid/NPMplus + Emby. 


 

[Neminem 1515]

I use this config in NPM official docker image.

Never used NPM+.

Advanced config.

Remember to edit https://your.domian.com

Quote

add_header X-Content-Type-Options "nosniff" always;
add_header Referrer-Policy "no-referrer" always;
add_header X-Download-Options "noopen" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header X-XSS-Protection "1; mode=block" always;
add_header X-Permitted-Cross-Domain-Policies "none" always;
add_header X-Robots-Tag "none" always;
add_header X-Permitted-Cross-Domain-Policies "master-only" always;
add_header Pragma "no-cache" always;
add_header Cache-Control "no-store" always;
add_header Content-Security-Policy "default-src 'none'; child-src 'self'; font-src 'self' data:; connect-src 'self' wss: ws: https://mb3admin.com https://github.com/MediaBrowser/; media-src 'self' blob: data: https://github.com/MediaBrowser/; manifest-src 'self'; base-uri 'none'; form-action 'self'; frame-ancestors 'self'; object-src 'self'; worker-src 'self' blob:; script-src 'self' https://your.domain.com. https://www.gstatic.com; img-src data: https: http:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com/css; report-to https://magicc.report-uri.com/r/d/csp/reportOnly;" always;

 

 

Edited January 24 by Neminem

[suttyd0lt 2]

Hey, thanks for the above. I dont quite have the technical prowess to figure this out. 

With the proxy specifically, I've tried without my headers, moved to zerossl, changed my certs from ECDSA to RSA and forced specific cyphers, I did wonder whether http/2 was playing a part, but npm+ forces you onto it with no variable to downgrade and the above suggests its not a problem.  

In the end I've installed official NPM onto my free oracle VPS -> WG -> Server with emby.  It is now working for that user (in a fashion) Will make a post on the NPM+ fork github discussion. Thanks for your help. 

Edited January 24 by suttyd0lt