I recently installed a Starlink conneciton on my home network in addition to my VDSL broadband with static IP.
Plex no longer works outside my home.
I realise that Starlink / CGNAT will not work. I have set-up policy based routeing for port 32400 via the static IP and also added a custom URL for external access (with valid LetsEncrypt cert). I have also tried UPNP out the DSL and not fixing the port number, but same.
I can’t route the outbound query to http://plex.tv/pms/:/ip via the DSL line, and as the Starlink is the preferred route for traffic because of the higher bandwidth it all goes that way.
The logs, happy to share but they are full of my custom domain and static IP and given the recent issues I don’t feel comfortable with that out there, show a mix of custom URL being registed and dou=ble-NAT being found too.
You will need to setup your own Customer Server Access URL.
This URL , when opened, provides the unambiguous path you want Plex clients to use.
It’s most commonly implemented by:
Minimally - a DDNS which you maintain (typically via automation updating from any host on your LAN)
Optional - you can add your own domain & certificate (some prefer their custom , full, domain name over a DDNS name)
In Settings - Network - Show Advanced, you will specify that DDNS/Domain name access URL. PMS/Plex.tv will handle adding the port number (your Remote Access port) so you don’t need it. Just the base Domain/DDNS name
When PMS next publishes (Remote Access OFF - ON or Restart), your Custom URL will be sent to Plex.tv for clients to use when contacting your server.
I have done this. I have tried both with and without port number as per the article I linked. The custom URL appears in the log but it still insists on registering the IP found via the discovery endpoint.
Edit: on mobile, will slightly opaque log and attach shortly.
Disable remote access; it is not needed when specifying a custom server access URL (and can actually cause harm as your non-custom address will still be published).
Instead of specifying your custom domain, place your IP address in the URL in the custom server access URL field. Something like: https://ip.address.of.server:port
The port is only needed if you’ve forwarded something other than the default of 32400.
Plex will generally do the right thing with this. And again, this is just a test.
You can also see exactly what is being published to Plex by accessing this URL: https://plex.tv/api/resources?includeIPv6=1&includeHttps=1&X-Plex-Token=your-plex-token
You can find your Plex online token using the information in this support article.
Once you’ve established that you can get the correct IP published via the custom server access URL and that the server can be accessed that way (via app.plex.tv), you can add the additional complexity of the custom domain with certificate.
[Edit]
As an addendum, the above won’t work if the IP address you specify in the URL is the same as that which Plex detects as your public IP address. For example, if Plex detects your public IP address as 192.0.2.100 and that is what you specify in the custom server access URL (say, https://192.0.2.100:32400), it will not be published. It doesn’t sound like that will be the case here since Plex detects your Starlink IP address, but I’m including it for completeness.
Ah! That worked. It’s not clear from the docs that the two are independent settings.
I have now set the custom URL and disabled remote access and it works. This is a combination I didn’t even consider trying.
@ChuckPa thanks also for your suggestions - perhaps the article https://support.plex.tv/articles/200430283-network/ could be updated to be more explicit, and also the mention of the port from the remote access page will confuse, as that’s only visible when remote access is enabled?
