Windows Users:
I tried the app ForceBindIP - You can specify a NIC or specify and IP per .EXE
For example:
“C:\Program Files (x86)\ForceBindIP\ForceBindIP.exe” -i 192.168.1.70 “C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe”
Unfortunately Plex will load, and seems to be bound to the correct NIC, however, Streaming isn’t working and I cannot access the Server info tab within Plex.
+1 I also have a QNAP NAS and Plex is binding to the docker bridge interface, not the br0 default network connection (this mean’s I can’t access outside of my local network - very frustrating).
+1 this does seem just slightly…stupid. The NAS based installs like QNAP with muliple adaptes and multiple IP’s PLEX seems to respond on all of them. I’d like to bind it to ONE adapter and one IP, although…I can see how maybe having it bound to all can provide some redundant connectivity if the player apps are smart enough. Problem is externally you can only forward to one IP anyhow…so it stands to reason that if multiple IP’s are detected you should have the option of 0.0.0.0 OR selecting a specific IP that is available. This is a non issue on single machine installs like Linux, Windows, Mac for the most part most people don’t have multiple IP’s but since PLEX supports NAS installs this should be an option on those devices.
+1 for me, seriously!! I consider this a basic configuration option in all of the programs I develop, what’s taking so long?.
+1 please develop these feature
+1 PLEASE DEVS! This request has been sitting idle for years!
Problem: My Plex host has an internal 192. address for my local network and a 10. isolated address to connect to storage. With Plex not being able to blacklist/whitelist addresses or interfaces things like Mopidy-Plex get broken because Plex reports the 10. isolated address back to the client (which is obviously useless).
Bumping on the issue.
In my case, my Mac requires to have both Ethernet and WiFi running at the same time. I won’t discuss why. It doesn’t matter why. This is networking 101. It’s a simple feature that any programmer worth their weight can add in a couple of days (if not less time). I shouldn’t even be calling it a feature. The fact that it’s missing defines this issue as a bug. Plain and simple.
So this bug has a simple fix, and has been KNOWINGLY lingering for four years. FOUR. YEARS.
If it’s a matter of not having enough man-power to do the job, hell, I’ll volunteer my time to just get it over with, because this is depressing.
I’ll say +1 also. I think it would help me with an issue too. I have several products wanting to DLNA from a single machine. So, you say this is a problem as there is a common port. Exactly, so, the solution might be to add a second IP address, and, bind product A to IP1, and, Plex to IP2. Each can now provide DLNA services from the same machine and not conflict.
Please, please please implement this! Can’t have remote access while using a VPN for everything else. This is absolutely essential.
In August 2012 tobiashieta announced this feature to be on the roadmap. There are many votes for this improvement in this thread, the Plex team has brought out release after release and added device after device but still no way to bind the server to one or more particular interface(s). This is a security relevant feature! How many more votes does it take to make the Plex team to act on an important and simple to implement feature? Anyhow, I’m throwing in my +1 too.
+1 common Plex… there are a lot of people with this need… support us, please!!!
+1
every user with QNAP and docker containers may come across the issue.
mine started with random disconnects and “cannot find server” and then after the last update, i was forced to delete the docker app and remove the network interface
Plex is awesome…except the complete radio silence when it comes to features especially security relevant ones like this. This should be so easy to add to the configuration UI on the server for any all all version versions of the server app. It’s especially needed on the QNAP with multiple interfaces.
Can the devs stop ignoring this please?
It’s been years… this is kind of bull…
I have one server.
It hosts multiple virtual machines on one dedicated network interface that uses 172.16.13.x as the subnet.
Plex is supposed to use the Host’s other interface 10.0.0.x but refuses.
I have tried re-arranging eth0/eth1 to see if plex will take a higher/lower interface number.
It seem’s like plex just chooses the 172 subnet over the 10.0.0. subnet, so if I want this to work, I have to re-ip address all my systems, firewall entries, port forwards, web sites etc.
All because plex, won’t let you bind to an interface.
This app is great and all, but its probably all copy/pasted code if they can’t implement one of the most basic features that is in almost all network based software.
I’ve found an alternative Plex type software… in time they will become more polished and probably overtake Plex with market share due to problems exactly like this thread we are posting in now
…
Soon Plex will lose my subscription, and all my friends who view…
We will all make the switch.
There are a ton of threads just like this… Tons of +1 +1 but no comments from the dev team. Is the Plex dev or marketing team active on these boards at all?
this crap is back… plex wont let go of the wrong adapter
I have ens33 as the regular 192.xxx adapter and 10.55 as an internal to esxi only data network that has NO internet pathway…
it is choosing the 10.55 adapter … and get this… its getting a green light but saying not directly connecting… is plex bridging my networks withoug authority?
getting the warning that the connection is not direct…
I had this fixed for awile and after 1.7.3 alot of stuff is no longer working well… mkv playback to apple tv for one…
Depending on how Plex is started on your particular distribution I don’t know all the in’s and out’s of how you might be able to do this, based on the different ways Plex is started, but:
I just did a similar exercise with HDHomeRun’s recorder software which always picked my WAN adapter in preference to the LAN and so always complained that the DVR was not available. Here’s what I did:
Use a network namespace to run the software. Bridge the “root” end of the veth pair with the interface you want it to bind to. That way whatever you run in the net namespace can only connect to the interface defined there, not all the interfaces available. My LAN interface was already a bridge, so I just had to add the new virtual ethernet to it. If this is not the case, then my understanding is that you set you current interface to an IP of 0.0.0.0 then after creating and adding the interfaces to the bridge, you assign the IP/gateway to the bridge:
ip netns add HDnet
ip netns exec HDnet ip link set dev lo up
ip link add veth0 type veth peer name veth1
ip link set veth1 netns HDnet
ip netns exec HDnet ifconfig veth1 192.168.0.201/24 up
ifconfig veth0 0.0.0.0 up
ip netns exec HDnet route add default gw 192.168.0.254
brctl addif br0 veth0
ip netns exec HDnet <start the application>
Cheers.
+1 really need this on my server
This is a sorely needed feature. They can pull off authentication by IP/subnet,m but can’t add in a simple “bind-to” function?
cmon Plex devs! this is pretty important especially with the rising need for VPN’s these days
It’s pretty telling where priorities are when this request dates back three years without a hint of information. It is a fundamental configuration of all network applications. Instead we have to make a work around, makes me wonder what alternatives there are.
