Did you ever run the Plex server as a system service?
(this doesn’t mean that you should try it now)
You can kill everything Plex related from HKEY_USERS.DEFAULT However, you might have to run the PMS installer executable afterwards.
(and it might not let you delete from there, as long as the “Plex Updater” service is still running)
How long ago is the change of network addresses?
I remember that I tried, but refused a long time ago, so it was running not as a service for a few years
Deleted with no issues
Around 2 weeks ago
Repeated the whole process, with re-login step before claiming the server, including re-login on a client, but nothing changed - DNS request is still looking for an old IP.
Could there be any place on a client, where old IP is stored?
All clients have a cache, but that should be flushed when logging out and back in.
Strange, but now there is a request from a server, not a client, with an old PMS IP
Before it definitely was a client request
And PMS env operates with new IP and DNS in place
Sorry, I am unable to comment on that as I don’t know your local network.
The only remaining idea I have is to fully remove the server from your account.
But this would require all clients to be reset https://app.plex.tv/desktop/#!/settings/devices/pms
(and the shared user you have to also be granted access to the new server ID.)
After deleting the server from the above link, you need to perform the procedure Why am I locked out of Server Settings and how do I get in? | Plex Support again.
Removed the server, cleaned the registry, and re-claimed the server, but nothing changed - neither server nor client tried to send a DNS request with new PMS IP
btw, all clients (desktop and mobile) were picked up without resetting and I still can’t see PlexOnlineHome key in the registry, 3 others are propagated
Regarding the network - win 10 PC is the only client in the whole network, having problems. android phone, 2 Shields, Plex web are okay
Android phone stream is going directly to the client, but PC is routed through a UDM since it can connect only remotely
Which client are you using on the PC?
The web app or something else? It might be interesting to try several.
Does the plex web app behave the same? https://app.plex.tv
If the web app behaves as expected, close Plex for Windows, and empty out its configuration folder.
C:\Users\Peter\AppData\Local\Plex (NOT Plex Media Server)
Official Plex for Windows
Exactly the same - both are routed through the router
I suspect, that for app.plex.tv it’s expected behavior, but the Windows client previously was capable of direct connection
Closed Plex for Windows, cleared the folder, flushed DNS on both computers, restarted the PMS, and nothing changed - still remote with traffic going through the router.
Also, noticed another strange DNS request from the PMS (check the token)
Wait a minute. “Local” and “Direct Play” are perfect results.
There is nothing wrong about this.
Left to right: mobile on cellular → app.plex.tv from PC in local network → Plex for Windows from PC in local network
Agree, that local and direct play is not wrong, but shouldn’t Plex for Windows display not ‘remote’?
I suspect that this is still cached data. As long as the Dashboard shows “local”, everything is alright.
That’s perfectly normal. This request is used by the server to determine whether DNS rebinding protection is active in this network.
Seems that there is something still wrong with the windows app - I’ve cleared the cache multiple times in the last hour, but it’s still displaying PMS as ‘remote’ and there is 5-6sec delay before any music track starts playing and it happens only in windows client - plexamp, plex android are totally okay, no delay
See above.
This could also be caused by its ability to HDMI bitstream and/or a configured “Refresh Rate Switching Delay”.
i.e it doesn’t have to be caused by an indirect connection,
Since this is only happening with one client I would check the hosts file.
C:\Windows\System32\drivers\etc\hosts
done already, only a few docker entries
So back to the Pi-hole, did you clear out all the old leases for that MAC address? That is also where you add plex.direct private domain.
Also, try browsing to this domain on the client PC (or the server, or both):
https://plex.tv/api/resources?includeIPv6=1&X-Plex-Token=[your token]
There’s some help in this support article for finding out what your authentication token is:
In the resulting page, there should be XML entries showing resource information for each of your open/logged in servers and clients. The product type is noted, so they should be easy to distinguish.
Look for entries which don’t show your current IP numbering, particularly for the server.
Regarding the Pi-Hole, are you running a local recursive DNS server on it, such as Unbound? If so, it’s in that DNS server’s configuration where you’ll likely need to carve out the exception for *plex.direct. For instance, in my own Unbound configuration (running on a Pi-Hole), I have the following configuration directive:
private-domain: "plex.direct"
