I’ve been trying for days now but Plex Dash simply doesn’t work. I get either a black screen or the constantly spinning wheel.
Latest iOS, Media Server and iPhone XR.
Works great on my end.
Would you mind to elaborate where and when exactly you get that black screen? Does it happen right when you start the app or when you try to connect it to your server/account… somewhere else?
Have you tried force-quitting the app and starting it later from scratch?
Are you running DNS rebind protection on your LAN? I believe this can cause that issue.
As I said elsewhere, Plex is relying on something that is broken by design.
Private IP addresses should never appear on a public DNS, and as providers small and large tighten their setups it might not be in the hands of the end user to be able to “allow” this bad behavior anyway.
Given the problems it causes to a lot of your users and clients, how about working on an implementation that doesn’t break standards and best practices?
If you have a suggestion for a solution which solves the same problems and doesn’t conflict with DNS rebinding protections, I’m all ears, but just calling something broken isn’t super helpful.
I didn’t just “call something broken” out of spite: going against an RFC is factually a broken design, I think; and unless this a job offer or you plan to opensource your code, I can’t really be more helpful: I don’t see how I could make a meaningful suggestion otherwise 
If anything, and without having any more insight on why you’re doing what you’re doing, I fail to see why Plex Amp and Plex Dash would require using your plex.direct system when the main Plex app (which provides all the functionality of the other two and then some) doesn’t: if anything, one would suppose it should be possible to use the same network backend for all of them.
While I sympathize with your goal to provide your users with a better sense of security by encrypting all network traffic (even though IMO the necessity of doing so on LAN is debatable for Plex); a solution that requires the users to circumvent or entirely forego (as you seem to suggest here) another protection which is standards compliant feels a bit backwards: by securing their Plex setup, they open themselves to other attack vectors. Not to mention the user-unfriendliness of having to fiddle with DNS settings (if possible at all). Clearly there might be room for improvement here?
HTH
It’s fairly simple. The official Plex app uses native networking code, so they can do DNS/HTTPS tricks to ensure plex.direct addresses work. These new apps use React Native networking (fetch) which doesn’t allow for e.g. node’s https agent.
In any event, we’ll address it in one way or another!
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
