Chromecast not seeing your device or failing to connect? Try this Google Support workaround

As of Feb 13, 2019, my Chrome browser would no longer let my Plex web app see my Chromecast TV(i) so I couldn’t cast to it any more. Using https://app.plex.tv allowed me to see my TV, but attempting a cast would fail at exactly 1 minute. And casting using Chrome’s built-in casting (the 3-dot menu option, “Cast…”) would only let me cast the browser tab, desktop, or a file; it wouldn’t actually make a cast connection from my Plex server to the TV. For a short while, I was able to use the Plex Android app to cast to the TV, but even this stopped working after a short while.

I tried all kinds of troubleshooting techniques to isolate the problem, all to no avail. I finally got to talk directly with a Google Chromecast team member and we spent over an hour w/ various test cases, finally hitting on something that might now help all of you folks as well. Here’s what to do…

Symptom 1: Plex web app, using local LAN address, would not see Chromecast devices on my LAN. Using Chrome’s built-in casting would only allow casting the browser tab, desktop, or file.

Symptom 2: Plex web app, using Plex public url of https://app.plex.tv, would see Chromecast devices (e.g. my TV{i}), but cast attempts would fail with a generic error after a 1-minute timeout, and no entries would show up in the Plex logs, indicating a client-only issue.

Workaround(ii): Using the Chrome browser, connect to the Plex public url, https://app.plex.tv, use Chrome’s built-in casting (3-dot menu at upper-right, select “Cast…”), and Chrome would establish a server-to-TV Chromecast connection the same as if casting Netflix to the TV.

Post-workaround: After the workaround succeeded just 1 time, Plex’s Chromecast device identification resumed working; plus, Plex’s cast icon is once again able to establish server-to-TV cast connections.

The Google Chromecast Support person and I both think the combination of Plex’s public url and Chrome’s built-in casting somehow re-enabled normal Plex functionality. This isn’t something we can prove, per se, although it seemed fairly obvious to us.

Note: I also heard from a Plex person that, apparently overnight, they pushed out some sort of update addressing this issue. I checked my Plex server and there was no update available, so maybe it’s a public-only update which–as a side effect?–corrected something in PMS that got broken by the Feb 13 Chrome update. (That’s a guess on my part, but it fits the scenario.)

(i) I have an LG 55L621U 4K Chromecast TV with built-in Chromecast Ultra, connected to my gigabit LAN via Cat-6 cable and the LAN uses only 10/100/1000 switches.

(ii) The workaround somehow triggered Plex’s original Chromecast device identification and the ability to successfully cast once again. Now, the workaround still works but is no longer needed once the originally functionality started working again.

I am having the same issue. Using https://app.plex.tv did allow me to Chromecast, while a LAN address will not. However, trying the 3 dots in Chrome thing you suggested did not resolve the issue while using the LAN address as it did with you.

Can confirm having the same issue with local plex webclient - using app.plex.tv seems to work fine. Look like a bug.

so uh, do you think they’re gonna like, fix this?

Looks like the Plex folks are betting the bank on https://app.plex.tv working for everyone, but it doesn’t appear to be very reliable. It’s sometimes working for me, sometimes not; and rebooting my TV and/or PMS doesn’t change anything. Usually, it works, but not always. Tonight, the family sat down for movie night and Plex couldn’t cast at all. Thank God I’ve got Emby still, it’s not as pretty, but it’s reliable. Starting to regret my Plex license and maybe should’ve gone with an Emby license instead. :frowning:

they are two different versions and the one at app.plex.tv is newer. that is why we ask if you have tried it.

We are aware of the issue and are looking into trying to make it more reliable with chrome.

The issue mostly seems to stem around secure connections setting on server and if you are using using https or not (Whether it be lan or hosted web app)

It worked for me when using https (as opposed to just http) with the LAN address.

EDIT: Correction, it didn’t really work. Using https with the LAN address allowed me to connect Plex to the Chromecast (it didn’t even see any cast destinations with http without the s), but it would fail as soon as I tried to play video. So it is only working with app.plex.tv for me.

1 Like

So, I’ve been frustrated reading all the links with possible fixes. None worked for me. I have the Chromecast dongle and cast would not work within the Chrome/Plex but would cast from the Chrome Cast from the tab. Today I noticed that the Plex icon in the loaded tray would open my Firefox browser. I wondered if that association was the problem and yes.. I changed my default browser (which has been Firefox forever) to Chrome and it sure was the problem. I can now cast from within the Plex web page.

3.91.0

  • Added modal explaining no Chromecast support for http-hosted app

so that is the fix for it? Disappointing…

OK, how many Plex users have an SSL cert installed on their Plex server, lemme see the hands! Hmm, I think I see one way in the back, can’t tell for sure w/o my binoculars…

The point is, hardly ANYBODY hosts Plex using HTTPS.

Hey Plex guys, please rethink your use cases, ok? I’m thinking the non-SSL Plex hosts are in the majority, so please reconsider this as your primary use case? Please?

We pay for SSL certs for all users. (of course one can use their own if they chose) Just need to be signed into your server. Most have this enabled.

Are there any instructions on how to do this? I’ve looked all over in my server pages and haven’t seen any references to this. Can you point me to a link, please?

Y’know, this is HUGE news if it works. :slight_smile:

There are no real instructions needed. Sign in your server to your plex.tv account. That’s it.
https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/

Wow yeah, I hadn’t seen that before, am reading it now and will test it tonight.

Thanks tons, I really appreciate it!

Ok, my server setting is and always has been: Secure Connections = Preferred so I guess I’m ok. However, in my browser, if I use http://myserver:32400/ I connect ok, can watch anything locally, but the Cast page icon still can’t see my Chromecast TV. When I change it to https://myserver:32400, Chrome gives me the standard SSL warning, I accept it, connect, but the https:// is lined-out in my browser URL bar and yet I CAN now see my Chromecast TV. :slight_smile: I connected OK, verified movie casting worked…voila!

Thank you EVER so much!

The certificate is only valid for the FQDN your server is receiving automatically from Plex. Not for your own, custom domain name. And it’ll never be valid for the pure IP address.
Hence the recommendation to load the web app from app.plex.tv because it will get loaded securely over https and without any certificate warnings.
You could use the Plex FQDN for your server, but you’ll have to bookmark it manually, and it’s subject to change every few months.

You read my mind…after exploring around with settings I hadn’t looked at for eons, I was about to ask about my FQDN vs Plex URL.

You can find your current FQDN(s) by calling https://plex.tv/api/resources/?X-Plex-Token=xxxxxxxxxxxxxxx&includeHttps=1

(replace xxxxxxxxxxxxxxx with your own X-Plex-Token)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.