It's always done it, I've been running Plex on this server for a year or two now, it seems more often now though and seems to be more when I don't use Plex (this occasion I was away on holiday and came back to no Plex on my TV). My nas is pretty much just running plex and ftp. (there are 4 plex crash uploader logfiles, but they don't provide any info) quad core intel based qnap with 8gb of ram. Nothing in the logs looks awry, Plex is up to date, and the version seems to have never had any effect on the problem. And then it works fine for 3-10 days and happens again. My family sends me a text saying the plex is down and I have to open the app center "stop" plex and then when its done stopping "start" it. did it just start for you or did you recently set up qnap/plex? I have the same problem! and I have for the past year. Zipping the file helps to minimize that a lot. Not that anyone cares, but the internet and bots are ruthless. I sanitize any mention of my ip address in 192.168.40.1 format or in 192-168-40-1 format, also usernames, email, home directory, computer, and video I'm used. Upload the zipped log here or to the Plex forums, and let me know.īoth of you can do that.
RESTART PLEX MEDIA SERVER ZIP
If the problem occurs again, restart the server and zip up an older file, the `Plex Media Server.1.log` because that's the one that holds the problem while the unnumbered log file will have logged only the reboot. I'll have a look to see if it's generally happy. Sanitize, zip, and upload only the `Plex Media Server.log` as a zip.
RESTART PLEX MEDIA SERVER DOWNLOAD
I'd enable server debug logging again, reboot, and after 6min download the logs.
I'm used to reading the whole logs and problem solving them on the Plex forums. The double NAT and unreachable may not be related, but one of them may be your issue. Because Plex is made of a number of modules of open source code, the error recovery isn't the greatest when it comes to weird files. The SSDP discovery errors are not important. So i just looked at the errors, seeing a lot of connection refused and double nat stuff, with a few malformed files it's trying to read. It only keeps a max of 6 and will delete the oldest to make room a new one. You may have to leave your debug logging enabled until it dies and read the last things to occur, focusing on the same keywords. Weird hangs like yours aren't too common. Uncheck your debug logging and save the changes. You could also check your for those words, but there's false positives about 403 http stuff. Which is plain text file in good text editorįind any occurrence of the words "error" or "critical"? It drops a folder, you go in there and you open Plex Media Server.log Go into your Admin account and use your Wrench Start your Plex app on your computer again. Power cycle the NAS if possible, or at least Stop and Start the Plex Media Server app. To your left click the checkbox for Enable Plex Media Server Debug Logging and then Save Changes To your far right click the words Show Advanced but if it says Hide Advanced don't bother. In the left hand column, carefully find the Settings section half way down. I use my administrator account if I have multiple Plex family users.Īs the admin in the Plex app I click my wrench in the upper right hand corner to open the main settings page. If it's responding to Stop Starts from QNAP that's good. We can grab a debug log from the Plex server.
0 kommentar(er)
