-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
k8s localRelayEnabled results in transcoder error (502 Bad Gateway) #328
Comments
Let me try to reproduce it |
I'm seeing this as well. Transcoding appears to work, but quite a number of 502 errors much like shown in the initial comment. Direct plays are working without issue, fortunately but I've gotten reports of some instances where things just spin at playback attempts. @AngellusMortis Are you able to elaborate on what you did to get things working? When you say disable the relay, I assume you mean in both the chart as well as the Plex settings. I tried this as well as adding the SVC IP for PMS as described ( I actually added all private CIDRs and the specific IP to the 'List of IP addresses and networks that are allowed without auth' section ) and I was not able to get things working. Perhaps I'm missing something but wanted to confirm. Thanks for your time. |
The relay in Plex settings has nothing to do with this relay. The Plex settings relay is to relay via Plex's servers if it cannot direct connect. The relay in the chart is a nginx reverse proxy to let the other worker pods access Plex without authentication. You can whitelist all the IPs of worker pods and then set the |
Thank you for the clarity. Unfortunately even when I disable the relay in the chart, whitelist all private range CIDR’s in Plex setting and set the value of
I’m running k3s v1.28.3+k3s2 on top of FedoraOS. I’ll continue testing and report back if I discover anything. Thanks, all. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
From looking at those nginx logs it would appear that the plex transcoder is sending duplicate header lines for Content-Length. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Describe the bug
Using the default setting for the local relay in the Helm chart for k8s results in the transcoder failing. In the
plex-worker
logs, it looks like it is getting a 502 Bad Gateway when it tries to post the chunks back to the relay.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Transcoder should work as expected.
Screenshots
plex-worker log
nginx error log for relay
nginx access log for relay
Desktop (please complete the following information):
(not a client issue)
Additional context
Cluster is on bare metal running Talos OS 1.7.6 and k8s 1.30.3. PMS is 1.40.5. Cluster Plex is 1.4.13 (latest everything, just installed today).
Disabling the relay, whitelisting all IPs and adding the plex-pms service IP to the
pmsIP
in the Helm chart fixes everything.The text was updated successfully, but these errors were encountered: