Plex upnp is bombarding minidlna with requests!

Plex Media Server Desktops & Laptops
1

I installed minidlna dlna server, because plex can’t play some video files on my tv directly with subtitles…
I turned plex dlna off… in minidlna logs i can see that plex is constantly sending requests to minidlna, 6 times in one second, and it’s doing constantly… is this upnp, and how to disable it? i tried setting manually external port… but i don’'t whant to open ports in router… i watch my media at home only… please help…

[2018/04/27 20:56:26] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:34719 ST: ssdp:all, MX: 5, MAN: “ssdp:discover”
[2018/04/27 20:56:26] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: uuid:4d696e69-444c-164e-9d41-b827eb664f1d
[2018/04/27 20:56:26] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: upnp:rootdevice
[2018/04/27 20:56:26] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:device:MediaServer:
[2018/04/27 20:56:26] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ContentDirectory:
[2018/04/27 20:56:26] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ConnectionManager:
[2018/04/27 20:56:26] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:
[2018/04/27 20:56:36] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:34719 ST: ssdp:all, MX: 5, MAN: “ssdp:discover”
[2018/04/27 20:56:36] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: uuid:4d696e69-444c-164e-9d41-b827eb664f1d
[2018/04/27 20:56:36] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: upnp:rootdevice
[2018/04/27 20:56:36] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:device:MediaServer:
[2018/04/27 20:56:36] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ContentDirectory:
[2018/04/27 20:56:36] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ConnectionManager:
[2018/04/27 20:56:36] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:
[2018/04/27 20:56:46] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:34719 ST: ssdp:all, MX: 5, MAN: “ssdp:discover”
[2018/04/27 20:56:46] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: uuid:4d696e69-444c-164e-9d41-b827eb664f1d
[2018/04/27 20:56:46] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: upnp:rootdevice
[2018/04/27 20:56:46] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:device:MediaServer:
[2018/04/27 20:56:46] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ContentDirectory:
[2018/04/27 20:56:46] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ConnectionManager:
[2018/04/27 20:56:46] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:
[2018/04/27 20:56:56] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:34719 ST: ssdp:all, MX: 5, MAN: “ssdp:discover”
[2018/04/27 20:56:56] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: uuid:4d696e69-444c-164e-9d41-b827eb664f1d
[2018/04/27 20:56:56] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: upnp:rootdevice
[2018/04/27 20:56:56] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:device:MediaServer:
[2018/04/27 20:56:56] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ContentDirectory:
[2018/04/27 20:56:56] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:schemas-upnp-org:service:ConnectionManager:
[2018/04/27 20:56:56] minissdp.c:258: debug: Sending M-SEARCH response to 192.168.1.12:34719 ST: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:

2

Plex ssdp searches are every few seconds and not many a second

udp port 34719 is not one used by Plex Media Server or Plex DLNA server

Why do you think it is plex media server?

could you do a netstat -a -b to see what ports are being used

3

You could use wireshark to see if there is some info on these SSDP searches that would help identify the source application and if it is as you believe - being Plex or some other program

4

Hi @sa2000 Yes i’m certain that this is plex sending SSDP request… because when i turn off plex with
“service plexmediaserver stop” i don’t get these requests anymore from that ip 192.168.1.12 (where is plex installed)
And every time i start plexmediaserver port is different, it’s never the same port…i copied requests again for you yo see that i get several of them per second, 6 times per second…

[2018/04/28 16:33:27] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:33:37] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:33:47] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:33:57] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:34:07] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:34:17] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:34:27] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:34:37] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:34:47] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:34:57] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:35:07] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:35:17] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:35:27] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:35:37] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:35:47] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:35:57] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:36:07] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:36:17] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"
[2018/04/28 16:36:27] minissdp.c:704: debug: SSDP M-SEARCH from 192.168.1.12:43394 ST: ssdp:all, MX: 5, MAN: "ssdp:discover"

I restarted again plex just to confirm and port is now 192.168.1.12:47981, and not 43394…
also after netstat -a -b i get

netstat: invalid option -- 'b'
5

oh sorry that is the source port number. The search would probably be on destination port 1900

Although you are seeing 6 a second - the searches are actually every 10 seconds. Could you see with wireshark what the search destination port is and if it is the same on each of the 6 searches and the type of the search is identical

But … SSDP searches every 10 seconds is harmless - every 5 seconds is also harmless. Really it is only an issue if you are getting hundreds a second. The above is just showing 6 every 10 seconds - that should not have any impact

Actually your last log shows 6 a minute not 6 a second - one every 10 seconds

The netstat -a -b is probably windows only
What I was after is identifying application names - you can see web pages like this to see what parameters are available for listing ports and programs / processes
https://www.tecmint.com/20-netstat-commands-for-linux-network-management/

But it is probably not necessary as I misread the original log thinking it was destination port for the SSDP search

6

Oh my god, I’m a fool, you are right @sa2000 … these requests are indeed every 10 seconds. I did’t pay attention right…
thank you and sorry… next time i will check 3 times before posting something

But, if i want to block these requests with iptables like

iptables -A INPUT -p udp --dport 1900 -j DROP

I will not loose anything special because i don’t use plex dlna?

7

Hello, I want to disable SSDP in plex, every 10 seconds it launches a request and as plex I have it in an installed vps I am not interested.

Of course I blocked traffic on the firewall, but it generates many errors in the log.

If it cannot be deactivated, can you at least increase the time of 10 seconds in some way?