Bug: Cannot AirPlay or Chromecast in New App

[vermaakpetrus]

I have both old and new app installed, old app can cast to Chromecast and AirPlay without any problems. New app fails to cast.

All of the new app versions do the same, not able to cast to Chromecast Ultra or AirPlay, while the old app always works 100%

When doing Chromecast only shows PLEX on screen but nothing starts casting.
When doing AirPlay gets error on phone "Error Occurred. A server with the specified hostname could not be found.

Server Version#: 1.41.6.9685
Player Version#: 2025.15.0

log-2025-04-25T02_28_00.191Z.zip (33.8 KB)
Plex Media Server Logs_2025-04-25_04-30-50.zip (5.7 MB)

Extra info:
Windows 11 24H2 with Plex Version 1.41.6.9685
iPhone 15 Max Pro with Plex Version 2025.14.0
Casting Devices: Chromecast Ultra & LG TV UP7500PVG (AirPlay)

[vermaakpetrus]

FYI videos can play in Plex on the device itself, but not cast at all.

[vermaakpetrus]

This solved everything

[luigigalvez]

Same issues with mine. Airplay just casts the audio but not the video itself. Pretty annoying. Previous version was working smoothly

[rfrink]

Similar issue for me. I have a Chromecast Ultra and it won’t even show up in the cast option in the Android app. Downgraded the app and it shows just like it used to before updating the app.

[luigigalvez]

This is fixed in 2025.15.0 version. Airplay is working as expected

[vermaakpetrus]

No AirpPlay and Chromecast are not fixed for everyone. Many people still have issues even with 2025.15.0, including me.

[clowg]

And me

[m_matt_girard]

Same here. Just paid for Lifetime a few months ago. Things should be getting better, not worse…

[vermaakpetrus]

Updated to 2025.16.0 on ios and STILL cannot AirPlay or cast to chromecast. I wonder if its because I am on Cloudflare DNS. But that’s Plex’s problem, not mine.

[vermaakpetrus]

Updated to 2025.18.0 on ios and STILL cannot AirPlay or cast to Chromecast!

[vermaakpetrus]

Updated to 2025.19.0 on ios and STILL cannot AirPlay or cast to Chromecast!

[HisToccO]

Same conclusion here… Worked smooth before. Very anoying. How do we know that Plex has been informed of the issue and works on fixing this ?

[vermaakpetrus]

Tried 2025.21.0 and still cannot AirPlay or cast to Chromecast!

[twntyfive2life]

I still cannot cast in the latest version of the Plex app on an iPhone 14 with latest iOS

[InflatableStego]

Seconding this issue with Plex, specifically the iOS app. Same error message as in the OP post, across multiple configurations, and having just recently started on a known-working configuration.

Attempting to AirPlay from the current (as of 03AUG2025) iOS app to a stereo Homepod pair returns the “A server with the specified hostname could not be found” error message. All other apps can AirPlay just fine, and the Homepods both have internet connectivity and a functioning DNS server. Behavior persists regardless of the VLAN or WiFi network they’re on; even having all three devices (iOS player and both Homepods) on the same WiFi network, same AP, and same VLAN, with a full ANY/ALL rule setup for traffic between them returns the above error message.

Playback on Mac via Safari does NOT have issues. Toggling AirPlay first via the iOS Control Center before launching the Plex App still returns the same error message when playing back content. This suggests it’s an issue specific to the app and not the server, though I also enabled ANY/ALL traffic rules on the server VLAN for troubleshooting after the issue began.

Setup:

• Stereo Homepods on VLAN 200
• Plex Server on VLAN 100
• iPhone on VLAN 1
• ANY/ALL routing permitted between all applicable devices
• Only iOS app has AirPlay issues

[vermaakpetrus]

Tried 2025.22.0 and still cannot AirPlay or cast to Chromecast!

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

[vermaakpetrus]

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

• Open Safari → https://config.claspws.tv

• Open Safari → Artifactory@ip-172-31-33-164 :: Welcome
  Result meanings:

• Any quick page, even 404 or index, means reachable.

• Timeout or block page means DNS or filtering is in the way.

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 Video & Audio Local 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.