Server Version: 1.24.3.5033 (Container)
Player Version: 4.66.1
Chrome Version: 94.0.4606.61
Hello 
Long time Plex user seeing some weird behaviour out of the blue.
If I stream from the Android App, Plex correctly connects over the local network to the server via the 192 range:
Request: [192.168.68.120:50082 (WAN)] GET /:/websockets/notifications (12 live) TLS GZIP Signed-in Token (masterjonny)
The same happens when I stream from my Google TV:
Request: [192.168.68.124:37846 (WAN)] GET /:/websockets/notifications (3 live) TLS GZIP Signed-in Token (masterjonny)
However if I stream from Chrome (on both Windows and Mac), the app.plex.tv web app never detects the server as nearby, and always routes the connection out via the internet and back in again:
Request: [149.x.x.x:58690 (WAN)] GET /activities (11 live) TLS GZIP Signed-in Token (masterjonny)
This obviously messes with the quality settings and playback. I can work around this by accessing my server directly at 192.168.68.112:32400, and not using app.plex.tv, but I’ve not needed to do this in the past - app.plex.tv has always correctly detected my server as nearby when on the same network.
I can confirm DNS rebinding is working fine on the network:
% dig 192-168-68-112.mytoken.plex.direct +short
192.168.68.112
% curl 192-168-68-112.mytoken.plex.direct:32400
<html><head><script>window.location = window.location.href.match ...
As my server runs in a container, I have LAN Networks set to 192.168.68.0/24,172.16.0.0/16
This has only started recently, and the Plex stack has been working happily for years now, so I don’t think anything’s misconfigured.
