Server Version#: 1.41.5.9522
Player Version#: multiple
I would like to clear connection URIs under https://plex.tv/pms/resources.xml except for the current one, which is custom.
What’s the way?
Mmmh, I thought this is a simple one. But now 7 days passed.
Maybe too simple? Have I used the wrong search terms, for I couldn’t find an answer?
Are you referencing your servers or those shared with you?
(Sorry, I wasn’t notified. Sometimes the forum doesn’t notify me of new posts)
Nevermind, I’m glad I got in contact 
I reference my server, which publishes URI’s, which I use to access my server from the Internet while away from home.
Edit: I don’t use Plex’s Remote Access, instead go through my reverse proxy and hence use a custom URL under Network settings and a manually defined port under Remote Access settings.
What connections do you see published for your server here?
https://plex.tv/api/resources?includeIPv6=1&includeHttps=1&X-Plex-Token=<your_token>
You can find your Plex token using the information in this document:
https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
Is your old custom URL still published? If not, then it’s likely the clients still have it cached for some reason.
I do see old and obsolete connections, of course. That’s why I said: “…except for the current one,”
I see connections with my docker container address in it, with my current custom URI (which is the only desired one) and one with my public IP address, some labeled local, one not.
How can a cached address on a client influence information that my server publishes? If this is true it seems not correct.
This is the only one I wish to keep:
<Connection protocol="https" address="<My Custom URL" port="443" uri="https://<My Custom URL>:443" local="0"/>
Here are some of the others I wish to delete/clear:
Current local (internal LAN) IP address:
<Connection protocol="https" address="<Current Local IP Adress>" port="32400" uri="https://<Current Local IP Adress>.<ID redacted>.plex.direct:32400" local="1"/>
Old docker container IP address:
<Connection protocol="https" address="172.10.0.1" port="32400" uri="https://172-10-0-1.<ID redacted>.plex.direct:32400" local="0"/>
Old docker container IP address:
<Connection protocol="https" address="172.17.0.1" port="32400" uri="https://172-17-0-1.<ID redacted>.plex.direct:32400" local="1"/>
Current public (Internet facing) IP address of my ISP connection:
<Connection protocol="https" address="<My Public IP>" port="443" uri="https://<My Public IP>.<ID redacted>.plex.direct:443" local="0"/>
A current local IP address is always going to be published, it cannot be removed. You can influence which is published, if you have multiple, by selecting the preferred network interface in Settings → Network → Preferred network interface. (Pick a specific interface and not “Any.”)
The current public IP address of your ISP connection can be removed by disabling remote access in Settings → Remote Access. It is not needed when using custom server access URLs. (If the custom URL is indeed working.)
As for your Docker container IP addresses, I’m not sure why those would still be published. Unless maybe you configured the container with ADVERTISE_IP set to that value and it’s still using that for some reason.
Yeah, I didn’t really state that clearly. I jumped trains of thought there (that perhaps clients were still trying to connect to the old published connections). Feel free to ignore that part.
Note that my first statement is a bit of a lie. If you don’t have a local interface with a default gateway configured, it won’t be used. But that would break other functionality, so would not be practical.
Thank you for the detailed explanation.
I disabled Remote Access and the public IP is gone. Good.
OK, the local LAN IP will stay there - that’s not a problem for its 192.168.x.y.
The Custom URL is still published - also good.
I don’t have any IP advertised through docker config. Plex is configured with network_mode: host.
The IP addresses I see with Plex are of the docker bridge interfaces of docker-wide configured docker networks and one of podman…
OK, it seems that everything is as you explained and everything is coming from the server, not from caching clients. Changing things on the PMS does change things on plex.tv for that server. Again: good.
If I change the network mode for the Plex container in docker, will it help? I think the only port I have to publish in docker is 32400, for I don’t use GDM, DLNA, AVAHI/Bonjour or Roku. At home I use a Nvidia Shield as client, on the internet my phone or laptop.
If you want to share your server logs (Debug enabled, Verbose disabled) they might show a little more information about why those addresses are being published. If you do, please restart the container and then wait about a minute before collecting them to allow things to settle. You can PM them to me if you’d like.
I don’t know that changing the network mode for the container will affect this (it might though). But if you’re currently using host mode, that’s where I’d leave it. In host mode you shouldn’t need to manually publish any ports.
Those addresses get published for they are all addresses of the docker host. On the host ip a shows them and they stem from created docker networks.
Running the Plex container with network mode: host makes them discoverable by the container. This way Plex can see them as possible IP addresses of it’s own container, for network mode : host on a container means: every host address is useable by the container / is seen as an interface address of the container.
Changing the container config for Plex to docker bridge mode and publishing ports is an easy job and I can go back to host mode in seconds in case of problems. So I tried it and it’s working.
But I don’t want Plex behind an (not so performant) docker bridge and so I tried the IPvlan driver of docker with success:
Now Plex is running with it’s own local IP directly on an interface of the docker host (without using docker bridge), the only published network port is 32400 and looking at plex.tv reveals only the private class c address as well as my custom URL. Wish come true 
Thank you for your input, @pshanew .
No problem, glad you got it working.
So I am running into something similar post and I checked the URL and the custom URL is not in the plublished server url’s.
However I do see it in my dns logs. So I guess this means my client has it cached? If so how do I go about clearing this from my client? I tried signing out and signing in and that did not help. Tried this via browser and mobile apps.
Have you tried in an incognito/private browser window? That should eliminate the possibility of client caching as far as the browser is concerned. For mobile, if it’s Android, you can force a cache clear in the same place you force stop the application.
However, given that multiple clients are showing this, are you sure the old custom URL isn’t being published?
Looking at your Plex.tv account,
You do have a FQDN listed under local addresses.
(Something you did publish)
The domain (redacted) plex.t*******p.*********ty
I can do a dns lookup of the name and it does match your WAN IP address.
@pshanew I checked URL https://plex.tv/api/resources?includeIPv6=1&includeHttps=1&X-Plex-Token= and it only mentions the domain that @ChuckPa mentioned in the comment.
That is the correct domain.
However in pihole I can see queries also being made for
2025-03-27 17:16:09 A plex.t****d.duckdns.org
2025-03-27 17:15:09 HTTPS _11443._https.plex.t****d.duckdns.org
2025-03-27 17:15:09 A plex.t****d.duckdns.org
2025-03-27 17:14:36 HTTPS _32400._https.plex.t****d.duckdns.org
2025-03-27 17:14:36 A plex.t****d.duckdns.org
2025-03-27 17:14:36 A plex.t****d.duckdns.org
2025-03-27 17:13:36 HTTPS _32400._https.plex.t****d.duckdns.org
2025-03-27 17:13:36 A plex.t****d.duckdns.org
2025-03-27 17:13:09 HTTPS _11443._https.plex.t****d.duckdns.org
2025-03-27 17:13:09 A plex.t****d.duckdns.org
When i search plex media server logs for this domain I see the following messages
Library/Application Support/Plex Media Server/Logs/Plex Media Server.log
25:Mar 27, 2025 13:33:00.455 [140187451640632] WARN - [HttpClient/HCl#43] HTTP error requesting GET https://plex.t****d.duckdns.org:32400 (7, Couldn't connect to server) (Failed to connect to plex.t****d.duckdns.org port 32400 after 1972 ms: Couldn't connect to server)
Library/Application Support/Plex Media Server/Logs/Plex Media Server.2.log
1106:Mar 26, 2025 15:44:47.581 [140536199822136] ERROR - [EventSourceClient/mediaserver/plex.t****d.duckdns.org:11443] Retrying in 15 seconds.
1107:Mar 26, 2025 15:45:03.415 [140536199822136] ERROR - [EventSourceClient/mediaserver/plex.t****d.duckdns.org:11443] Retrying in 30 seconds.
1108:Mar 26, 2025 15:45:33.749 [140536197712696] ERROR - [EventSourceClient/mediaserver/plex.t****d.duckdns.org:11443] Retrying in 60 seconds.
1109:Mar 26, 2025 15:46:33.797 [140536199822136] ERROR - [EventSourceClient/mediaserver/plex.t****d.duckdns.org:11443] Retrying in 120 seconds.
1127:Mar 26, 2025 18:49:20.077 [140536199822136] ERROR - [EventSourceClient/mediaserver/plex.t****d.duckdns.org:11443] Retrying in 15 seconds.
Library/Application Support/Plex Media Server/Logs/Plex Media Server.1.log
28:Mar 27, 2025 07:00:29.476 [140006151555896] WARN - [HttpClient/HCl#43] HTTP error requesting GET https://plex.t****d.duckdns.org:32400 (7, Couldn't connect to server) (Failed to connect to plex.t****d.duckdns.org port 32400 after 2260 ms: Couldn't connect to server)
Library/Application Support/Plex Media Server/Logs/Plex Media Server.4.log
344:Mar 24, 2025 05:24:33.716 [140152788175672] WARN - [HttpClient/HCl#295] HTTP error requesting GET https://plex.t****d.duckdns.org:11443/media/providers?includePreferences=1 (6, Couldn't resolve host name) (Could not resolve host: plex.t****d.duckdns.org)
376:Mar 24, 2025 06:18:12.364 [140152813693752] ERROR - [EventSourceClient/mediaserver/plex.t****d.duckdns.org:11443] Retrying in 15 seconds.
I am running the LSIO plex image with updates set to public.
edit:
Also a few months back I moved my docker install to a different machine so my server name changed. I was informed in other forums that this might be related to the issue I am seeing. However the change where i switched to a different domain happened at least a few months before I moved machines.
I missed this before, but I see the offending domain published under another device which is my friends plex server.
I guess that’s why my plex server is trying to reach it. I will check with them to see if they picked up my previous domain lol.
Ah, that makes much more sense.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
