Even weirder, if I connect via plex.tv or direct via the machine’s local hostname, I get a Remote connection… however if I connect via its local IP address I get a Nearby connection.
I have tried restarting, signing out and into the server (in general settings), disabling and reenabling remote access, and entering my public domain address (which points to my external IP) in Custom server access URLs.
I have Ethernet(192.168.20.112) selected as my preferred network adapter (which is the only one), but even though it apparently is aware of that adapter’s address, it does not seem to realise that this should be the private IP.
Ok, so resources.xml lists the server, with the correct external IP, and two connection entries:
A local connection containing the server’s local IP address, port 32400 and a plex.direct uri.
A remote connection containing my exteral domain address and port 443 (which goes through a reverse proxy).
So, that all looks correct.
Why then am I not getting nearby connections on anything but the local IP address (including even the local dns hostname - which resolves to the same IP)?
I should also mention that in addition to the reverse proxy on 443, I also have my WAN address forwarded on port 32400 to the plex server, so either port will work when connecting externally to my WAN IP (either direct or proxied).
Does the issue arise if you do not use the Custom Server Access URLs field?
and does the problem resolve itself after disabling and re-enabling remote access
If the problem persists would like to see the xml responses after a fresh disable / re-enable remote together with https://plex.tv/pms/resources.xml?includeHttps=1&includeRelay=1&X-Plex-Token=xxxxxxxxxxx and server logs with debug logging enabled beforehand and time when the IP addresses showed as Unknown