Server Version#: 3.87.2
Player Version#: Chrome browser, casting to TV
Plex has been fine for eons. Starting a few days ago, I can no longer cast to my TV. When I click on the chromecast icon, it only shows “now players found”.
I saw someone else having the same problem and they suggested a workaround of using https://app.plex.tv which worked once and then no more, instead showing my TV as an available player, but when I try casting, the TV just shows the word “Plex” in the upper left corner of the screen and a spinning circle in the center of the screen, then it gives up after 1 minute, the TV returning to its screensaver and Plex reporting no error or anything; if I try casting again, it then gives the chrome error “failed to cast”.
I am able to cast just fine using Netflix and I can also cast to my TV using the Plex app on my phone, so I’m inclined to think it’s a problem with Plex, not my browser, workstation, or server.
PMS is installed in a Windows 2012 R2 server, dual quadcore opterons, 16GB RAM. My TV is an LG Chromecast TV which has Chromecast 2 on a gigabit LAN. (WiFi is not an issue.)
Is this perhaps some issue with SSL? If so, this is @*#&$^ because nobody spends zillions of dollars to buy an SSL cert for their home computer.
Update: My Plex app which was able to cast last night can no longer cast today.
Hey, whatever you guys did overnight, it’s working again! I checked my server’s build number and it didn’t change (sorry, original post had my web client build number by mistake). Here’s some add’l text which I’ll post in more detail to the general channel after lunch…
I talked with Google Chromecast support and found that no matter what I did, trying to cast to my TV (with built-in Chromecast Ultra) failed, using both my server’s IP on my LAN and using app.plex.tv. (Locally, the cast icon wouldn’t see my TV at all, the Plex public url would see it but fail to cast.) FWIW, same results using Emby. The Google person and I tried all kinds of things and, finally, using the app.plex.tv URL and Chrome’s (browser, not Chromebook!) built-in cast (3-dot menu, “Cast…” option) was able to see AND establish the server cast connection to my TV. Before, using Chrome’s native casting would allow me to cast the browser tab, desktop, or a file, but never allow to cast directly from the server to the TV like it would with Netflix or YouTube. Now, using Chrome’s native casting makes the cast connection directly from my Plex server to the TV, just like Netflix does w/o any app cast icon. ALSO, once the Chrome native casting succeeded, it somehow triggered something w/in Plex because now Plex’s cast icon can once again see my TV and also cast to it, just like before.
Hello! I’ve been having the same problem for a few days. When I try to use the Chromecast button inside Plex from my computer it says “No players found”. If I use the Chromecast button from Chrome it works, so I guess it’s something to do with Plex used from my computer (from my mobile it works properly). I’ve been checking the settings just in case I changed something without realising, but I can’t see anything. Any idea I can try, please?
Me too!
And the https://app.plex.tv work around isn’t working for me (it sees “Chrome Plex Web” but neither of my chromecasts)
Unplugged the chromecasts to force them to re-boot, but no effect.
I run Plex in a docker off my unRAID server and it’s currently running version 3.77.4.
Usually connect through a chrome browser on my Win10 laptop with the docker’s address 192.168.1.xxx:32400, but that gives the “No players found.”
Help
Afraid this doesn’t work for me. I have used the HTTPS address since Google switched Chrome. Everything is up to date, including the server, but Plex cannot find either of my two chromecasts, yet I can cast from the browser window. Directing it from the mobile works though. The problem is clearly with Plex and I wait eagerly for a solution.
All other apps are casting just fine via http, only Plex is SOL.
If there’s some “deployed fix”, either it’s not working or I’m not getting it.
If casting now requires SSL (i.e. https only), then 99% of the Plex users are screwed because hardly anybody blows hundreds of bucks on an SSL cert for their home.
If Google yanked non-SSL support of their cast API, I suggest Plex add an alternative. (Google’s been on this “https only” holy crusade for a year now, but they really don’t get it because they think that the only people on the planet using web protocols are on the Internet. Stupid Google.) So please, please don’t be a Google sheep and do whatever they tell you, ok? Think of the users. Think of everyone like me who can’t afford an SSL cert for their home network so have to cast via http from their home computers, ok?
Hi, my Plex server sits on an Austor NAS and I used to be able to cast to Chromecast and Chromecast Audio devices. I noticed a few days back that when clicking the icon I just received a “No Players found notification” (This is when visiting the web page via HTTP on my local network via a Chrome browser). After having read the posts here I accessed the web page via HTTPS and I am now able to select the relevant device and it connects however I cannot stream media to it, I receive “An error occurred trying to play this item”. The same media when played to the client I’m using plays fine over HTTPS or HTTP.
The Plex version number shows as: Version 1.14.1.5488
https://app.plex.tv/desktop?secure=1# <-- Brings back the “Cast” option but when I try to play something I get this error: “The server “XXXXXXXXX” does not have a valid connection for casting. Check that the server is claimed in server settings.”
https://192.168.1.174:32400/web/index.html <-- This one specifically states that it is NOT secure and crosses the “https” out in red in the URL field. Brings back the “Cast” option but when I try to play something I get this error: “The server “XXXXXXXXX” does not have a valid connection for casting. Check that the server is claimed in server settings.”
Is PLEX planning to update their app to fix this issue?
I have terrible internet so the first one will not work for me day in and day out. And I do not consider something secure if it says in big red letters “not secure”.
I can still connect TO cast but not actually CAST from Chrome. I can still cast from iOS and, strangely, I can see what has been cast ON the web client and can even pause/play it or set it to random or repeat. But NOT, and I repeat, NOT cast.
I am running Ubuntu 16.04 and PMS 1.14.1.5488 and cast to a Chomecast 2nd generation using Chrome 72.0.3626.119 (Official Build) (64-bit).
This one specifically states that it is NOT secure and crosses the “https” out in red in the URL field. Brings back the “Cast” option but when I try to play something I get this error: “The server “XXXXXXXXX” does not have a valid connection for casting. Check that the server is claimed in server settings.”
The strike-through indicates that the certificate offered by the server is not valid for the given url. Specifically, the wildcard certificate included with each Plex Media Server is recognized by browsers as valid for a .plex.direct domain specific to that server.
This strike-through does not mean that the connection is actually insecure, only that that the domain does not match the one referred-to in the certificate.
Thanks, duncanbeevers, I appreciate you posting so quickly.
That is weird since it reads to the left, “Not Secure”, and when you click on the “Not Secure” the dropdown reads, “Your Connection to this Site is Not Secure.” It does also note that the certificate is invalid, which matches what you said. Any idea how to get rid of that error ("The server “XXXXXXXXX” does not have a valid connection for casting. Check that the server is claimed in server settings.”)? Otherwise I cannot cast without going to the *.tv address.
Also, any idea regarding how soon Plex will be able to issue a fix for the Chrome api change? Is there a better place to report this issue, especially since it is affecting so many users (including many that are having the issue but have not figured out what the issue is and reported it via the forums or reddit)?
Hi guys, I just came back to attempt Cast from Chrome after a month of not using and found to my surprise no players available to Cast to, same as everyone else. After fiddling about a bit, it turned out to be related to DNSMASQ on my AdvancedTomato router configuration. I had to add:
adding that line above fixed the issue and I can now properly validate and redirect from app.plex.tv and plex.tv/web back to my local connection. Note: I do not have Remote Access enabled. I tried also https://<local IP/computer name>:32400 and after proceeding with invalid certificate name, it validates with app.plex.tv once, then redirects back to :32400 and I was able to cast as well. It’s not a perfect solution, but it works.
Sorry if this is a stupid question but what types of cast devices should appear?
I have a chromecasts, android tvs, google home and a home hub. The only devices showing are one of the android TVs and the chrome browser I’m using. All of them appear if I use the native cast button in chrome.
The Google person and I tried all kinds of things and, finally, using the app.plex.tv URL and Chrome’s (browser, not Chromebook!) built-in cast (3-dot menu, “Cast…” option) was able to see AND establish the server cast connection to my TV. Before, using Chrome’s native casting would allow me to cast the browser tab, desktop, or a file, but never allow to cast directly from the server to the TV like it would with Netflix or YouTube. Now, using Chrome’s native casting makes the cast connection directly from my Plex server to the TV, just like Netflix does w/o any app cast icon. ALSO, once the Chrome native casting succeeded, it somehow triggered something w/in Plex because now Plex’s cast icon can once again see my TV and also cast to it, just like before.