My Plex Server is failing to HW transcode when starting media from a Shield

General Discussions
, ,
21

@Cibot

You have included the player logs, not the server logs.

Your logs do show the player failing to handle the input video stream.

02-16 19:10:03.680  e: [Player][ExoPlayer] Playback error detected
02-16 19:10:03.681  e: An exception occurred: com.google.android.exoplayer2.i: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
02-16 19:10:03.682  e: Stacktrace: com.google.android.exoplayer2.i: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.google.android.exoplayer2.o.handleMessage(SourceFile:386)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:193)
	at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.plexapp.plex.ff.FFDemuxer.open(SourceFile:158)
	at com.plexapp.plex.ff.source.FFLoadable.load(SourceFile:70)
	at com.google.android.exoplayer2.g.al.run(SourceFile:381)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:764)

02-16 19:10:03.682  i: [FF] Releasing demuxer.
02-16 19:10:03.687  i: [Player][Timeline] Handling player error
02-16 19:10:03.687  i: [Player][Timeline] Playback stopped (error: true)
02-16 19:10:03.688  i: [Player][Timeline] Unable to report progress to server as duration is unavailable.
02-16 19:10:03.689  i: [Player][Timeline] Player error not known by server, likely to be a client configuration error
02-16 19:10:03.689  i: [Player] Error reported: PlaybackInterrupted (null)
02-16 19:10:03.689  i: [Player][Timeline] Playback stopped (error: false)
02-16 19:10:03.690  i: [Player][Timeline] Unable to report progress to server as duration is unavailable.
02-16 19:10:03.737  i: [TranscodeSession] Stopping...

Specifically it shows losing connection to the server.

I need to see the server logs jointly with this.

Your problem is different than this thread…
Please create a new one

22

Is this going to be fixed? It seems kinda silly that my plex server works outside my network but not inside it.

Telling us to enable DNS rebinding is a security threat, there is a reason it is restricted and not all of us have access to disable it.

23

If one reviews what I post, I specifically recommend adding the rule to allow private domain ‘plex.direct’ This action does not disable DNS rebinding protection.

May I have the XML of a file (from top through the </Media> marker only of a title which fails to operate as expected?

I will find something in my library and do my best to replicate then report

24

I got it working with the plex.direct. I’m just irritated because this is the second time in 6 months where my setup stopped working properly. I’m not sure why this started all of the sudden, I’m running a 6 month old version of PMS to get Xbox 360 support.

25

I am having the same issue, and I’m not sure I have that option to allow private domain in my router settings. Besides, it really should be fixed in the player I think.
I notice the difference in logs that “new player” is setting option resolve_hosts which should rebind plex.direct url to local url (which doesn’t appear to work). But “old player” is modifying url instead to be local url (which seems to work). What is the reasoning/benefit of using resolve_hosts instead of just modifying the url? It seems quite evident here what the drawbacks are or can be.

26

There’s a fix in Android v7.31 (in beta very soon) which should address the DNS rebinding issue :slight_smile:

2 Likes
27

v7.31 is now in beta :slight_smile:

1 Like
28

Still seeing this issue on 7.31.0.16802 on both Nvidia Shield Client and Android Mobile.

04-22 21:50:58.811  i: [FFmpeg] [ERROR] [tcp @ 0x26f3023300] Failed to resolve hostname 192-168-1-2.667d37a79ee4424d8c6af2fd9550c2f9.plex.direct: No address associated with hostname

I can workaround the issue by re-enabling DNS Rebind on my router.

Server version: 1.19.1.2645.

[pms]$ cat /etc/*release* |head -1
CentOS Linux release 7.7.1908 (Core)
[pms]$ uname -r
3.10.0-1062.18.1.el7.x86_64
29

Please create a thread tagged server-nvidia-shield

30

I can create a new thread, but I’m not running PMS on Nvidia? Sorry if I misinterpreted.

31

@qwolf0

My apologies, I misread.

Your error is DNS Rebinding and my post above about creating a rule to allow private domain in the DNS resolver is the solution for the error message you posted.

1 Like
32

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.