No offense taken.
I guess your shared users should be fine, but I am not sure about that.
How many other apps do you have which are a local server but require remote connection for authentification? I have none other. As I said, Emby does it differently with a much simpler, yet imho much less secure/much more difficult to set-up way.
If you can’t whitelist dns rebinding in your router, you probably don’t have your own domain and know how to generate valid certificates.
I simply have no idea why it worked before for you all. The old player probably simply ignored the missing redirect and “just worked”. If this was a security issue is way beyond my knowledge.
Since I have white listed plex.direct for a while I never had this issue. I am also an android user.
This has been happening for me as well. I’ll revert back to the old player for now until there is a fix.
Edit: I turned off DHCP handling on my router and installed Pi-hole and used that as the DHCP server instead. Seems to be working correctly now. I suspect my modem has some kind of DNS protection enabled but I couldn’t modify it to include direct.plex.
I feel your pain and agree. I work in IT support and work with these kind of issues regularly but for my infrastructure at home, I don’t want to spend hours troubleshooting problems. When I’m finished work and its time to relax, I just want things to work quickly and reliably.
That said, these things are always a difficult balance to get right, especially when security is involved. If you want to run a server (work or home), it usually goes beyond “plug and play”. You need to understand what an IP address is and how to configure port forwarding. For me personally, I prefer everything to be manual configuration so I can configure it correctly and make it reliable/fast. At the opposite end of the spectrum are users who want to click, next, next, done, and have everything work first time. This relies on wizards and lots of automatic checks that slow everything down.
In this case, its clear that Plex has implemented this for security (a trade off with simplicity). Businesses with any public facing infrastructure usually pay for their own domain and SSL certificates. However for the average home user, this is clearly an overkill so there needs to be another way. Plex has chosen to allow its users to “piggyback” off their own domain and SSL certificates to implement their security (to protect everyone).
Please don’t get me wrong, I’m not saying I agree or disagree with their implementation. But here the things I would do to improve the current problem:
Display a meaningful error message when playback fails. The generic error is meant to catch unknown errors, not make an incorrect suggestion for a known problem.
Instead of a single green “tick” for remote access, have other checks/ticks for each key mandatory item. There needs to be another one showing whether your DNS name is resolvable from the server and the IP address.
Back again to add to the traffic and say that the full release of 8.0.0 yesterday didn’t solve this on either my Shield TV Pro - still need to choose the old player - or my Android mobile.
If the Old Player is to be removed, this has to be classed as a show-stopping issue. And apparently it isn’t…
Same issue here… 8.0 versión was installed yesterday and force-enabled the new player so all the media crashed…in the last previous versions, I had disabled the new player so it took me a minute to realize that after I got the errors back… The New player, as nice as it looks is not working for a lot of people, so the sensible thing to do, if not to fix the new player, is to not mess with people’s settings… We’re using the old player so we can use Plex at all. Don’t make us regret the money we’re spending on you in this time where not every company will come out of the crisis in their feet.
Same update and Still same problem on android tv 9 with last 8.xxxx Plex client …
Thanks Plex dev team in advance For the résolution !
The issue is now since one month So we gess the solution is on way
Take care !
Unfortunately, I had to turn to Emby (Due to lack of engagement from Plex to resolve these issues). I have been a Plex Plus subscriber for years now but since these latest updates, nothing plays, even after disabling New media player. I’m going to give Emby a try. Its been running since yesterday without a single issue. I’m running both Emby and Plex simultaneously on the same server without any issues. If Emby continues to perform well, I will be cancelling my Plex Pass Subscription. Like others have said on this thread, Plex has grown into something completely different than when I originally signed up. Its broken almost constantly with every new update. So far Emby has proven to be very stable and performing well. It’s extremely disappointing that Plex employees have failed to engage with us on this thread despite so many replies, people with the same issues and going on for such a long period of time. I suggest that you all give Emby a try.
Like you friend, I had been with Plex for about 6-7 years and I too also took this decision over the weekend and migrated myself and my family over to Emby. A bit scary after so long under our Plex overlords control but it was pretty painless. The interface is snappier, i have more control as an administrator and most importantly it plays everything without fuss. I can watch Live TV again after about two months (and I don’t need to fanny about with DNS Rebinding, nslookup and capturing packets lol! I have a simple BT router that can barely even cope with assigning a static IP address to a local device without having a hissy fit so of course this wasn’t causing my issue)
A shame but the lack of response from Plex over this forced my hand in the end…that and forcing “Plex Movies and TV” unto me.
Could please someone of Plex team reply to this subject ?
The issue is since one month and there is more than 300 comments in this topic (there are other topics than this one with much comment related to this issue) and 0 reply from plex team…
So we dont know if the issue is even identified by plex and so if it will be corrected soon. (Or not)
So if you need again some logs To help to solve the problem, you can Ask, i ´ll give you mines.
My issue with the situation is that Plex are very quiet. They don’t seem to be acknowledging the issue to their customers. (whether they consider it an issue or not, their users do, therefore it is!) nor issuing any guidance. If they came out and explained that it was “expected behaviour” with the new player because of reasons x, y and z then people would be better informed to make a decision in the long term.
The potential DNS rebind issue / resolution concerns me. Many home routers (including mine!) dont allow this level of configuration and the answer therefore isnt straightforward. People shouldn’t “Expect” to have to go to this level of configuration, at least without warning or options being made available.
For the record I am running Nvidia Shield TV Pro (and Shield TV elsewhere inthe house) and they both have the “New Player” issue. Strangely though on occasions I can enable the new player and it works for days and days without a problem, but then it just stops. I would expect the DNS Rebind issue to be an all or nothing problem. May be wrong on that, but it seems very hit and miss.
Come on Plex - we’re not asking for much. Just some clarity on the issue that hundreds (thousands?) of people are reporting and details of any roadmap to resolve them if that is in your plans.
Sorry for the silence on this issue, we have been investigating and have found the problem when DNS rebinding protection is in use on a network. The build below should fix the issue and allow you to play with the new player on a network with DNS rebinding protection.
I’ve been reading this thread for a good while hoping for a resolution. Reading the stuff about DNS and having a Fritzbox router, thought I was onto a winner based on the earlier post from a Fritzbox user. I too am getting the the following with the new player enabled.
04-25 17:07:09.087 i: [FFmpeg] [ERROR] [tcp @ 0x86d55de0] Failed to resolve hostname .plex.direct: No address associated with hostname
I’ve tried entering the full FQDN and also just plex.direct into the DNS Rebind Protection setting on the router but it doesn’t appear to have made any difference. Tried testing with nslookup as described in an earlier post.
@TheOne320 Were there any other settings you needed to change on your router after entering plex.direct?
@mike_birket.co.uk
No, nothing else and you could just try the new build. It could also be something completely different in your case, but you would have to post your client logs.
05-01 12:47:43.726 e: Stacktrace: com.google.android.exoplayer2.r: java.lang.IllegalArgumentException
at com.google.android.exoplayer2.v.handleMessage(SourceFile:24)
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: java.lang.IllegalArgumentException
at android.media.MediaCodec.native_setSurface(Native Method)
at android.media.MediaCodec.setOutputSurface(MediaCodec.java:1979)
at com.google.android.exoplayer2.video.k.a(SourceFile:143)
at com.google.android.exoplayer2.video.k.a(SourceFile:33)
at com.google.android.exoplayer2.video.k.handleMessage(SourceFile:1)
at com.google.android.exoplayer2.v.c(SourceFile:3)
at com.google.android.exoplayer2.v.e(SourceFile:44)
at com.google.android.exoplayer2.v.d(SourceFile:18)
at com.google.android.exoplayer2.v.handleMessage(SourceFile:4)
... 3 more
Thank you for the update. I have installed the new client and so far so good. Worked each time I have tested it, after allowing my shield TV to sleeo, etc.
Happy to continue to feedback on here if I experience anything different.
Looks like you are experiencing a different issue, I have a feeling I know the problem and will send you another build to test shortly which I think will solve the issue.
Thanks for this. Probably a daft question (apologies) but not got access to my Shield at the moment as my son hogging the TV playing Minecraft. Will that build just be available to download from the normal Apps section in the Shield or does it require a sideload or something?
