My smart TVs have started to detect the plex server as remote and I have looked through the troubleshooting guide…
It looks like the my NAS is publishing both physical 192 interfaces and a 172 address as local addresses and it might be screwing up the smartTVs
Not sure if something has changes in recent Synology updates or Plex but the server has correctly detected as Nearby in the past.
FYI the 172 interface is the internal bridge interface for Docker not a direct LAN interface… I wonder if this can be intelligently excluded.
This question is in regard to the package install but I am also running docker on the Synology.
The ability to select which interface to use, when multiple exist, in a host such as Synology which as 4, plus those added by docker, is a long requested feature.
Engineering has not yet provided that feature despite multiple requests
On the plex side why not use the LAN Networks setting on the server then to filter out what gets advertised to the plex service?
I know the LAN Networks setting is intended for the server to know what is local, but if the user has to set it anyway it could be used for both.
I have been chasing resolution of this for some 18 months (minimum).
I’ve taken it on myself to write the code for it. It’s about 2/3 done. When I finish it, I’ll give the whole package to Engineering. It should be close enough to exact for a ‘drop in’ fit.
Open up network settings from the control panel on the Synology NAS and go to network interfaces, click the down arrow on the right side of each interface and find the one that has your local IP address of 192.168.x.x and click on edit. Make sure there is a check mark in the “Set as default gateway” after you make this change you may have to reboot all your device such as the troubled TV. It sounds to me like the interface that list the IP address of 172.16.x.x is set as the default gateway.
Hope this helps…
Nope, the first 192.168…x.x interface is already set as the default. The docker 172 interface does not even appear there.
The issue here is that plex is publishing ALL the interfaces and marking them as locally available to plex clients.
The smartTV clients don’t have as many options to test the paths and default to the external path if confused.
Chuck already answered and that setting has already been set. It doesn’t change the publishing behaviour.
