Local Devices can only access Plex Remotely

Server Version#: 1.32.5.7328
Player Version#:

When accessing plex on a laptop or Xbox they will connect on a secure remote connection rather than a local connection and if i turn off remote access I lose access on all devices. I recently built a new Truenas scale server with a Ryzen 5 3600, 32gib of ram and a gtx 670 with two 2 terabytes HDD’s . After the build plex movies take forever to load and struggle to play the most basic videos, I’m assuming it has something to do with remote connection to local devices.

Guidance would be great!

Sounds like your new NAS is on a different subnet or some other configuration is blocking the clients to see the server locally (e.g. some firewall or other network restrictions).

I don’t know if its a different subnet, to my knowledge all my devices are on the same subnet as my router between 192.160.1.1 - 192.168.1.254, I did look at the network restrictions and there is none set by default, and I haven’t messed with that. As for a firewall issue I haven’t looked, my last Nas which uses the same ip (192.168.1.148) seemed to have no issue. I have a cheap 2.5gbe ethernet card in my new system could this be affecting the connection status?

Another possible reason might be “DNS rebinding protection”.
https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/

Reading over that link it noted that some default DNS’s have built in DNS rebinding protection so i changed it to 1.1.1.1 & 8.8.8.8 but plex still only allows indirect connections. I’m using a Netgear Nighthawk RAX50 Router and i don’t believe there is any DNS rebinding protection built in. Similarly my pi-hole application running on the same system ran into a “dnsmasq” error and would not run. This is mentioned in the support page from plex but i have absolutely no clue what “dnsmasq” is…

Pi-hole has for certain DNS rebinding protection built in.
dnsmasq is the open source DNS server that is part of Pi-hole.

So the instructions from the article can be used directly in Pi-hole

Pi-hole aside, when only using DNS’s 1.1.1.1 & 8.8.8.8 hopefully negating the Rebinding protection plex still thinks it has a remote connection to devices on my local network, the only way to have a local connection is opening the web portal from TrueNAS itself. I’m still assuming it’s definitely a network problem as running TrueNAS on my old office computer before upgrading to a build system it had no issues. I’m quite new to all of this and only got this far because of tutorials online so when there is no definite solution, I’m lost in the world of software hahaha. is there anyway I can share the logs so people can look at them without my terrible explanations?

There is no “pihole aside”, pihole is the cause of this issue.

On your pihole server

in the /etc/dnsmasq.d directory

create a file called 99-pihole-custom.conf

and add the below to the contents of the file.

rebind-domain-ok=/plex.direct/

then restart the pihole service.

But I Stopped the pi-hole service completely thinking it was causing the issue and I’m still experiencing remote connections for local devices.

then whatever is now doing your DNS (likely your router) has rebinding protection on and you need to disable it there.

also, make you the NAT setting on your router is correct (netgear call the settings stupid things) make sure its “open” and not “strict”. it might also be called something like NAT loopback, which needs to be enabled.

I’ve just set the NAT type to open as it was on secure. It seems this has had no visible effect the plex applications are still saying remote secure connection. Doing some more research I’ve come across an article DNS Rebinding & Permitting a private domain - NETGEAR Communities. The user is also using a NETGEAR router and they claim there is no user control over DNS Rebinding Protection. and if that’s the case…This sucks! would it be worth trying the original router/modem from the ISP? I would be sacrificing a lot of speed and customisability.

Just bring the pi-hole back into play and let it be the DNS server for your private network.
Because this one can be configured as needed.

your ISP router/modem will offer even less controls than the netgear - put pihole back in the mix and it’ll give you the needed control.

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