I explain the problem that I have my sony android tv before an update it works perfect but someone came up to update the plex client and there it all started I can not reproduce the trailer for the movies send the same error that you posted on this site buy an MBox S 4K android Tv to test and the same problem to discard install an emby server and so far I have no problems I see the trailers and I do not have to be fighting with the client for real something they did ■■■■ in plex
This is never getting fixed. It’s clear. They haven’t even begun to fix it, because they claim to not have enough info.
Please stop providing unhelpful and negative comments. I’m trying to ascertain if it’s an issue we’ve already fixed (but isn’t publicly released yet), or if it’s a new issue. I need more information to discern that. Have a read at our Community Guidelines.
1 Like
To anyone holding off updating their Android TV boxes to the latest release of 7.30.1, I can confirm that the option to “turn off new video player” still exists in the advanced settings on my Nvidia Shield. Until further notice, I believe that I will be turning off automatic updates until this gets sorted out. For what its worth, I also have a 4K Fire TV dongle that is rocking the old school 6.12.0.3239 version of the app that works great as well. 
Hopefully this comment helps some folks: A week or so ago I removed Plex App from my Firestick 4k, and installed a beta version “kepler-armv7a-googlePlay-stdExo-7.30.0.16311-29f7de79.apk”, from Release Announcements - Android TV beta, using ‘Easy Fire Tools’ from the Google Play Store.
All the issues I was having (related to this thread) were resolved. Last night, I decided to go back to the public version to see if things were fixed. The issues started again. So, in response to @DaveBinM, I think the issue was fixed in beta, but not yet pushed out (like you stated).
Strange, i installed the same version, and still seeing the issue. I’m getting a cert not matching error, and couldn’t open cache. @DaveBinM, I’ll PM the logs as my domain name is in them.
@DaveBinM I’ve also sent some details in a PM.
The certificate on :32400 doesn’t contain the server’s friendly name, just the server’s generated plex.direct hostname.
It looks as if tls_verify is being enabled on the new player, but I can’t find a log trace of it being enabled on the legacy player (which works fine).
1 Like
Thanks for all the logs, I’ll take a look!
1 Like
@smri Your issue appears to be related to DNS rebinding which is addressed in v7.31, which will be in beta very soon 
@tmar89 Can you please upgrade to either the public v7.30 release or the new v7.31 beta and try again?
Do you see this issue on other clients too, or only on Android? 
Everything is working for me with 7.31. Thank you.
1 Like
@DaveBinM, still getting this in 7.31:
03-31 13:58:05.496 i: [FFmpeg] [ERROR] [tls @ 0x82abd060] The certificate’s owner does not match hostname [plex1.MYDOMAIN.com](http://plex1.mydomain.com/)
03-31 13:58:05.521 i: [FFmpeg] [ERROR] [DemuxerPipeline] Failed to open cache.
03-31 13:58:05.521 e: [FF] Demuxer failed to open input from `https://plex1.MYDOMAIN.com:8443/video/:/transcode/universal/start.m3u8?
PMing you new set of logs.
[FFmpeg] [ERROR] [tls @ 0x82abd060] The certificate’s owner does not match hostname [plex1.MYDOMAIN.com](http://plex1.mydomain.com/)
Errors like this tend to indicate a custom certificate or a custom URL. Our certificate won’t match a custom URL so that would explain the SSL failure. In the new player as we now validate SSL on playback connections, the old player didn’t validate the certificate/hostname, so seems something isn’t quite right there. We’ll discuss internally how best to handle these while maintaining the best user security we can.
You can also try adding the domain into Custom certificate domain in the Server settings under `Network (you’ll need to enable advanced settings).
6 Likes
@DaveBinM, can i virtually kiss you right now 
lol…so, i added custom certificate domain the same as I have it listed in the custom URL, and it works! Tried several different episodes/movies, all worked with new player! I knew that option was there, but i always though you had to have the cert info as well, didn’t know i could just enter the domain.
Thank you so much! Hope this helps others as this is a simple fix!
3 Likes
So I had port 443 => 32400 behind an nginx reverse proxy, I never needed to worry about a valid TLS certificate on :32400.
I did fill in the SSL fields many years ago with a custom certificate, but missed the description where it asked for PKCS#12 (this must have been a 4am change on my side) and instead plonked in my PEM bundle path, and the path to he key in the “custom encryption key” 
Bundling the certificates to PKCS#12 worked a charm, and the new player is working absolutely fine now! 
I think allowing users to disable TLS validation would be a valid approach, but enabling validation by default.
1 Like
@Deehem, did you try only filling in the domain for the cert and see if it works? I left the rest blank and it works like a charm!
I’m glad to hear the new player is now working correctly (and securely) for you both! 
1 Like
I didn’t try that, but as I already have a certificate I use for :443, I wanted to get it also on :32400 successfully given the option is there.
Unfortunately there is no validation on certificates in that section and it will blindly fail and revert to plex.direct as the certificate common name, something I’ll raise separately with the PMS team.
@Deehem, i have certs as well, but it’s all created by nginx/letencrypt everytime i re-create/update docker (not in PKCS#12 format) and would be a pain to renew all the time and convert for plex. This is awesome that i can just provide the custom domain name in plex and it just works now with the already created cert from nginx/letencrypt. I’m so happy right now…Thanks again @DaveBinM
1 Like
Ok thanks, looking forward to trying 7.31. I was browsing the settings but couldn’t find a way to use beta versions on my Android TV. Do you know if that’s possible?
