My server sits behind a reverse proxy, and because of that the Remote Access page
shows a permanent red error for something that actually works fine. I would like
an option to tell Plex “I use a different route, please stop checking”.
SETUP
- Plex Media Server 1.43.4.10903 in Docker on TrueNAS
- Container uses a bridge network, so the server’s own address is 172.17.x.x
- Remote access goes through a reverse proxy (Caddy) on port 443
- Published to Plex as a Custom Connection URL: https://plex.example.com:443
- Clients: Plex for Mac, iOS
WHAT HAPPENS
Remote Access always reports “Not available outside your network” and shows:
Private 172.17.x.x : 32400 -> Public <wan ip> : 32400 X
As far as I can tell, the server reports its container address (172.17.x.x) to
plex.tv, and the reachability check is then run against
172-17-x-x.<hash>.plex.direct
That is an RFC1918 address, so it cannot be reachable from the outside by
definition. The check is not detecting a real failure — it is testing an address
that does not exist outside the container.
WHY THIS IS A PROBLEM
Remote access works perfectly. Verified from an external host:
curl https://plex.example.com/identity -> HTTP 200, TLS verify OK
Clients get the Custom Connection URL from plex.tv and use it without any issue,
from LAN and from mobile networks alike.
But there is no way to acknowledge this, so the settings page shows a red error
icon permanently. That makes the indicator useless: if it is always red, it can
no longer tell me when something is genuinely broken. I would never notice a real
remote access failure, because it looks exactly like today.
WHAT I WOULD LIKE
An option such as:
[ ] I use a custom connection / reverse proxy — skip the remote reachability check
Alternatives that would work just as well for me:
- If at least one Custom Connection URL is configured and reachable, treat remote
access as OK. - Or report the two things separately: “direct port: unavailable” and
“custom connection: OK”, instead of one combined red error.
I doubt I am the only one running Plex behind a reverse proxy in a container, so
this probably affects a fair number of setups.
