I’m not able to watch anything withe the new player (exo). I always have an error when I try to watch something.
Server Version#: 1.19.1.2645
Player Version#: 7.31
My nvidia shield as plex client:
plex_nvidiashield_client.zip (67.8 KB)
My ubuntu plex server:
Plex Media Server Logs_2020-04-20_18-55-49.zip (1.6 MB)
Huh. You are running into a DNS issue. That was supposed to be fixed in this version and it did for some. You must still have something else going on. Thanks for the info, I’ll let you know if I need anything else.
Your server logs don’t have debug logging enabled. Can you enable that, restart PMS, playback the same file from the Android app, and get me a new logs.
Here is the client and server log with debug ON for the server.
plex_nvidiashield_client.zip (67.8 KB)
Did you grab the logs at the same time? Your shield logs stop 1 hour earlier.
Sorry, I probably uploaded the wrong file. Here is the file:
Plex Media Server Logs_2020-04-21_14-26-53.zip (3.8 MB) plex_nvidiashield_client.zip (64.5 KB)
Are you trying to watch Live TV?
Yes, try to watch live tv
So is it just LiveTV that doesn’t work? How about regular videos from your server?
LiveTV and one TV Show are not working (Startrek Picard) and another one work (Flintstone).
Here the logs:
Plex Media Server Logs_2020-04-21_14-51-59.zip (3.8 MB)
plex_nvidiashield_client.zip (88.3 KB)
Any news?
You have the Failed to resolve hostname x.plex.direct error. There’s a bunch of posts recently where users have solved it. This is probably the original one:
Support article:
Seems pretty much spot on, dns rebinding error again.
MovieFan.Plex, this DNS rebinding issue seems to be running rampant, and explains a significant amount of the problems reported with the new player. I just wanted to tag you to make sure Plex is aware of this issue and the solution since it’s buried in so many threads. That solves it from the server side, but it doesn’t explain why it’s broken on the client side with the new player as opposed to the old player, so that bug needs to be addressed by the Plex team at some point.
Thanks you for pointing to my attention the cause of the problem. I have do an additional search on my router side. And for people which are using routeur with DD-WRT or similar. An additional setting must be set in the DNSMASQ configuration,
Here is the link of the solution for rebinding dns:
https://forum.securifi.com/index.php?topic=4530.0
Unfortunatly, it doesn’t solve the problem. I probably have more than one problem because I resolve this one and same problem.
Now I can do a nslookup myserver.plex.direct with success. But if I enable the new player I still got dns error.
So what’s next?
Here is the latest log shield_plexclient.txt (10.9 KB)
dns on android could be broken. just because you can do a dns from a desktop / laptop doesn’t mean it resolves the same way on your android device (i.e. bugs in android dns resolution)
I might experiment by installing and activating this https://github.com/x-falcon/Virtual-Hosts/ (though wont appear in the leanback launcher, have to jump through hoops to run)
this might intercept the dns requests and have them be resolved in a manner that works.
Broken in what way? I mean it is working for a lot of users (eg for me) so I don’t think that this is a general problem of the platform.
dns can have many issues due to interactions between server and client. broken should perhaps be in air qoutes, the point would be if dns resolution works on one machine, and fails on another, there’s something “broken” in how that machine is doing resolution with one’s dns server.
So far we have seen several cases where the dns rebinding was obviously blocked by the users’ routers. But you probably don’t mean them but the others that are failing?
