UPNP Logs waking up NAS

[TeknoJunky]

just a thought, since the log is an error about being unable to get the xml, maybe you should TURN ON the unpnp of the router, so that the plex is no longer generating the error?

of course that may fix the log error, but still not stop the drives from waking up.

[Typhoo2n]

Unfortunately this does not resolve the issue.

Also when iterating through all the media server and UPnP options of the router, no change is obtained. The drives will be spun up after <10mins and I see the error as mentioned in the OP.

[pshanew]

Depending on how fully-featured QTS’ underlying OS is, you may be able to configure an iptables rule to block SSDP responses from your router. This rule would prevent all IP traffic originating from IP address 192.168.0.254 on UDP port 1900:
sudo iptables -I INPUT 1 -p udp --sport 1900 -s 192.168.0.254 -j DROP

This will prevent its responses to Plex Media Server’s SSDP queries from being received and processed. If you’d like to prevent any of PMS’ queries from being sent at all, you could do something like this instead:
sudo iptables -I OUTPUT 1 -p udp --dport 1900 -d 239.255.255.250 -j DROP

I wouldn’t recommend doing that, it will break functionality; potentially functionality that you want.

Notes:

• I don’t have a QNAP NAS on which to test, so use these rules at your own risk.
• iptables rules do not persist through a reboot; there are ways to have them be automatically applied, however.
• QTS may have its own built-in firewall which would be better suited to this task. The idea here is to block inbound traffic from UDP 1900.
• As mentioned above, there are other things which will cause PMS to create log entries and spin up your drives, so this may not help at all.

[Typhoo2n]

Thank you all for your input and time trying to help me on this. For the time being I will stick to scheduling Plex for specific hours when I need it.

As a comment to the developers, I believe it would be a great feature if PLEX would actually allow for non activity times (or solely scheduled activity times) so that servers could spin down drives for a consecutive period of times as it might be useful in classic home applications, where the server is mainly used for movies, music etc.

Looking forward to future releases.

Best,
Typhoo2n

[SchneiE1974]

I have similar issue with my Synology NAS…have also turned off everything but PLEX writes every 30 seconds into the log that it could not query my Fire TV Stick…and there is no option to turn off UpNp there…this definetly keeps my NAS from going into Sleep mode and turn off disks…

I would really like an option in PLEX to ignore UnpN or option to not log it.

Thanks

Erik

[manish_vallabh_mv_gmail_com]

I have the same issue I have two fire stick 4k devices and Plex scan’s them and generates errors all day long. Doesn’t seem to cause problems, but filled up the logs and puts unnecessary writes to the NAS. Synology DS920+. I tried with UPNP on/off etc on the router, disabled all sorts of stuff in Plex configuration however it continues to scan. Tried disabling UPNP on router (Google WiFi Mesh router) no go.

M.

[SchneiE1974]

Did anybody face the same issue or found a solution to it ?

[manish_vallabh_mv_gmail_com]

I added a firewall rule to my Synology NAS to block all UDP traffic to the IP’s of my firestick 4k’s and my android TV. That was the only way I could resolve it.

M.

[SchneiE1974]

@manish_vallabh_mv_gmail_com , I tried the same but no luck. can you explain or show which Firewall rule you did set in your Synology ?

I did block port 9080 of protocol UPD for both, source and target of FireTV stick IP , but still do ge t below messages every 30 seconds in PLEX MEDIA SERVER.log file

Jun 11, 2021 11:03:25.092 [0x7f1b68c43b38] ERROR - XML: Entity: line 1:
Jun 11, 2021 11:03:25.092 [0x7f1b68c43b38] ERROR - XML: parser
Jun 11, 2021 11:03:25.092 [0x7f1b68c43b38] ERROR - XML: error :
Jun 11, 2021 11:03:25.092 [0x7f1b68c43b38] ERROR - XML: Start tag expected, ‘<’ not found
Jun 11, 2021 11:03:25.092 [0x7f1b68c43b38] ERROR - XML: status=ok
Jun 11, 2021 11:03:25.092 [0x7f1b68c43b38] ERROR - XML: ^
Jun 11, 2021 11:03:25.093 [0x7f1b68c43b38] ERROR - Error parsing content.
Jun 11, 2021 11:03:25.093 [0x7f1b68c43b38] ERROR - Error parsing XML: Error parsing file.
Jun 11, 2021 11:03:25.093 [0x7f1b68c43b38] ERROR - SSDP: Error parsing device schema for http://192.168.178.101:9080

[manish_vallabh_mv_gmail_com]

You have to block all ports, for UDP to the IP of your device. I have 3 devices which were generating the same error. Ports 1-65535/UDP Source IP is the device which is generating the error. and choose Deny..

Hope this helps.
M.