Server Version#:Version 1.42.2.10156
Player Version#: Any
I have two internet connections connected to a PFSense router with dual WAN. I have set rules to force them down one connection. However Plex seems to ignore this and starts moving to the other connection that does not work for remote access. How do I stop Plex from thinking it is on the Internet connection that does not have the ports open.
This sounds more like a PFSense question than a Plex question - you might have better luck asking on PFSense boards.
Its been a minute since I’ve used PFsense - but it sounds like you need a firewall rule with the gateway of the wan you want used set (ie: source is plex host, dest is wan, route via gateway (the wan you want).
i dont remember if the default behavior is fail-over or load balancing on pfsense multi-wan.
I have set that up. I also have setup forward rules on on and not the other. When I test it, it works fine. Some time later it will think it is on the other Internet connection and claim it has no access. Since there is no STUN settings I would really think this is in the code of the plex.tv server. tshark tells me it is doing SSDP over and over. Worse than a Roku box.
I’m multi-wan myself but don’t use port forwarding any more for external access.
when I was I did have a similar issue however using policy routes + firewall rules to lock all outgoing traffic for plex to a single WAN fixed the issue for me once their dns picked it up. If you know how to use their API and check for all the lists dns names for the server it should only list your internal and the WAN you want (+ any custom ones you set).
I don’t use UPnP so unless that’s registering it on the other wan (if you have it enabled).
edit: also keep in-mind that you’ll need to restart plex and i’ve seen the update take abit of time sometimes.
This is not a firewall issue. I already have policy based routing. The issue is when setup it will work fine on WAN1. It will show proper routing. And then without any interventaion or change it will flip to the other WAN2 that is not setup for ingress.
This again, is not a firewall issue. Nor routing issue. In fact if I route everything from the system out the WAN1 that works it will revert back to the one without the WAN2
Plex Media Server publishes its public IP address based solely upon the IP address resolved by visiting https://v4.plex.tv/pms/:/ip. If this changes over time for any reason, then the published IP address changes.
(https://v4.plex.tv/pms/:/ip returns the IP address from which traffic was received from PMS.)
You may want to consider using a custom server access URL if you can’t figure out how to set up policy-based routing correctly.
Thank you — this was the piece I was missing. Using Wireshark, I noticed the system making HTTPS calls, but I assumed they were just version checks. I redirected all HTTPS traffic to the same interface, and everything seems stable now.
Awesome, glad you got it working!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
