Whatbox plex server getting several hundred discover packet errors

Server Version#: 1.14.0.5470
I have Plex running on a Whatbox VS and I am getting several errors a second for “NetworkServiceBrowser: Error sending out discover packet” DLNA and GDM are turned off in the GUI. I opened a ticket with Whatbox and there response was

“I believe it’s Plex that is still sending out SSDP packets, and it’s being blocked by our iptables rules. I"m afraid I don’t know of any way to prevent it entirely due to Plex being closed-source, so you may want to check on the Plex forums in case anyone has found a way.”

I am at a lost on how to resolve this. it makes it a pain to try and diagnose anything when the logs are filled with this error.

Nov 30, 2018 19:26:03.354 [0x7f255cbff700] Warning — NetworkServiceBrowser: Error sending out discover packet from 192.131.44.xxx to 239.255.255.250: Operation not permitted
Nov 30, 2018 19:26:13.354 [0x7f255cbff700] Warning — NetworkServiceBrowser: Error sending out discover packet from 192.131.44.xxx to 239.255.255.250: Operation not permitted
Nov 30, 2018 19:26:23.354 [0x7f255bbff700] Warning — NetworkServiceBrowser: Error sending out discover packet from 192.131.44.xxx to 239.255.255.250: Operation not permitted
Nov 30, 2018 19:26:33.354 [0x7f256a7ff700] Warning — NetworkServiceBrowser: Error sending out discover packet from 192.131.44.xxx to 239.255.255.250: Operation not permitted

Those are from PMS. PMS, in its normal home environment, is attempting to find the other players in your home ( Televisions and devices).

Since you have this in a datacenter, with locked down network visibility, unfortunately this is normal.
PMS will have a great deal of difficulty with that provider. Almost as much as Feral hosting and their namespaces

Is there a better service to go with that is Plex friendly or a way to turn off the player search in Plex?

Yes, that is how UPNP works, It sends out an HTTP like connection on port 1900 UDP via a multicast. That 239.255.255.250 is that multicast. If your firewall (I assume it is local iptabels) block that, then SSDP. This means your UPNP request cannot find the UPNP firewall.

They are also how DLNA works. I would get rid of DLNA if you do not need it.

I’ve heard, NOT VERIFIED because I have no need of it, Hetzner is a good one in Europe.

The above is correct, the multicast group is shutdown for you on that server.
They don’t want you discovering the other hosts on their LAN

Is there a way to disable this function in Plex? GDM and DLNA are already turned off.

You will need to go into Remote Access and manually specify the port. There will be much less but still some

With in Automatic mode, it searches.

What difficulty exactly would there be with that provider? Plex runs fine on remote servers. As long as DLNA and GDM are disabled, and I believe they are by default, there’s no issue.

The issues is IGD discovery. This requires SSDP unless the IGD search is disabled.

How then is IGD disabled? With manual port mapping? And if that is already being used, and IGD discovery is still running, then what?

Should be. What does you ifconfig and netstat look like?

Plex Media Server Version 1.14.1.5488

I have a similar error. I see a lot of errors parsing the igd.xml file, like this:
SSDP: Error parsing device schema for http://192.168.0.1:1900/igd.xml

The address belongs to my router:
TP-LINK N750 Wireless Dual Band Gigabit Router
Model No. TL-WDR4300

Is there a chance to stop this errors?

I’ve already set the remote access to a static port.

I’m asking because my NAS (QNAP TS-431X2) is using the HDDs when Plex is running all the time. Maybe the logging of the error is the reason?!

Tell TP-Link to fix their SSDP presence.

If the IGD file is properly formatted XML, there will be no parse errors.

(Many devices claim to be XML but aren’t correctly formatted)

Ok, thank you for the information. I think the igd.xml is not present at all… The request returns

500 Internal Server Error

That is my fundamental point.

If they are going to advertise as an IGD, they need comply with the SSDP specification.
If not, don’t advertise.

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