Hi,
I am running Plex Media Server in a Kubernetes environment with reverse proxy setup so i can acccess my plex using https://plex.mydomain.com which works fine however i am pretty sure when i play from local network it goes over the internet to bounce back. From documentation i am guessing that i need to set the local ip range in LAN Network which is only available for Plex Pass. Is there a way i can see in the log what plex considers as local or should i just assume that whatever ip the media server has X.X.X.X it uses X.X.X.0/24 of that ?
btw. when i access https://plex.mydomain.com locally i have a local DNS server which resolves to the reverse proxy which then forwards my request to the Plex media server.
Thank you ChuckPA, i added the subnets in LAN Networks but i have very unstable connection, the server disappears on my devices being on the subnet i specified and it may work once then the second time it doesn’t work, it’s on off all the time. I looked at the logs and i see : Request: [10.42.0.111:38538 (WAN)] GET /activities (13 live) GZIP Signed-in Token , Does WAN indicate it’s goes thru the WAN or how should i interpret this ?
As mentioned earlier, my server can be reached on https://plex.mydomain.com . I run reverse proxy. The server itself is running on a different subnet. In Plex i disabled remote access since i understood that should be disabled when i run reverse proxy. What other settings should i be looking at ?
You are correct in your assumptions about a cluster environment. In my case that should not be the case. I don’t run it distributed. In fact i only have one host/node/machine. I run in it in this environment because i use it for my other docker containers and it’s a nice environment to organize the containers in. Just because PMS see this as a remote connection it doesn’t necessary mean the traffic goes thru the internet right ? How can i make sure it’s not doing that ?
I would ensure your network topography , in particular your netmasking, is such as to make it wide enough. By default, most networks are /24 in the home environment (255.255.255.0 netmask). This means 192.168.0.x is different than 192.168.1.x.
If you widen the mask to /23 (255.255.254.0) those IP ranges now become the same LAN. All hosts on those nets must have their netmasks updated.
You can effect the same with your 10.x.x.x (usually also a /24 in a home environment) because it’s a non-routed RFC-1918 block.
Yes i know. My local network is 10.10.0.0/24 (the network i access plex from). I do also have a VPN network which is 10.10.20.0/24 so in Plex LAN Networks i put the two networks. From my point of view everything is good. Still sometime the server drops out from Plex. What should i be looking for to troubleshoot this ?
If you’ve entered the subnets, are the logs reporting errors with the specification?
PMS is very exacting about what it will accept and Plex/web doesn’t perform any error checking or formatting. If it’s incorrect in any way, it will be quite loud about it in the logs. Restarting PMS is a good way to see if everything is being picked up correctly. (DEBUG logs, not VERBOSE)
