Server Version#: Version 1.19.5.3006
Player Version#: Web Version 4.36.1
I was going to reply to this thread created by @Mike-G (hey, nice name! ), but it’s locked and closed, so I am forced to start a new one.
I am getting this same repeated error, and also wonder why it still is being produced despite being turned off in settings. I understand the logging is “negligible” as referenced in the thread, but you get a few “negligible” repeating log events and they start to add up.
The other possibly more pressing issue here is that if it is accurate that “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” and we have turned off this feature, this becomes a possible security concern/vector for someone to exploit in some way.
DirecTV uses Link Local to communicate with it’s own devices. This is generally why they don’t want you to plug the ethernet in without using their Cinema connection kit.
If you had a smart switch you could filter the 169.x.x.x.
OK cool… I am still confused on who is causing the messages in the logs. Is it DirecTV or is it Plex? Or both? Looks like Plex is sending out SSDP pings despite the DNLP feature being turned off?
Unfortunately, I do not have a smart switch and even if I did I would prefer to make my network less chatty if I could help it. Any unwanted/unexpected communication is a security concern/vector at the very least, after all, which is my fundamental concern here. Secondary is the logs being filled with this traffic.
Correct @trumpy81, thank you for your reply. The issue here is that I have disabled this feature in settings as mentioned above in this thread and it still occurs.
I guess we have a difference of view on what you mean by frequency, as these are occurring quite often in my console as denoted above, and I would rather not be punched in the face with a bunch of warnings/errors when I view the logs, harmless or not.
Regardless, since this seems to be occurring when I disable it in settings, this seems to be a bug.
But why? I do not want to cast to any TV Tuners or any other devices, especially DirecTV as this seems to be the devices causing the issue. All other connections are via Roku and Web players which works the reverse direction, that is, device → server (preferred), not server → device which is what I am trying to avoid here.
In addition to unnecessary/unwanted traffic and functionality, there is also the security consideration of broadcasting so much information across the network as well. You’re basically broadcasting a beacon on your network saying “LOOK AT ME I MIGHT HAVE A VULNERABILITY YOU CAN EXPLOIT.”
Haha, maybe impact was the word I was looking for.
Fine. You win. I guess there are bigger problems in life.
It would be nice to see Plex eventually cut down on the chatter and make this an option to toggle off in the settings.
FWIW I did take another look, and it seems my impression with the screenshot above was a bad one. I was thinking it was occurring every minute as you suggested. However, a careful screening of some logs shows that it happens much less often than that, like every hour or so.
In any case, thank you for taking the time to share some knowledge and insight, @trumpy81.
), but it’s locked and closed, so I am forced to start a new one. 
