Same problem here on Windows 10. I have one gigabit NIC and one virtual NIC (ZeroTier). Setting “Network interface to listen on” to the gigabit NIC makes no difference, remote access always try to use the ZeroTier one, which is a virtual LAN with no internet access.
It worked a few updates ago.
VPNs are the nemesis.
PMS does not control its outbound socket.
ServerBindInterface only controls where the HTTP server is (Engineering’s decision).
All socket communication is otherwise “as the OS deems appropriate”
I’m not using a VPN.
Do you have a solution yet?
I have the exact same problem on my Ubuntu server. For some reason PMS is still reporting that its using the wrong interface (my interface for SMB sharing only -> no internet/gateway connection) in the “Remote Access” tab, but my friends are able to access my PMS from other networks. Yet every time I reboot my server I have to disable and re-enable the Remote Access before it actually works. Am just guessing but it seems to be that there is a little bug with the latest version of plex, because I have used this same setup for 2 years and never had any problems with it.
I created a bond on my Synology for my house to use and left 1 NIC open for the rest of the world. In Plex under Setting–> Server–> Network. I changed “Network interface to listen on” to the IP I wanted it to listen for traffic on but under the remote access setting it is showing the wrong IP. I have restarted my NAS and everything. Any thoughts on how to fix this?
If both the Bond and the solo NICs are on the same subnet, your only alternative is to remove the Gateway address from the Bond0 adapter.
By removing the gateway address, the Linux networking stack will do what PMS can’t.
Interface selection only controls the HTTP server, not anything else, at this time.
We’d hoped for more but this is where it’s at.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
