It might be linux commands like tcpdump
if you get that to work, would be useful to also enabled the advanced hidden setting for Plex Media Server for TLS Logging to allow me to decrypt the captured packets
eg following for public port 32400
tcpdump -i any -w pmscapture-xxxxx.cap port 32400
Once that is successful, I can send you in a PM instructions for TLS Logging
What do I replace xxxxx with?
I believe that pmscapture is a filename - so could be something to indicate when capture started eg pmscapture-20200831-1630.cap
Once you know you can capture all tcp traffic let me know and i will send you instructions on what to do to enable TLS Logging in PMS
What would help for this is establishing what sequence of events leads to the problem so that it can be reproduced in house
And to establish why it seems to be mainly from QNAP servers.
Points to establish
Ideally would like debug server logs covering from the time when it was ok and up to the time when the pubsub connection got lost and leading to this error and network packet capture (tcpdump and with PMS TLS Logging) covering the time when the connection got lost and subsequent failure
If the problem is predictable then that should make it easier and minimize how much packet capture to have
So is it a Qnap problem? Qnap loses connection to the outside? Apparently I still have access from outside my network …
All I know is that eventually plex says no connection.
It is impossible to have logs from working until not working because I don’t know when it will stop working.
Apparently restarting PMS the error is fixed, but it should not be a valid solution.
Thanks.
This is clearly an issue with Plex on Qnap. My NAS network connections always are still working when Plex decides it has no internet connection. Every day or two I have to stop and restart Plex to get it to scan new media. It continues to be able to play media over the internet, but something internal loses its mind. It is not the NAS, it is Plex scan that stops working. The restart make it work again for awhile.
Have you tried ChuckPA’s solution (which worked for me)?
I did make that change but it the Plex media scan still stopped working. So, now with the state of Plex on my QNAP everytime I add new media I have to stop and restart Plex to get it scanned. This is clearly a bug in Plex releases for the last month or two. It had never happened before that for many years.
I’m on Synology and this problem just started for me. Music won’t update but everything else will.
I don’t know if being forced to use Google DNS is a solution per se. Some people actively avoid google for privacy concerns.
Still no answer…
Would be happy to look at fresh logs from the server - preferably covering time since last launch of Plex Media Server
How soon after restarting Plex Media Server does the problem arise ?
How many days before it happens?
Does the problem arise if the server is enabled for remote access and a manual selected port used with a port forward or dynamic upnp port used ?
Does aggregating network interfaces 192.168.4.31 and 192.168.4.30 into one interface help ?
What are the other two connections ? 10.0.5.1 and 10.0.3.1 ?
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
and for number of log files - see LogNumFiles
Advanced, Hidden Server Settings | Plex Support
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
A problem has been identified and fix included in 1.24.2.4973
