Plex server keeps polling 169.254.100.156:37215

Server Version#: 1.18.4.2171
Player Version#: 4.12.3

Hi in my server console i keep seeing this error (repeats every 30 seconds);

SSDP: Error parsing device schema for http://169.254.100.156:37215/upnpdev.xml

My server is in the 192.168.0.x/24 subnet (255.255.255.0) so it should not be able to find anything with a private 169.x ip address.

To the best of my knowledge i have nothing in 169.x - even if i had, the plex server should not fin it.

i do have ipv6 enabled, but I would assume that if plex found some device on ipv6, then the device schema parsing request woud be on the ipv6 address, not on some private ipv4 address.

How do i determine where this is comming from ?

Br,

Henrik

It could be that one of your devices has an additional IP in the APIPA range and is responding on there.
Nothing to be concerned of. You can safely ignore these lines.

Hi Otto,

I’m not greatly concerned. but a little confused.

Even if i had a device with multiple IP’s, then i should not see the 169.x address from plex.

So My question is - is plex storing a “device list” somwhere (that i can look at and edit) or is it constantly running some sort of network discovery (that i can replicate to find the offending device)?

Either way i’d like to remove the offending device from device list or from discovery.

Lets just say i like things nice and tidy in my network :slight_smile:

Br,

Henrik

There is nothing you could edit or filter to get rid of those lines.

For the interrest of other readers:

I tried gssdp-discover -i on the linux server. and it found a surprising number of my lan routers are upnp devices, that return a private ip address for the wps_device.xml address. (even when queried and located on the 192.168.0.0/24 subnet)

as most of the lan devices are to be replaced soon, i’ll look more into the upnp offering on the new devices and whether or not to enable the feature in those before installing them.

Br,

Henrik

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.