Incorrect nearby/remote detection dependent on both IP/name resolution and secure connections setting

It’s almost exactly the same issue here Server not recognized as local if accessing by DNS name in LAN

But a bit more to it.

With encryption off:
http://nas:32400 => nearby
http://192.168.0.2:32400 => nearby

With encryption preferred:
http://nas:32400 => remote/direct
https://nas:32400 => remote/direct
http://192.168.0.2:32400 => nearby
https://192.168.0.2:32400 => nearby

Using plex.tv/web mirrors using “nas”

On the client, ping nas => 192.168.0.2
And traceroute nas => 1 hop, straight to the destination.
Both computers are on the same subnet 255.255.255.0

Unfortunately I couldn’t make heads or tails of that other thread, my networking knowledge is very limited and I’m not running a QNAP box. In addition it looks like the bug extends to encryption settings as well which was not covered in that thread.

I am running Arch Linux on both server and client. Plex is up to date. I have had this bug for ages and worked around it by disabling encryption completely but I was just having trouble connecting remotely via the Android app without encryption so thought I’d make a thread.

What’s going wrong?

That doesn’t make any sense. Unfortunately don’t know how Arch handles DNS or how well PMS works on it (not supported on Arch).

Thoughts which come to mind:

  1. Local domain naming: .lan is the correct domain for lan-local domain name. .local was discontinued due to conflict with mDNS (Apple)
  2. All hosts here are members of my .lan domain (hessen.lan). QNAP, Synology, and Fedora all see everything as local.
  3. The DNS resolver (pfSense) provides hessen.lan search resolution.

One thought which might come into play… DNS rebinding protection in your configuration.

Define *.plex.direct as a private LAN in the DNS resolver. Something is jogging my memory on that about Local/Remote

It’s neither nas,lan or nas.local for me, only nas resolves to the right IP. My crappy ISP provided router doesn’t let me change any DNS settings so I’m not sure what I should do. I just double checked each configuration and it is happening to me as written. Would any logs be useful?

Does that router allow you to turn off “DNS rebinding protection”?

My ISP doesn’t have the best router either. I finally put it in purchased a pfSense (netgate) box and reconfigured their modem/router to be just the modem (RFC-1483 transparent bridge mode). My pfSense box is now proper router and stateful firewall which I have control of.

It does not. but I am still convinced it’s a Plex bug at least partly, because it depends on the setting set in PMS rather than whether I am actually using https or not. I have rebuilt my server using Debian Stretch and I am running the official Plex Docker image with host networking. It has the same issue. I don’t even need to refresh the page after changing between disabled and preferred encryption for the remote/nearby status to change. I’ve attached a video to illustrate what I mean.plex secure bug.zip (2.3 MB)

Are there any real security implications for not using encryption? Since login is via plex.tv and encrypted anyway. It doesn’t really bother me if some random person knows what episode of The Office I’m watching.

Docker changes everything.

You’ll need the newly released PMS 1.13.5 which allows selection of network adapter to use

moving to the Docker forum

Does it? I still had the exact same issue when it was installed natively.

1.13.5 doesn’t appear to be in the public channel yet but I’ll post back when it is.

I ran into this problem on my network. Which uses 192.168.x.0. I put “192.168.x.0/255.255.255.0” in the LAN Networks field.

Change x in the above to the number your network is using.

It would help if the documentation clarified and showed examples of how the LAN Networks field should be populated.

This, however, did not solve the Indirect problem. I had to also set Secure Connections to Disabled.

@wkearney99 Where is the LAN Networks field? I couldn’t find it in PMS Settings > Network or anywhere else. It might be new to 1.13.5?

Use the [Show Advanced] button

Bear in mind disabled Secure Connections wrecks remote access.

I’m still on the hunt to solve this. I think it may also be a DNS rebind issue.

I have advanced settings shown. Can you tell me exactly where the setting is?

Funnily enough, my Android phone has no problems connecting remotely unencrypted as long as I match the encryption setting in the app to the server.

plex server -> settings -> network (showing advanced options) -> LAN Networks.

This using versions 1.13.5.5291 (windows) and 1.13.2.5154. (Qnap NAS).

I’m running 1.13.4.5271 (the latest public release without a plex pass) so I must be stupid or blind or something… any chance you could post up a screenshot?

I see custom certificate options, custom server URLs, an auth-less IP list and a few more things but no LAN Networks section or box. And CTRL+F for “lan” doesn’t turn anything up (except for Languages on the left).

scroll down, perhaps? it’s on the same page as custom certs.

Nope. Are you sure it’s on your Qnap and not just Windows? Here’s what the bottom of my Network page looks like.

I wouldn’t have posted if I hadn’t checked.

OH WAIT, you don’t have a plex pass? That might be the separating factor. I don’t have the (GO PREMIUM) button on my screens (as I have a lifetime plex pass). I seem to recall the docs mentioning various things require having a plex pass. Don’t know if this is one of them or not.

And I have to say, all this theater over “security” is a colossal clustef*ck of wasting my time.

Way too many layers of crap here, and no clear debugging tools or documentation on how to best debug it.

LAN Networks
Very few people will need to set or change this preference. It simply lets you specify which IP addresses or networks will be considered to be “local” to you. If you set any bandwidth limits under Remote Access, those do not apply to “local” playback and only take effect for remote playback. By default, only the network subnet on which the server is located is considered to be “local” (which is appropriate for the vast majority of users).
Tip!: This feature requires an active Plex Pass subscription for the Plex Media Server admin Plex account.

Well, that’s that then. There is absolutely no reason this setting needs a plex pass, as if it’s a premium feature. It’s little things like this (and the Android music transcoding bug which none of the devs seem to care about) which actually keep me from getting a plex pass in the first place.

I thought “screw it” and bought a Plex Pass for a month. I put 192.168.0.0/16 in the LAN Networks section. Still didn’t help. Cancelled subscription.

I also have “Treat WAN IP As LAN Bandwidth” ticked.

Any help?

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