Closed magn2o closed 5 years ago
I can't edit your issue, but please remove your IP address :/
Does the transcoder also find the file it should play on the transcoder server?
The log has already been anonymized, that’s not my real IP. Thanks, though. :)
I don’t see any errors regarding not being able to find a file, so I assume so?
Is the created folder empty on the transcoder when you start a video? The file must be on the same path as in Plex.
Can you give as a screenshot of Chrome devtools when you start a video ? Can you see a 302 (redirect) request to your transcoder ? Are the initial.mp4 and chunks requested on transcoder or on your main domain?
Did you removed Plex Relay and drop 32400 port ?
Ok, so Chrome Dev tools exposed more details. The following is constantly repeated:
GET http://144.76.41.56:3000/video/:/transcode/universal/dash/c8688xsz2n81s63jkznef7h9/1/initial.mp4 404 (Not Found)
GET http://144.76.41.56:3000/video/:/transcode/universal/dash/c8688xsz2n81s63jkznef7h9/1/0.m4s 404 (Not Found)
This leads me to believe I have a misconfiguration somewhere, but not sure exactly what.
And yes, port 32400 has been dropped and the Plex Relay binary was removed.
Ok, problem solved. I'm an idiot and overlooked that the media share wasn't available to the loadbalancer. Once I remedied that, everything started working perfectly.
Running latest master pull for all 3 components.
I've been beating my head on the wall for a week with this. As far as I can tell, everything else is working. LoadBalancer is handling incoming connections, passing through to the Plex Server, and routing requests to the transcoder. The issue presents itself as soon as the transcoder receives a request:
That's pretty much it. The Plex Client sits, spinning indefinitely waiting for content which never comes.