I have 2 local networks in my house. 192.168.xxx.xxx is local to the Verizon FIOS router. My Plex Server has one adapter connected to this network.
The second network is 172.24.1.xxx and my Plex Server has another adapter going to this network. This is the network that my NAS is on and all my local devices. This network is behind a BOX 2 Virus Scanner.
This is wild goose guess without looking at the log files (which
wouldn’t do me any good anyway).
Years ago I installed MythTV on a Linux computer with 2 network
cards, eth0 (on motherboard, 100M) and eth1 (separate PCI card,
1G). I was using eth1, and I couldn’t get MythTV to work (everything
else worked). I finally figured out that MythTV had eth0 hard coded,
period. I was able to disable eth0 in my BIOS, turning former eth1
into eth0, and whammo, MythTV liked that.
Perhaps Plex is doing something similar. If I understand you correctly,
you have 2 ethernet cables plugged into your Plex server. Consider
turning off the server, swapping where the cables are plugged in,
and restarting. It might be a stupid idea…
You will need to manually port forward (you seem like you have the know how) That preferred network interface is only for local clients to connect, it does not tell the router which IP to use for UPnP
@damtor@BigWheel Thanks for the replies! I have fixed the issue and want to share. It’s obscure.
So I am running Ubuntu 19.04 and have one interface going to one network 192. And another going to the 172 network.
The 2nd adapter I configured manually under /etc/network/interfaces
I had one configured automagically by Ubuntu through NetworkManager and since I did the 2nd one manually through /etc/network/interfaces it screwed things up in Plex.
Once I had them all configured through Network Manager Plex had no problems binding to the correct address.
