Right now, my server have multiple IP addresses (multiple ISPs). I have one dedicated for CrashPlan (newest), and original one for everything else (Calibre, minecraft server, terraria, etc).
Has anyone been able to develop a patch to fix this bug? It’s been 5 years or so now. Basically makes Plex Server not suitable for a server environment
I’m really annoyed about this. Soooo MANY HOURS wasted because this.
@sa2000 said:
The only change made in this area is Plex Media Server ignoring network interfaces that have no defined default gateway.
Yeah, but actually a network interface without gateway is a missconfiguration causing Windows to mark it as untrusted network beacuse that network cannot be identified.
The real problem is that a network interface with a default gateway IS NOT a guarantee of have internet access, so it is mandatory to allow the administrator to ignore specific network interface.
In my case I have 3 networks, 2 of them has internet connection to 2 different ISPs. The third one is an internal connection with a very restrictive subnet, used for monitoring critical devices (without internet access for security) like security cam recorder. This network device has network metric set to 9999 so when every single software requesting internet connection ignores it because it has the least priority… every software but Plex, which binds to it like it was the only one connection available. Why?
@XumariValencia said:
I’m really annoyed about this. Soooo MANY HOURS wasted because this.
@sa2000 said:
The only change made in this area is Plex Media Server ignoring network interfaces that have no defined default gateway.
Yeah, but actually a network interface without gateway is a missconfiguration causing Windows to mark it as untrusted network beacuse that network cannot be identified.
The real problem is that a network interface with a default gateway IS NOT a guarantee of have internet access, so it is mandatory to allow the administrator to ignore specific network interface.
In my case I have 3 networks, 2 of them has internet connection to 2 different ISPs. The third one is an internal connection with a very restrictive subnet, used for monitoring critical devices (without internet access for security) like security cam recorder. This network device has network metric set to 9999 so when every single software requesting internet connection ignores it because it has the least priority… every software but Plex, which binds to it like it was the only one connection available. Why?
This has been raised internally to consider using the ipv4Metric.
Also, do note, programmatically, you can choose which NIC to use (At least in Java, C#, and C++). We do this at my day job in those languages for server apps. I don’t know what language the Plex Server is written in. But this ability exposed through the Windows API (I don’t know about other OSes), in case it isn’t written in any of the above languages.
Christmas has come early ! The feature of allowing the user to select a specific network interface is now available as from Plex Media Server version 1.13.5.5291 which was released to Plex Pass beta yesterday
I do see that it’s still in beta, but sadly Plex is not finding all of my interfaces. It found my VPN’s ‘tun0’ last night fine without issues. Now it can not do so. I finally found a work around for Plex remote issues and I’m getting delayed because plex can’t locate the interface of my VPN. The bad thing is the two different VPN’s i’ve tried once activated setup default routes with a metric of 0 being all traffic will be routed out from the tun0 interface, and isn’t much Plex can do about that I believe, unless you program Plex to not only bind to our non-VPN interface but to route traffic only though that interface.
@sa2000, do you have any suggestions for a workaround for that default behavior? If not, can you point me to the logic that this applies to in code so that I can modify it?
My network interfaces that I want Plex to listen on are “vlan10”, “vlan20” etc.
Further to my previous reply, I think I’ve found something that could be a bug.
In my case, I migrated Plex from an old physical machine to a VM. I copied over all my plex data and started the services.
My internal connections are not working, so I did some troubleshooting like signing out of the server, stopping services, starting it, signing in, etc. to no avail.
Then, I decided to inspect https://plex.tv/pms/resources.xml and discovered this - it still thinks I’m using my OLD internal IP address.
Again, this is after multiple stops/starts/sign-in/sign-outs. Why is it hanging on to that old IP? If you’re ignoring v* interfaces, how do I tell your backend about my new internal IP? How do I select which interface I wish for it to report?
In case another victim happens to be affected by this, here’s a solution that TEMPORARILY works. Temporarily, because the next time you receive a different IP (due to DHCP, or because you switch interfaces you wish to listen on) you’ll have to do this again.
ifconfig vmx0 name avmx0
You could use any name, just don’t start it with a v (SERIOUSLY, WTF PLEX DEVELOPERS).
I believe the best course of action for a forum post that is very old now. Would be rethink this logic in Plex. Why not adjust it so we could least on NIX based OSes have an option -i (or whatever you want to call it) to force bind to a certain interface(s).
There has been some work done by the development team to better handle network adapters with names starting with a v
If you are interested, I could make a development build available to you to try out. I will need to know platform and exactly which binary/package and filename you use for installs
For anyone that has network interface with name starting with “v” and actual is the one to be used, please see release notice for Plex Media Server 1.15.7.1079
IP addresses from interfacing starting with a “v” weren’t published (#9576)
