That list doesn’t currently appear to be up-to-date. There was another thread opened about it recently which is apparently still under investigation. You may want to check over there to see if there’s an update.
Yes. My suggestion here would be to disable remote access entirely and set up remote access URL(s). (Settings → [Server Name] → Network → Custom server access URLs.)
You can still use secure connections and do not necessarily need to set up your own custom domain. You can piggy-back off of Plex’s secure remote access functionality (they automatically create a TLS certificate for your server).
The URL you specify will be in the form:
- The HTTPS URL scheme (https://).
- The public address of your server with the octets separated by dashes instead of periods.
- Your server’s unique certificate UUID. This can be found in your Plex installation’s
Preferences.xmlfile and is namedCertificateUUID. - The domain
plex.direct. - The port number you are (selectively) forwarding in your router’s configuration.
So, for example, if your public IP address is 93.184.216.34, your certificate UUID is abcdefedcbabcdef1234567890, and your external port to be forwarded is 50000, your custom server access URL would be:
https://93-184-216-34.abcdefedcbabcdef1234567890.plex.direct:50000
You can then configure your router to only allow the IP addresses you desire to allow as clients; Plex doesn’t perform connectivity checks for custom server access URLs. This URL will published to Plex’s server (and offered to clients) as a non-local access URL for your server.
