I’m seeing this error/warning in my server’s console (Settings -> Manage -> Console):
HTTP error requesting GET http://169.254.8.76:63445/upnp/xml/devices/MediaRenderer1.xml (0, No error) (Failed to connect to 169.254.8.76 port 63445: Network unreachable). A new entry is made approximately every 30 seconds.
From what I understand, 169.254.x.x addresses are used as a fallback when the host can’t get an address from a DHCP server. I have a router that gives out all requested addresses (I’m using 10.x.x.x), and I can connect to it just fine from the PC. But why would PMS even be asking for an address anyway, when my computer already has one?). I suppose it must be something else.
I’m confused. Can someone explain what’s going on here?
The short answer is that there is a device on your network at IP 169.254.8.76 which is responding to PMS’ SSDP broadcasts. These broadcasts are generally used to discover DLNA-capable players on the local network. Whatever is at that IP address is responding, so PMS is trying to query it for capabilities and such. If you’re not using DLNA on your network you can disable this functionality in Plex by unchecking the following in the PMS web UI:
Settings → DLNA → Enable the DLNA Server
You could also just ignore the error.
[Edited July 24th, 2020]
In case someone else stumbles across this post, and as it is being linked elsewhere, I’d like to clarify that the above is somewhat incorrect, or at least incomplete. While DNLA uses SSDP for device discovery, it is not the only Plex feature which does. So, disabling DLNA will not disable Plex’s use of SSDP discovery. It is used (at least) for a few other services, including network tuner support and creating automatic port forwarding using UPnP. Here’s a more recent post with some additional information:
And here’s a recently created feature suggestion for the ability to completely disable Plex’s use of SSDP:
After spending some time [dis]connecting network cables, I determined the device causing the issue was a DirecTV HR44/Genie. PMS console shows no errors when it’s not connected and the errors when it is connected. The HR44 reports the correct network addresses in its setup menu, so all I can think of is that this behavior is a leftover from when it used to support “Media Share”. Media Share was removed several years ago and there aren’t any configuration options for it any longer. I wonder if it’s advertising itself as a DLNA-capable device, but reporting the wrong IP address, and maybe PMS is seeing this broadcast and trying to do something with it.
But even after disabling “Enable the DLNA server” and “DLNA server timeline reporting” and then rebooting my PC (for good measure), I’m still seeing the same error in the PMS console when the HR44 is on my home network.
I’m stumped. At least it doesn’t seem to be causing any significant issues.
Yep, I just noticed the same behavior on my macOS-based PMS (PMS sending SSDP discovery packets). I thought PMS only did this for DLNA client discovery, perhaps I was wrong, sorry.
At any rate, you can safely ignore those log messages; the extra traffic these requests generate on your network should be negligible.
