[Acknowledged - Still No Fix] Unable to cast server content on Chromecast device

Plex Players Mobile Devices
, ,
1

Server Version#: 1.41.7.9823-59f304c16
Player Version#: Version 4.146.0

  • Device: Samsung Galaxy S24 (Model: SM-S921U1)
  • OS: Android 15
  • Plex App Version: 2025.16.0 (14 May 2025)

I’m experiencing a casting issue that’s driving me mad, and I’m hoping someone can help. Here’s the situation:

  1. I can stream my own content perfectly on my Samsung Galaxy S24.
  2. However, when I try to cast to any of my Gen2 or Gen3 Chromecast devices, the Plex logo shows up on the TV (indicating a connection), but when I hit Play on my mobile, nothing happens—except I can control the volume.
  3. I can cast content from Friends’ servers and Plex TV without any issues.
  4. Casting from a web browser (desktop/laptop) also works fine.
  5. I recently shared my server with a friend, and he was able to stream and cast my personal content without any problems.

So the issue seems specific to casting my own content from the mobile app, despite everything else working normally. I’m on the same local network, remote access is enabled, and there are no VPNs or blockers in place. The problem started right after the big Plex update a few weeks ago.

Would appreciate any ideas or suggestions.

20250527 Plex Log 2.txt (142.5 KB)

2 Likes
2

Update after extensive testing and log review (28 May):

I’ve now confirmed that this issue is a likely bug in the Android Plex app’s casting system. Here’s a detailed summary of everything I’ve ruled out, plus what the logs show…

Issue Summary

  • Plex Server: Windows 10, hostname: LOFT-PC
  • Chromecast Devices: Gen2 and Gen3 (“Loft TV”)

After casting a video from the mobile app:

  • The Plex logo appears on the Chromecast screen :check_mark:
  • I can control the volume from my phone :check_mark:
  • But video playback never starts :cross_mark:

What I’ve Confirmed

  • Casting from other apps (e.g. Google Home, YouTube) works fine on the same Chromecast devices.
  • I can cast Plex content from a web browser (Chrome) with no issues.
  • I can also cast my friends’ Plex content and Plex TV from the Android app successfully.
  • The problem only occurs when casting my own content from the Android Plex app.
  • Content is direct play compatible (H.264/AAC)—no transcoding needed.
  • My Plex settings:
    • Secure connections set to Preferred
    • Local IP range (192.168.0.0/16) added to “Allowed networks without auth”
  • I’ve restarted all devices and performed a full uninstall/reinstall of the Plex Android app.

log.txt (84.8 KB)
nativeLog_0.txt (154.3 KB)
Log Evidence (Attached)

From log.txt and nativeLog_0.txt generated by the Android app:

  • Cast session is successfully initiated:
    [Vizbee] Playing on TV Loft TV

  • But then:
    [ExoPlayer][VideoFrameReleaseHelper] Failed to call Surface.setFrameRate:
    java.lang.IllegalStateException: Surface has already been released.

  • This is followed by:
    Playing Locally – Not connected to TV

This indicates that the Android app believes the cast session has failed and tries to fall back to local playback—but can’t render the video locally either due to a broken player surface.

I’m happy to provide any further logs or assist with testing a fix. You can refer to the attached logs and/or my forum thread for full context.

3

Appreciate your deep dive into the issue.

I am in the same boat at least with the outward symptoms.

Hopefully this will help Plex find a resolution, but its been over a month for me.

In the meantime if you roll back to the previous version of the app it functions fine.

2 Likes
4

Hi, thanks for the reply. I really appreciate you confirming you’re seeing the same issue.
I’ve been hesitant to roll back the app, but it’s frustrating that this hasn’t received any visible attention. From what I understood, Plex actively monitors the forum for bug reports, and I believe I’ve provided everything they’d need to begin investigating.

It’s quite disappointing that a broken core feature like Chromecast casting can go unresolved for this long without any acknowledgement. Hopefully, the more of us who report it, the harder it will be to overlook.

1 Like
5

Update (29 May):

I’ve now rolled back the Plex Android app to a version prior to the 29 March update, specifically, v9.36.0.37495 and casting to my Gen2/Gen3 Chromecast works perfectly again.

This confirms that the issue is caused by a regression introduced in the 29 March update (v9.37.x and above). The app initiates the cast session but fails to hand off playback correctly, causing the video never to start, even though volume control and the Plex logo appear on the TV.

Thanks to @morri916 for confirming the same symptoms and suggesting the rollback, and to @jcschauer for detailing the exact steps to do it. Much appreciated.

If anyone else is experiencing this issue, I recommend rolling back to an earlier version from a trusted source like apkmirror.com. Just be sure to uninstall the current app first.

Plex team — please could you acknowledge or escalate this? Happy to help test a fix if needed.

3 Likes
6

I have EXACT same issue on IOS. Worst part is it looks like they don’t care to fix it. Bug: Cannot AirPlay or Chromecast in New App

2 Likes
7

@Mrdavebot First of all, sorry that it feels like you are being ignored. Plex forums sometimes feel like that scene from Finding Nemo with the seagulls (“Mine?”.. “Mine”.. “Mine!”) and reports can get misplaced.

Anyhow, I’ve gathered this info and filed an issue internally. We may reach out to you individually for more logs but there is already a lot of great info here. I really appreciate the due diligence and logs on this issue as I know it’s pretty frustrating. I will do my best to follow up as we make progress here on your problem.

2 Likes
9

@MJ_Plex Thanks for getting back to me, I’m happy to hear it’s been logged. Let me know if you need anything else from my side. Happy to help however I can.

1 Like
10

Add another here that has been unable to connect to Chromecast.
It sees the Chromecast, tries to connect, sits and spins, then just stops trying. No error, no connection.
It’s been like this since the AWFUL “new experience” update, MONTHS, unable to use the service bc it is the only thing I use Plex for.

Screenshot_20250611_171215_Plex
Screenshot_20250611_171215_Plex677×738 26.4 KB

2 Likes
11

Same issues. Can’t cast at all. Just doesn’t work.

Reverted the app prior to the update and it works fine

What have you done?

2 Likes
12

Been trying to figure out how to revert and which version to go to! :rofl:

Edit to add:
Clear cache on phone, in app and during phone reboot
Uninstall and reinstall with removing data prior to reinstall
Checked for updates etc

IMHO, since I was actively streaming, it automatically updated then it couldn’t even connect to the Chromecast it’s pretty clear where in the version changes it happened.

1 Like
13

Hi @MJ_Plex, just checking in to see if there’s been any progress on this. I know things take time, but thought I’d ask in case there’s an update you can share. Still happy to help with logs or testing if needed.

1 Like
14

Still unable to connect here as well and also happy to provide what I can!

1 Like
15

Another user here having issues with Chromecast as well.

2 Likes
16

Hi @MJ_Plex, just following up again as it’s been a while since the last update. I know these things take time, but I’d really appreciate any news on progress or if you need anything else.

1 Like
17

Tried 2025.22.0 and still cannot AirPlay or cast to Chromecast!

We cannot log tickets, I guess will never get solved….

1 Like
18

@MJ_Plex

I also am still unable to use Android Plex Mobile app with Chromecast.

This has been going on for…5 or 6 months now? Since the release of the “new experience” without any updates or acknowledgement etc

That’s 6 months of the only way I use it that’s unavailable.

I’m replying to this users post so someone can acknowledge that it’s happening to them plus kudos for pinging the thread.

2 Likes
19

finally after much much much fiddling this worked:

Resolve DNS with test then check Plex Settings

1. RESOLVE DNS

Step 1: Quick sanity checks first

Do these on the iPhone and the PC.

iPhone

Windows

nslookup config.claspws.tv

nslookup repo.claspws.tv

curl -I https://config.claspws.tv

curl -I Artifactory@ip-172-31-33-164 :: Welcome

  • If you get IPs and fast HTTP headers, DNS is fine.

  • If resolution fails or hangs, fix DNS below.

Step 2: If both resolve, skip DNS fixes

Go straight to Plex items:

  • iPhone → Settings → Plex → Local Network = On.

  • Plex Server → Settings → Network → Secure connections = Preferred.

  • Allow DNS rebinding for plex.direct in your resolver if you use one.

  • Enable hardware transcoding. You already set NVIDIA.

  • When testing, check Plex Web → Status → Dashboard for Playback and Connection.

Step 3: If either domain fails, then do DNS changes

iPhone

  • Wi-Fi → tap your SSID → Configure DNS → Manual → 8.8.8.8 and 8.8.4.4 → Save.

  • If you run Pi-hole, NextDNS, AdGuard, or Cloudflare Gateway, allow-list:

    • config.claspws.tv

    • repo.claspws.tv

    • claspws.tv

    • Also add a rebinding exception for plex.direct.

Windows
GUI path:

  • Adapter Properties → IPv4 DNS: 8.8.8.8 and 8.8.4.4.

  • IPv6 DNS: 2001:4860:4860::8888 and 2001:4860:4860::8844.
    Then run:

ipconfig /flushdns

PowerShell option:

Set-DnsClientServerAddress -InterfaceAlias “Wi-Fi 2” -AddressFamily IPv4 -ServerAddresses 8.8.8.8,8.8.4.4

Set-DnsClientServerAddress -InterfaceAlias “Wi-Fi 2” -AddressFamily IPv6 -ServerAddresses 2001:4860:4860::8888,2001:4860:4860::8844

ipconfig /flushdns

Browser Secure DNS

  • Chrome or Edge → Settings → Privacy and security → Security → Use secure DNS → choose Google or turn Off.

  • Firefox → Settings → General → Network Settings → DNS over HTTPS → Google or Off.

Router (only if you manage it)

  • Set WAN and LAN DNS to Google for IPv4 and IPv6.

  • Disable router DoH or content filters, or allow-list the domains above.

  • If you use a resolver with rebinding protection, add plex.direct to the exception list.

Step 4: Retest

  • Repeat Step 1 checks. If they pass, retry a cast and watch Plex Dashboard:

    • Aim for Direct Play or Direct Stream.

    • If it says Transcode, lower cast quality or remux to MP4 to avoid heavy HEVC transcodes.

That’s it. This order tests config.claspws.tv and repo.claspws.tv first. You only touch DNS if those fail.

2. PLEX SETTINGS
What we changed for Plex casting

  • Confirmed DNS isn’t blocking Vizbee: config.claspws.tv and repo.claspws.tv resolve and respond on both PC and iPhone.

  • Plex Media Server:

    • Secure connections = Preferred.

    • Hardware transcoding enabled and device set to NVIDIA. This stabilized the HEVC Main 10 transcodes.

  • iPhone: Local Network permission for Plex = On.

  • If you later use a DNS filter, keep an exception for plex.direct to avoid rebinding issues with secure direct connections.

If casting stutters again

  • On Plex Web → Status → Dashboard, check the session labels:

    • Aim for Direct Play/Direct Stream and Connection: Direct.

    • If it shows Transcode, your server must keep up. Lower cast quality or remux to MP4 for Direct Stream.

    • Change Plex app Videu & Audio Lcal Quality & Wi-Fi Quality down till stutter stops.

  • Keep Chromecast and iPhone on the same 5 GHz SSID and make sure mDNS is allowed.

That’s it. Your DNS is set to Google, and the Plex changes you made are the right ones for the new app.

Important note about DNS:
Cloudflare DNS can still be in use even if the checks above look fine. For this guide, set DNS to Google first on iPhone, Windows, and your router, then retest.
Use 8.8.8.8 and 8.8.4.4. For IPv6, use 2001:4860:4860::8888 and 2001:4860:4860::8844.

Update:
Cloudflare DNS was the culprit. After switching to Google DNS, I flushed DNS ipconfig /flushdns on Windows, and it still took about 30 to 60 minutes before casting worked. This delay happens because iOS and some network devices cache DNS internally, so the old address can be used until the cache expires.

1 Like
20

@MJ_Plex I finally made it work by making google my dns and not cloudflare, and fiddling with a ton of settings, which I highlighted at the bottom of this chat.

Can we have a button in phone app that tests if dns resolves and all settings are correct

And also on the server in browser settings button that checks dns is resolves and settings are correct

if not then a button to backup current settings and a button to apply correct settings and shows tooltip how to get dns resolved?

I think it will help a lot of users. Took me 3 months to get casting working, we could prevent future pain this way…

1 Like
21

Hi. Thanks for the above ad glad this worked for you. I think this is a little much for a ludite like me to try (and on Android so not sure if the steps would even be the same) but replying as its the only post I’ve seen a Plex Employee even acknowledge this issue. I’m honestly astounded this hasn’t either been fixed or rolled back as surely this is a major function of Plex (to be able to cast)!

@MJ_Plex is there any feedback on this issue and is it even likely to be fixed?

1 Like