Just now signed up for the beta, so I’m not yet in it. I’m looking forward to test it out.
1 Like
Hi guys,
I have the same issue and all my friend using Plex on adroid TV are having the same (so not a local issue for sure). I found out that everything is working fine once I disable the subtitles (.ass subtitles) but when I enable them the movie crashes. Maybe it is a way to investigate this.
Thanks for the support anyway 
I think that might be a different problem, as I have problems with and without subtitles.
You’d need to upload log.
Do you know when it will be available for armv7a devices (Mi Box S)?
Hi,
it works now for movies with the 7.31 beta version. But the live TV doesn’t work with the new player. I will attach the log.
This the log for live TV. IT seems thaht the problem of DNS corrected for movies was not corrected for liveTV : Failed to resolve hostname 192-168-0-189.6740316abee44e729788591fbef43798.plex.direct: No address associated with hostname
@DaveBinM
log live tv.txt (166.1 KB)
Thanks for the additional information, I’ll have a look and pass it along to our engineers
The same happens to me. Also the automatic refresh change activated produces black screen and does not play the content on Xiaomi Mi Box S with Android 9 2604
my Android TV, Firestick, Fire tv, all suck!! Switching everything to apple TV! Way way less issues with apple and plex.
New player dont work either on MI S Box android 9.0. Switched to Kodi with Plex addon
3 Likes
Same here
1 Like
I’m experiencing the same issue as well, while connected from a remote network on Galaxy 10 and firestick. I installed the beta (7.31) on the galaxy, the issue still exists. Everything is working great on my local network.
Do you have custom server access URLs entered in your plex settings under network? I did because my server is behind a nginx proxy but this was causing an issue because of the certificates with the same error using the new player. I removed them and port forwarded again and all is well.
There is a certificate verification using the new player but not the old. I suspect many of the issues people are having here in the forums may be related to reverse proxies and custom URL entries in their advanced settings and not having the certificates exactly right.
1 Like
I dont have it and I have the same problem as others
The cert appears correct in the browser, I’ve also verified the cert using openssl. The weird thing is sometimes the remote connection works, but most the time it does not. As far as I can tell only android clients are affected. I have used apple TV remotely without issue. This has to be a problem with the clientapp. I am also using an nginx reverse proxy without issue, until recently.
My media stack is hosted on a powerful linux server within docker containers including nginx. Plex is configured using the host driver everything else is using a custom bridge.
Yea. It is worth a shot to just remove all custom URLs, Certs, and remnants from nginx in your plex network settings and just port forward to test if the problem goes away. I have been switching clients off the new player for about a year or so now and just chalked it up to never being fixed.
Now that there is talk of the old player going away I started to dive into troubleshooting deeper. I found another thread where a plex employee was talking about certs being used in the new player for verification at start of playback. Makes sense why it would cause some issues. I had custom URL’s entered that I though were helping but actually causing my issue because I did not have my Cert defined for my custom URL in plex.
This is not everyone’s issue apparently but hopefully it helps a few people out.
Any updates? Plex new player still doesn’t work.
Dan,
Just to verify, you have all the certs and such in Nginx, and the custom url defined in Plex, but you didn’t have the certs listed within plex itself?
I’ve got the same setup right now, but I do have the cert defined. I was getting ready to remove the cert because in theory by the time the request is forwarded from nginx it’s http now, unless your sending it to Plex from Nginx using https as well?
Exactly. I had nginx all setup with let’s encrypt and reverse proxy setup using https. But I also had the port forward in my router for 32400 because of some issue I had way back when.
I found that the port was still forwarded so I left that alone and removed the custom URL’s from plex custom access URL’s and I no longer had my remote clients on android having issues with plex not playing using the new player.
So I found an old post, but essentially what OttoKerner says here is that as long as 32400 remains open, the apps will ALWAYS use 32400, not the proxy. So if you had 32400 open, the clients still would have come through 32400.
When you removed the custom URL did you by chance remove the certificate as well? I’m wondering if this perhaps is more of an issue with the certificate, rather than the custom URL?
OttoKernerPlex Ninja (Moderator)
@Suspense said:
Why is plex forcing a connection attempt on port 32400, when you specifically configure plex not to?.
That is not what the setting does.
It allows you to specify an additional , alternate URL for Plex clients to try and use. Just in case the direct connection (per local/private IP and port 32400) is not usable.
Nowhere does it say that other routes to contact the server are switched off by this.
