BTW, I did test things. With remote access DISABLED and my port forwarded manually, custom SSL certificate enabled and custom domain filled it, things still do NOT work from outside of the network
I looked at the generated XML and the *.plex.direct utilized ends up being the internal private IP address (192.168.0.3 for me) which is obviously not routeable outside.
So it would seem Volts is correct. One of the functions of having remote access enabled is indeed to detect the public Internet IP address.
This begs another question now though of why the Android app is attempting to use the 192.168.0.3 address when it’s not reachable. My custom domain was definitely listed in the XML and I can obviously connect properly to the server.
Seems like some sort of BUG to me.
This appears to be at odds with the findings from your solution though. I’m going to double check my tests again.
I think an easy fix from the server side is to have option under network settings to just completely disable the*.Plex.Direct function, for those of us who know what we’re doing with port forwarding and custom domains and certs.
