@mr_trebus I’m having trouble re-creating your issue with the samples you sent. any chance you’d be willing to re-install the beta and send me your full debug logs?
Just an FYI, this server beta is causing playback to fail on all content for the AppleTV HD using the public 8.45 client and the “old video player” (which is required for the AppleTV HD clients.
Logs attached.
Plex Media Server Logs_2025-09-29_11-26-18 2.zip (5.9 MB)
logging.zip (66.1 KB)
@dklein the build i posted earlier in this thread should fix the issue you are seeing
Hi Chris,
Unfortunately I still see the same issue with AppleTV HD devices and 8.45 with the build listed at https://artifacts.plex.tv/plex-media-server-experimental/1.43.1.10183-e3bdfea69/macos/PlexMediaServer-1.43.1.10183-e3bdfea69-universal.zip
Logs:
@dklein your now seeing a different issue which I am also working on fixing.
@chris_decker08 any timelines on addressing the tv issues? Or how can we get more invites for TestFlight.
- Gracias
@wakkedoff any chance you can send me your debug logs which capture the issue? I thought i was reproducing your issue but it ended up being a different one.
Also, unfortunately our TestFlight slots are full and we are already at the maximum allowed by apple 
CPU: AMD Ryzen 9 5950x (16 cores + 16 threads),
Video: NVidia video card, (VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)),
OS: Ubuntu 24.04 LTS.,
Memory: 64GB RAM.
Storage: SSD RAID1 for boot (USB3), Adaptec 81605 RAID adapter with 7x8TB 4kn drives in RAID6.
I have a 2nd Plex installation, same MB, same CPU and GK208 video card, same RAID adapter but older (512e) disks. I have not downgraded this machine so I can run on either version of Plex Server on both Rokus. Same symptoms on alternate server.
I tried to post yesterday but it looks like the reply didn’t make it.
I have 2 Plex servers.
Machine 1: primary use is playback and management
AMD Ryzen 9 5950x CPU (16 cores + 16 threads), 64GB RAM, NVIDIA Corporation GT218 [GeForce 210] (rev a2), currently running 10156 (rolled back after transcoder crash)
Machine 2: primary use is Live recording and transcoding
AMD Ryzen 9 5950x (16 cores + 16 threads), 64 GB RAM, NVIDIA Corporation GK208 [GeForce GT 720] (rev a1), Ubuntu 24.04 LTS, currently running 10162 (experiences same transcoder crash as machine 1)
Both machines share the same libraries, which reside on machine 1’s RAID6.
Just grabbed the logs - can I DM them?
I did notice this in there:
Request came in with unrecognized domain / IP ‘plex.redacted.domain.com’ in header Referer; treating as non-local
My server is local but I also can access it via a domain, that on my LAN resolves to the local IP address. But I don’t understand why the domain is in these headers at all. Why isn’t the server’s local IP in there?
edit: I see the same domain mentions in the logs after rolling back, so it’s not the issue. Still weird, though. I can’t see it set anywhere in PMS settings.
This fixed issues I had with the transcoder dying repeatedly. From the logs it looks like it thought I had an Nvidia card, but I have Intel xe. CudaInit() was failing. All good now.
1 Like
Been busy with work, do you still need the file. If so, where can I upload?
- Gracias
I’m having the same/similar issue. I can play the file back perfectly on Plex Web on Safari and on iOS, but the Apple TV gives me a “Playback Stopped. Conversion failed. The transcoder process crashed.” I’m using PMS on Docker, passing an Intel QuickSync through the container, but get the same results if I pass or don’t pass. This seems isolated to the Apple TV client.
Is there any new beta build coming with the latest set of fixes ? As I reported RTX 5070 GPU detected as Unknown NVIDIA (2f04) - #13 by dokuro the current beta fails when forcing a client to transcode.
Yes. Though looking through the upcoming beta bump, I don’t see a fix that covers the issue you linked specifically. Thank you for checking out 1.43.1.10183. The transcoder changes added in that custom build will be included. As mentioned in the initial 1.43.x beta release announcement this will be a longer lived beta cycle as we work through all the new issues that this major transcoder change may have caused. Thanks again for your reporting and thank you for your patience while we work through these issues. 
3 Likes
Thanks. Just so we are clear and on the same page, there are two issues in the thread I linked.
1st is minor where the gpu is detected as unknown, actually that’s been this way since I upgraded to a 5070 gpu and is an issue way before this beta.
2nd, however is serious. Transcoding fails when I force a client to transcode, by changing quality as an example. This works perfectly on the pre-beta builds.
1 Like
Yup! Thanks again for keeping us honest.
1 Like
Ill get you that info!
Where do i put these? one example is so small i can just upload it somewhere, the other is a movie, with the new version it simply wont transcode it, just fails, but prior release willl
Not sure if i have the same problem?
I’m running Plex in docker with an Intel chip and as of a few weeks ago has stopped playing certain files.
I was running the latest version which i presume broke it, but downgraded to public and it’s still broken. Currently on Server 1.43.0.10162, Client 4.152.0, Docker image version: linuxserver/plex:latest
When i look at “now playing” in the dashboard, it looks like it is playing but the client side doesn’t get a video. I have tested on Chrome, Chromecast, Samsung TV and all the same. It does work on Apple TV though
One example is 1080p - H.264 - EAC3 audio. When i change the resolution to force a transcode it doesn’t help.
CPU also goes to 100% and stays there even after i exit the client.
Any ideas? Cheers!
