-
Big fan of the project so far! My external clients coming in to watch Plex remotely are working great. Here's the arch: Remote Client --> Custom URL (https://replex.custom.domain) --> CF Proxy --> Pfsense --> Traefik --> Internal Replex Host (192.168.8.8:3001) --> Proxies to Plex for streaming (192.168.8.8:32400) This config is working great as-is from the outside. But, the internal clients on the same network as Plex are struggling to ever hit Replex (LAN network cidr is added to settings). I have an internal DNS record so that replex.custom.domain resolves locally. The internal Plex clients are skipping right past Replex now. What am I missing here? It feels like dns caching on the clients (Roku, Web, Android, HTPC). As I can sometimes see Replex on first startup of a client, then after a refresh Replex collections/heroes vanish and we're directly connecting to Plex. Any assistance is much appreciated 🙏 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
I'm not sure as I don't use it internally. But I know plex is bad in managing the different routings. It's registery usually hold old entries. Might want to check what endpoints are still avaiable internally. for example plex has docker endpoints that it tries to connect to. This is my instance. It can't connect to it but if it could it might pick that above the domain. might wanna check it out for your server with something like https://apps.apple.com/nl/app/varys-for-plex/id1450380518?l=en-GB (used for the screenshot) there are other options like inspect the network panel in the web app. I'm the end the trick is to block everything out to plex except traffic coming from your reverse proxy. |
Beta Was this translation helpful? Give feedback.
Ow en try to disable gdm in the network: Enable local network discovery (GDM
Also if running docker for plex don't use the host network option. As it will bind to your server ip. Just open the 32400 port with docker