404 Error "Callback -2" (on video files) after 'start.mpd' has returned it's successful response

Hi there guys,

I’m in the process of setting this up in a dockerised deployment (everything is up to the actual transcoder) which I’ll push up to github once it’s all working for others to easily deploy…

Currently as it stands:

• Environment is running behind Caddy reverse proxy for Lets Encrypt SSL’s
• Loadbalancer & FFMpeg replacement components configured & working fine
• When the request to the /video/:/transcode/universal/start.mpd is intercepted by the load balancer and then 301’d to the actual transcode worker I get an initial response from the Load transcode worker (with the XML body as expected) however then when the Plex client requests the initial.mp4 file I simply get the 404 response: Callback -2 from UnicornTranscoder’s Express.

Could anyone give me any feedback on what this may be / where to look?

I’m Currently running the latest commit in Master (so Version 2.0 I’m assuming) Happy to share my Docker files also which might make it easier for developing.

Cheers,

[drouarb]

Your output log shows http://127.0.0.1:3001/api/ffmpeg in the transcoder. This route is called by UnicornFFMPEG, it shouldn’t be run by the transcoder. UnicornFFMPEG is a binary that should replace Plex Transcoder only in the Plex Media Server folder. It is used to push arguments to the UnicornLoadBalancer so the UnicornTranscoder can pull them to run the real Plex Transcoder on his side. Just remove the plexmediaserver in the UnicornTranscoder folder and run npm run install and everything should work fine.

[Maxou44]

/config/Library/Application Support/Plex Media Server/Cache/Transcode/Sessions don’t need to be shared with the transcoder, only between Plex and the LoadBalancer.

---

2019-03-21T10:09:24.564Z UnicornTranscoder:Transcoder Failed to start waapgtycm0rv4b5dkfp2adca: StatusCodeError: 400 - "{\"error\":{\"code\":\"SESSION_TIMEOUT\",\"message\":\"The session wasn't launched in time, request fails\"}}"

It means, the UnicornFFMPEG didn’t sent arguments to the load balancer, in general it’s because UnicornFFMPEG wasn’t setup or it don’t have access to the load balanacer (URL configuration)