Plex client 404 Error fetching transcoded stream

[starcraft66]

Hi, I've deployed kube-plex along with the rest of my mediaserver stack using Kustomize.
Everything seems to be working (communication between the plex transcoding pods and main PMS instance is working perfectly) but when I try to play a video on plex, it never starts and when looking at the Network tab of firefox's debug tools, I can see that the plex webapp is hitting 404 errors when querying plex's /video/:/transcode/universal/dash/<long string> http endoint.

I'm really lost as to what the cause of this could be. I made sure my main plex pod, as well as the elastic transcode pods have the same /transcode volume connected with a ReadWriteMany NFS PV. I confirmed that the main plex instance's /transcode volume is populated with the transcode result by execuring a shell inside the container and confirming that /transcode/Transcode/Sessions/plex-transcode-<long string>-<some uuid> exists and everyone has the permission to read the dozens of .m4s files in there. I confirmed that plex's transcode folder is set to /transcode in the settings web interface as it should be.

What could be going on? I tried straceing plex to find out what files it was trying to open but I was having issues with strace not showing any open syscalls after attaching to the process using strace -fff -p <pid> -e trace=open.

[ThePrincelle]

Same issue on my end. Really frustrating because aside from that everything is working.

[karezza]

same here

[djeebus]

I had the same issue; for me it was b/c I was trying to transcode a video in a volume added via extraData. those mounts aren't added to the pms-elastic-transcoder pod, so it ended with a 404. switching that mount to the data mount fixed my issue.