I have a home server running Ubuntu Server 18.04 that is my router for my entire network and my server connects to a virtual router running OPNsense. Port forwarding is open for 172.20.0.1 which is the address for my home-server however Plex sees my home-server as 172.20.0.97.
My server has four subnets:
172.20.0.0/27: Home Server: 172.20.0.1 (br0)
172.20.0.32/27: Home Server: 172.20.0.33 (br10)
172.20.0.64/27: Home Server: 172.20.0.65 (br20)
172.20.0.96/27: Home Server: 172.20.0.97 (br30)
The DNS name is home-server and points to 172.20.0.1. I also have it pointed to 172.20.0.33, .65, and .97 in case one of my bridged interfaces go down.
172.20.0.2 is the address for OPNsense, so if my laptop is in 172.20.0.40 and were to access the Internet:
172.20.0.40 -> 172.20.0.33 -> 172.20.0.0/27 -> 172.20.0.2 -> Internet
I want the Remote Access to use the 172.20.0.1 address and not 172.20.0.97 address, which listens in br30.
How do I do about configuring my home server/Plex Media Server to listen in 172.20.0.1 for remote access?
Anyone who have configured their server with multiple subnets as a router can be of assistance.
Plex still insists in listening to 172.20.0.1 despite telling it to listen to 172.20.0.1 even though 172.20.0.97 is listed by Remote Access. I suspect it’s because br30 is the first interface Plex finds when starting PMS.
So I took at look at “ip a” (“ip addr” or “ip address” in Linux command line) and br30 shows up first in the list. I don’t know how I can reorder the bridged interfaces, so I thought I would switch the two interfaces (enp4s0f1 as br20 and enp3s0f1 as br0 with vlan enp3s0f1.10 for br10 and vlan enp3s0f1.30 for br30). My computer is connected to enp4s0f0, which is bridged to br10.
Now that enp4s0f1 has br20, Plex decided to listen to address 172.20.0.65.
To summarize:
enp3s0f0: assigned to virtual router
enp3s0f1: assigned to br0, with VLANs assigned to br10 and br30 for wireless access point
enp4s0f0: assigned to br10
enp4s0f1: assigned to br20
Previously, this is how I configured before the switch:
enp3s0f0: assigned to virtual router
enp3s0f1: assigned to br20
enp4s0f0: assigned to br10
enp4s0f1: assigned to br0, with VLANs assigned to br10 and br30 for wireless access point
What I can tell from Plex’s remote access is Plex grabs the IP address from the last interface.
Plex is not adhering to preferred network interface in Network settings when it comes to configuring Remote Access. I can test my theory by switching out the cables and the bridges for enp4s0f0 and enp4s0f1 and Plex could be assigning 172.20.0.33 as the private IP address in Remote Access, but I want to leave the interfaces as it is. And yes, I did restart PMS no matter what I do.
Update: I forgot to switch out the VLAN from enp4s0f1 to enp3s0f1 and now it listens to 172.20.0.97 despite setting the preferred network interface to br0 (172.20.0.1). The only way to force Remote Access to listen to 172.20.0.1 is to disable all the bridges except br0 and disable the two VLAN interfaces, but that seems extreme because if I need to restart PMS, I’ll have to disable all the interfaces again except br0.
This would be great. I have a windows server with two interfaces. One is connected directly to the net and the other is connected to my LAN. If i connect from a client on the LAN, it says the connection is remote and limits the connection to my setting of 720p for remote users. I use plex media player mostly, so i just added the servers LAN ip as a local server manually and now i can see my 4k content. This doesnt seem to be an option in the windows 10 app (from the app store). I can add it in the fire stick though, so that covers 90% of my use. I only have one device capable of 4k right now, so its not a huge deal, but i hope they fix it soon!
Yes, i added the LAN to the windows plex server config as a local subnet, but i still had to modify the client too.
This topic is about EXPOSING Plex Media Server to the outside world with just a single IP address. Plex Media Server does not understand that I have multiple subnets configured for my network. This isn’t about adding multiple subnets as that won’t help with getting Plex to use a single IP address for exposing a remote connection from the world to my PMS.
Plex Media Server expected me to use 172.20.0.97 for port forwarding while I insisted in using 172.20.0.1 instead! I added a destination IP address of 172.20.0.1 with a port of 32400 for port forwarding in my router and PMS still can’t communicate unless I specify 172.20.0.97 in my router.
172.20.0.1/27, .33/27, .65/27, and .95/27 all leads to my home server and these are my four subnets. If I add a fifth subnet (.129/27), then Plex will use 172.20.0.129 as it’s IP address and I don’t want that to happen.
How Plex does the HTTP server is not how you think of the traditional bind() action.
Engineering decided to move the HTTP server only.
They have no control over the actual outbound IP address (which is what bind() does).
Instead, they changed which IP address (by filtering) it listens to.
This wasn’t what was requested but is what we got.
Sorry that it works the way it does but if you want to use a specific IP, your best hope is to put PMS in a VM with one bridged adapter which is assigned to the specific LAN subnet you want to use.
