Issues with local server access from Plex App

Server Version#: 1.43.0.10492
Player Version#: (Android and iOS Client Versions 2026.4.0)
Server OS: Truenas Scale

Hey everyone.

I am having issues with accessing my local server from both android phones and iPad. All devices appear to be up to date, as is the server app version.

My setup is the Plex server app installed on a truenas server via the applications installable from within truenas (docker under the hood). The devices being used are on the same subnet as the server, and the devices can be pinged from the shell of the truenas server.

It seems that I have had this issue for a long time, and that I have been skating by with remote access from these devices, but this has randomly stopped working in the last week or so (could be related to this post as I have a similar baseline of being in the UK and I have a CGNAT, but I haven’t seen the similar log entries yet so may be unrelated - Plex Relay is Broken ).

As such, my devices aren’t falling back to the remote access so are unable to see the server at all.

I am able to hit the server via a browser from the devices using the route of http://local-ip:32400/web and the server config exists so that local connections are allowed without auth. I have also been able to successfully connect to the server from a browser using the https://{IP}{UniqueID}.plex.direct address.

Things I have tried:

  • Set the config for the Truenas/docker app to use the host network
  • Confirmed that the devices are on the same subnet as the server
  • Confirmed the devices can connect to the server using the ip address
  • Set the server config for Secure connections to “preferred”
  • GDM enabled
  • Confirmed router isn’t using an ISP specific dns in case of issues with DNS Rebinding.

The only device I am able to use successfully is an LG TV where the app still allows for a local server IP address to be configured within the app.

I have taken a look at https://plex.tv/api/resources?includeIPv6=1&includeHttps=1&includeRelay=1&X-Plex-Token=xyz and can see quite a few entries for connection protocol where the flag local=1 including one that has the servers local IP as the IP, and the above https plex.direct address as the uri. The other entries here that have local=1 are a mix of IPv4 addresses starting 172.16.x.x (whereas my local IPs are all 192.168.x.x) along with a few IPv6 addresses.

I guess my main questions are:

  1. Is there anything I have overlooked as a point to troubleshoot based on the above?
  2. Should I have so many entries under /api/resource that are flagged as “local” where the IP address are not the same as my local IP range?

Thank you for getting this far and for any help you are able to give.

Hey everyone.

Thankfully, I was able to address this issue - although I’m not yet 100% sure what action finally did it.

It does seem that one of things I needed to do was to set the Preferred network interface to that of the actual local network as opposed to “any”. Doing so and then a reboot meant that the list of connections shown when accessing https://plex.tv/api/resources was reduced massively. Turns out that Docker uses the 172.16.x range for IP addresses which is why I was seeing loads of entries within this range.

I should probably also look into why the relay isn’t working for me, but it’s Sunday.