Two local servers showing up as "Remote" all of a sudden

Plex Media Server Desktops & Laptops
1

Server Version#: Latest
Player Version#: Latest

Having troubles and appreciate any assistance.

Both of my Plex servers on my home network are showing up as Remote as of about three months back. All player devices on the network are affected. I have two Windows Servers running the latest Plex server version, three Win10 PC’s, and a Roku Ultra all affected. PMP, OpenPHT, WebClient all affected. Subnet is 192.132.4.0/255.255.255.0

  • One server has been working fine for years. The other was freshly loaded two months back and had issue immediately.

  • Connecting directly to the servers via http://IP:32400 still shows them as “Remote”

  • If connecting to a server via it’s locally installed web browser, that server shows as Nearby. That server in turn sees the other server as Remote despite being on the same LAN subnet.

  • Router has DNS Rebind turned off

  • Servers and player devices all use Google as their DNS resolvers

Something interesting while researching the problem. The output from following https://support.plex.tv/articles/206721658-using-plex-tv-resources-information-to-troubleshoot-app-connections/?_ga=2.151753727.75313420.1544316239-985537623.1464742070.

<Connection protocol=“http” address=“192.132.4.25” port=“32400” uri=“http://192.132.4.25:32400” local=“0”/>

<Connection protocol=“http” address=“98.29.REMOVED” port=“32400” uri=“http://98.29.REMOVED:32400” local=“0”/>

Why is the “local=” flag not set to 1 since it is local?

2

Neither of these networks is in the IP range designated for private networks.

These are publicly routable IP ranges and they should not be used in private networks - even if they are behind a NAT router.

That’s why Plex is classifying these as ‘remote’.

3

Thanks, OttoKerner! I had this noted from other posts, however, that one of these servers and it’s predecessor worked for years configured this way leads me to believe this is not simply a private/public subnet problem. Unless someone knows for sure that within a recent Plex update how Plex handles this was changed.

The below setting has also proven ineffective:
LAN Networks
Text box: 192.132.4.0/255.255.255.0
Comma separated list of IP addresses or IP/netmask entries for networks that will be considered to be on the local network when enforcing bandwidth restrictions. If set, all other IP addresses will be considered to be on the external network and and will be subject to external network bandwidth restrictions. If left blank, only the server’s subnet is considered to be on the local network.

4

This setting will only lift the bandwidth restrictions for remote access, which are defined under
Settings - Server - Remore Access

It will not switch the server classification from ‘remote’ to ‘local’.

5

Got it! Thanks for that. I was unsure.

6

Little update on this. Strangely, with this setting enabled for the 192.132.4.0 subnet it still restricts the bandwidth usage to what is set as remote limit under Settings - Server - Remote Access. Is there somewhere else in Plex I am forgetting where bandwidth to devices (not web clients) is set? Otherwise, this setting appears not to be working for my setup.

Thanks!

7

What exactly did you put into it?
Did you restart the Plex server after changing this setting?

8

Thanks for the help, OttoKerner. I did restart the entire server. I also restarted all streaming devices (PC’s & Roku). My local subnet was already entered in that box on the older server so all this tweaking is being done to the new server. I have been trying to find anything different between the two since the older one worked for years with no issue.

9

I am afraid that I have no other ideas left than to recommend you to use a proper ‘private’ network address. Which means reconfiguring at least your router.

10

Follow-up on this topic. I went ahead an changed my network subnet over to a private range and all the functionality that stopped working about four months ago is working again.

So, if you start having any issues similar to the above, you will have to move to one of the established private ranges. Whether due to changes with you ISP, how you firewall handles traffic, or Plex’s new view on updates/features this no longer works without the private subnets.

Thanks to all who offered help!

1 Like
11

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