Plex Remote Access IP Address Confusion

Plex Media Server Remote Access
1

Server Version#: Latest
Player Version#: n/a

The Plex Media Server is on static IP 192.168.1.1.18 (Linux)
Port forwarding is enabled. The router shows 192.168.1.18:32400

I enable remote access in PMS

After some activity I get remote access enabled with
Private 192.168.1.157 : 32400 ← Public 113.52.144.50 : 32400 X Internet

Scratching my head I do > ip a - I don’t see 192.168.1.157 - the ip address for the server is reported as defined 192.168.1.18

I check the router. There is no device connected with the IP 192.168.1.157

I drop 192.168.1.157:32400/web into the address bar. Bingo, the PMS on the LAN appears.

I try 192.168.1.18:32400/web - hey, it works as well. WTF?

I test remote access on https://app.plex.tv/desktop/#!/ and on my bat phone (wireless network disabled). Everything seems to be working.

I check back in settings; " Not available outside your network", still showing local I 192.168.1.157

Yet, remote access is working.

I’m confused.

Remote Access over VPN?
2

Do you have the server advertising itself as 192.168.1.157 (Settings - Server - Network - Show Advanced) ?

Is it in a container?

3

Sit tight. The Ubuntu Server Gods & Demons have just revealed their dastardly ways:

enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d4:3d:7e:48:ac:5b brd ff:ff:ff:ff:ff:ff
inet 192.168.1.157/24 brd 192.168.1.255 scope global noprefixroute enp1s0
valid_lft forever preferred_lft forever
inet 192.168.1.18/24 brd 192.168.1.255 scope global secondary noprefixroute enp1s0
valid_lft forever preferred_lft forever
inet6 fe80::62af:afba:7d9c:3cb9/64 scope link noprefixroute
valid_lft forever preferred_lft forever

Working on it.

4

Sorted by deleting the extraneous ip address:

sudo ip addr del 192.168.1.157/24 dev enp1s0

It seems to be holding and Plex remote access is now reporting as expected.

Thanks

5

The extra IP address was due to the linux network-manager. The ethernet connection was configured to autostart a VPN connection to the internet, which generated the 192.168.1.157 IP address.

Removing the auto connect and starting the VPN manually fixed things. Sort of, as discussed in this topic.

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.