Server Version#: 1.41.8.9834 (on Windows 10 PC)
Player Version#: web & android-mobile (2025.16.0)
Remote Access is “Fully accessible outside [my] network,” but accessing my server remotely gives warnings about “Indirect Connection” and my media streams at very low quality with very long loading times.
I have reserved the server’s IP in my router (xFi gateway)
I have manually forwarded the port (tested via canyouseeme.org)
I am not in a double-NAT nor a CGNAT situation (tested via whatismyip.org)
Don’t do that. It is unnecessary and potentially dangerous.
Plex will create the necessary exemptions in the Windows firewall for itself when it is installed.
All you need to make sure of is that the network connection in Windows is tagged as “private”, not “public”.
Your server is apparently published successfully and is available remotely.
In order to access it from the outside, the clients use the domain name that was assigned to your server automatically. In order to use the domain name, the client needs to be able to resolve the domain to the actual IP address. That is done with the help of a DNS server. If you are using a network (when away from home) that is using a filtered DNS server, it can happen that subdomains on *.plex.direct either don’t get resolved at all, or the results are stale and thus lead to the wrong IP.
The solution is to set a custom DNS server in the device with the Plex client. Google’s 8.8.8.8 or CLoudflare’s 1.1.1.1 are known-working alternatives.