(NOTE: I was 1.21.4.4079 last week as it was the last working version before this issue had started and updated it to the current version last night. I previously was running 1.22.2.4282 three or four weeks ago to see if updating the package would solve the issue.)
Player Version#: Plex for Windows - 1.31.0.2254-43df1e6e
This has been happening for over a month now, distinctly after I updated the package to 1.22.0.4163. While Plex seems to work, it will mysteriously stop running after a bit. I haven’t observed any consistent amount of time when it stops running, but it can stop after 15 minutes to about 8 hours after I start up the package in Synology. I’ve tried multiple things, like reverting to an older version since I’ve saved over 40 versions of Plex Media Server in case a situation like this came up. That didn’t work. I’ve considered backing up the media on the server and doing a clean install and rebuilding the whole lot to see if that would work but I’d like to not resort to that considering how involved it would be to work on.
Truth be told, I didn’t know. I’ve maintained everything via mapping it to Network Drive on computers, so I’ve only ever seen that look like language codes in the folder. I didn’t realize they actually were supposed to say anything in particular. Attaching what these files look like for reference.
EDIT: I forgot to mention, I’m currently moving everything, but it’ll take a solid day.
Thanks for the instructions. Worked like a charm. Took a bit still since I needed to configure some software to point to the new directories and not the old ones and make sure it worked.
I followed the steps after that and the behavior happened again where it seemingly stopped running. I was told just now by someone who was trying to use the Plex after I had left it alone for a few hours that it was down again so I went to grab the logs immediately.
This was migrated from a PC in 2018 or 2019. I wasn’t there for the entire process of everything being moved since I had someone help me with it before I was the only person maintaining it. This is the first time it’s acted up like this though since then.
At this rate, it might be quicker to just do a clean install of everything and redo everything from scratch. I’ve worked on this issue for a month stubbornly trying to keep the metadata intact but I might have to a throw in the towel for that.
Would there be any way to find which files are broken? I don’t mind replacing them. I just need to find a way to generate an itemized list for it and set aside time to do it.
If you didn’t start from scratch yet - when you tried older versions, did you uninstall the current one beforehand, or just installed one over it? The latter might cause issues, like it did in my case. Just in case you didn’t already try that, you can follow reinstall instructions here: Synology FAQ (DSM 5 & 6) - Questions, Answers, and a few How-To's - #14 by ChuckPa
