Server Version#: 1.15.6.1079
Player Version#: All including web app.
Hi There!
I recently moved my Plex instance into a kubernetes cluster and I am having issues getting Plex up and running externally. My setup is a bit complex so bare with me:
1x EdgeRouter X with port 32400 open to the VIP (252)
2x pfsense w/ HAProxy Load Balanced on a VIP (252), firewall configured to allow 32400 to the service (listed below)
1x K8S cluster running under Rancher
1x Plex pod within the cluster in it’s own namespace in a host networking configuration with backups performed through velero
I am able to hit all of the CSA URLs and load plex internally so they are resolving correctly. I have confirmed via https://www.yougetsignal.com/tools/open-ports/ that 32400 is open but it won’t setup the remote access. It will load green for the remote access on Private and Public, then it breaks almost immediately after.
Plex also only loads insecurely. I’m guessing that may have something to do with it.
Anyone have any ideas? At this stage, I’m thinking it could be an issue with the Plex.tv servers as I can reach it externally over 32400. My account also had a warning on it. I signed out of the server, removed it from the “Authorized Devices” and re-claimed it. Same problems…
Does your cluster present ONE host to Plex.tv or multiple?
Plex is not designed for a multi-host cluster. It’s not intended for enterprise level architecture usage as shown in this image.
Hey Chuck, it only presents one. I only have the singular host and will only have the singular host. I have removed any other hosts from my network. I am using PFSense with HAProxy to make it routable and can reach it outside of my network by going to http://External IP:32400/web.
As near as I can tell, no rhyme or reason it shouldn’t work. I have a colleague who has this setup without issue. I even implemented his configs.
If you are not tunneling the cert through, which a proxy will interrupt, you’ll never go anywhere with it within the plex.tv domain.
PMS and Plex.tv need that SSL connection. Injecting oneself as a MITM (a proxy) without proper handling, will break it and stop it from working every time.
Ok so it needs SSL open to the web to work. Does it need anything else open? I can open whatever ports. Just need to know what as it’s not outlined in anything I found.
Ok, so, wasn’t a port issue. In HAProxy, the front end for the plex connection from the firewall was the wrong type. Changed the type to “TCP”, re-deployed plex and everything is connected. Seems stable, will monitor for a few days.
