@amargherio Creating some form of certificate is something I don’t really know how to do yet as I’ve never needed to create any certs to try fix this sort of issue. At the moment I’m happy with Chrome remembering that the certificate from the DL4100 is not valid and not nagging me.
I’m just hoping that Plex doe snot do anything to prevent accessing the server and web player by HTTPS over a local area network connection.
Totally get that. I do a lot of this for a living, so maybe once I get this figured out I’ll write up a good guide on making all the browsers happy with certificates for Plex. And thank you for being willing to throw your hat in the ring when troubleshooting a problem - I always appreciate everyone coming in to help solve an issue!
Same for me, I have my own CA for home… so no pb with the certificate. But I’ve noticed the following behaviour (so it is still a struggle)
I’m not blaming Plex, but it starts to be very annoying. What is lacking from Plex is actually a full “HTTPS” tutorial 
(and I think with Google new security features, the will not have the choice…)
Can somebody guide me to look in the right log file ?
A decent guide would be excellent. I wouldn’t expect 100% coverage for all Plex-compatible servers as it’s an unreasonable goal but something is better than nothing. After being knee-deep in certificate, PKI, and related issues for the last month, I applaud you for your home-only CA! I’m thinking I may be able to leverage a wildcard from Let’s Encrypt as a possible option for general server use (Plex plus related applications).
Well, back at that topic : Plex 1.15.1.710 did not solve any of issues… 
I’m really wondering how people that have installed Plex server to customers are dealing with such problems as I clearly see an increase of problems overall. Not mentioning 1.15 have really performances issues.
I think there’s definitely some required focus on HTTPS and TLS-based connectivity to players and other devices required for PMS.
I didn’t hold much hope for 1.15 to improve the situation much as most of the Chrome changes were last minute, but it makes me wonder about testing the upgrade if performance took a hit.
Hi
Same issue here.
Plex server is running on Windows Server and I can open a Chrome browser on that (same updated version) and not need to be https, and it all works fine as before. Perhaps Chrome is happy over plain http when it’s localhost.
On any other Windows PC in the house, Plex in Chrome refuses to show any devices to cast to from the interface UI unless I go via https. Via https I can connect to devices all okay from the UI Plex UI (hear the Chromecast beep) but Plex will not start playing anything.
Really annoying this is.
Plex on Android is so far okay.
For me Plex on apple is fine until I enable https. I could leave with “mixed mode” but as soon as I put “preferred”, I have to login again every single time I open the app because it will think the server is offline.
So F***** up in both ways !
Hi
We use our computers and chrome quite a bit to cast from Plex to smart speakers and we now can’t, sure things break, but there doesn’t seem to be any update from Plex themselves on this.
Anyone know if they are working on a fix?
Are you using HTTPS when you go to your Plex? As we understand it, HTTP-based support was removed from the browser engine that Chrome uses. So I don’t know that Plex can do much about this issue - if there’s no support for it in the browser any more then Plex can’t guarantee anything.
Plex can’t do something about Google’s decision for sure… they cut the grass under their feet.
But on the other side, Plex claims you can secure your server since a long time but in reality, it is not the case.
Today I’ve experienced some strange behaviors, but even stranger than before after last update (1.15.2.X). So with forced SSL : working from my macbook to a Chromecast, not working in windows to another Chromecast. 1 iPad working and 1 not…
Then I was fed up and reverted the change, but it gave me a new lead : remove all authorized devices. I’ll dig into that to see if after a cleanup this would work… I’ll keep you posted 
Yes using https. Whilst that allows the cast options to work and see Google speakers to cast to (Windows 10 with Chrome), trying to play anything fails, usually casting just never starts. I suspect it is because the cast URL sent to the device is coming back to HTTPS but the certificate being self-signed is not accepted and so the speaker will not play it.
Very annoying, spent ages with my own domain and trying to get a certificate installed in Plex that is valid using LetsEncrypt and can’t work it out, and I work in IT. Plex needs to get something sorted out about this, yes they can’t do much about Google withdrawing support for something, but no it’s not an excuse, they should be testing against beta versions long before they arrive to us. Not happy.
Agreed entirely. I’ve noticed more odd behavior with casting across a variety of devices lately. I need to re-read what @Franck_Ehret mentioned for the 1.15.x updates and see if there are any overlaps.
This shouldn’t have been something that was accidently found through an update to a beta Chrome install.
I haven’t tried working through external server exposure enough yet to get a LetsEncrypt cert into place, but based on your comments I’m already assuming that time is going to be invested.
Hi
I have now managed to get a certificate from LetsEncrypt using my own domain name, and was able to export the PFX out and use it in Plex, so Plex now is HTTPS on my server with a valid certificate, i.e. no warnings in Chrome. It still would not cast locally, this turns out to be because of a DNS rebinding attack protection of the router. If I use instructions here Only have 'indirect connection' to my plex server on my local network to find the local domain name used, and nslookup that, it wasn’t returning an IP address inside my network using my own DNS. Following info here https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections I was able to get pfSense to accept the domain and resolve it to my local IP address. It’s now all working.
Not something that a lot of people could achieve given the steps, knowledge and patience required, as well as needing their own domain name etc for the SSL cert.
Hi there,
It has been a while but I could not figure something that would work.
Do you know how this can be addressed to Plex dev team ?
If it is stuck here in this post, it won’t help getting any further…
I think short of something in the documentation that could call out the requirements for HTTPS for any Chromecast-based devices, the only thing that would help remedy this issue would be some automation around providing a valid SSL certificate (or a better way of managing custom certificates) within Plex or a related install.
I think @LmHome’s work is valuable, but I don’t know (as he’s said in his post) that it’s meaningful for anyone who isn’t technical enough to manage it on their own.
I wonder (haven’t looked into it much yet) if there’s a way to build out a plugin that could cover the gap until a better response from the Plex dev team is issued.
Maybe we just have to be patient enough but it is very frustrating not having the ability to contact somebody from dev team.
In my opinion, more we will go, more all apps/websites on this planet will have to be secured. Plex is no exception, it will have to be secured from every aspect/component point of view.
If possible, I’d like to help the team building up all test scenarios, but first we have to reach out somebody.
Exactly. I wouldn’t mind throwing my time and effort at the problem as long as I knew we had traction with the dev team to get it completed and delivered. Even if there isn’t a solid timeline for it all, I’d like to at least hear that it’s on a roadmap somewhere.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
