I have a shared folder: /volume1/media which I accessed freely under the previous DSM and Plex release. I couldn’t access the Plex folder so I followed the steps given and resolved that issue. There were no permission issues previously with ~media.
I moved some folders from ~media to ~video and watched plex index the contents.
But I can’t see into any of the libraries through the movies/video/other interfaces. I can see the live tv and online media , but nothing of my own on my server.
Hello,
I had the same issue but the solution worked (I had to give the right to 2 folders, Plex and the one with my library). So I can read my content on my PC.
Neverless, I have an issue on my player (on both Raspberry and NVidia Shield) : the player don’t display the content.
Any idea ?
I’m working on the solution (I think): All of my media folders were shared volumes i.e., /volume1/media, /volume1/music, … which are root-level shared folders. I found they wouldn’t index properly within Plex.
I recall two items from the DSM-7 install discussions: one had to do with special folders like Plex, Plex Media Server and AppData I think. The other opened the issue of root-level data folders - which appear to be independent from Permissions. I’m moving everything to /volume1/Plex/Plex Media Server/ and think I’ll be fully functional once everything’s there (about 5TB to be moved and it’s s.l.o.w.) as I’ve already seen files/movies transferred over and defined the libraries.
Since I’m just changing the location of a folder, there should be a way to define a logical path to ~/Plex Media Server for the data. It makes sense to do so. But my command-line skills are a bit dated and I don’t know how, so I’m spending two days copying files from one structure to another so they can be found by the system.
This seems to be working for me so far, but it’s a Rube-Goldberg process and I don’t like it.
Please stop trying to circumvent simple permissions issues without understanding how things changed in DSM 7. ACLs are how it works now, There is no circumventing it.
DSM 7 is VERY VERY VERY fragile and restrictive by design.
Please DO NOT TOUCH “PlexMediaServer” shared folder. That is for the package’s internal use. I even put warnings, and AppData folder, and MORE warnings – in 6 languages. Thanks for understanding
To fix these “permissions” problems, which come in different forms:
Most common – Control Panel → Shared Folders → EDIT the shared folder → Change “Local User” to “System Internal User” → Give “PlexMediaServer” permission.
Second most common – This occurs when permissions have been hand forced and the ACLs have been damaged . (Damaged – meaning they aren’t how Synology wants them) . Control Panel → Shared Folders → Right Click the Shared folder name → Actions → “Convert to Windows ACL” aka “Repair Syno ACL”. While repairing, you can assign "PlexMediaServer permission to your media files.
Lastly, It’s not a Rube Goldberg machine but yes it feels like one.
The proper resolution of this is UNDERSTANDING what was changed.
This is NOT “typical DSM” anymore. It’s a whole new platform with a whole new set of rules.
It’s just possible the announcement of DSM-7 didn’t specify all of the changes to the system and programs - with their relative mitigation. Or if they did, I somehow missed it - and I shouldn’t have. I should have seen something in BIG letters. But trial and error works, too - but much more slowly and I’m sure I’m missing *** something ***. Maybe not, but how do I know?
Oh, it’s abundantly clear, and I agree with you 100%, Synology did not announce all the changes they made.
If you knew what I know about how it works underneath at the application level, you would be very displeased.
The best analogy I can give you is:
Give “Compose” the following info:
a. tar ball containing the code
b, some non-privileged scripts to manage it
c. list of system resources you will need
“Compositor” then creates
a. A sandbox for your code and data
b. A private, isolated, non privileged, username for your program
c. Links the control scripts to the code
Gives you “Start” , “Stop”, and “Status” access APIs.
“Compositor” does all the work and hands you back “Success” or “Failure”.
If you’re referring to the Plex players not finding the server, that’s usually because the server’s ID changed (which happens when a server is erased and installed fresh --or-- a new docker container is created).
In either case, Taking the apps and repinning them to select a new default server resolves it. I usually take the lazy way out of that step by reinstalling the plex apps and Linking it again. My way is a different way to do the same thing.
I had the same way but it don’t work neither.
I tried an old player, try to disconnect/reconnect ==> don’t work.
I’ve install the app on a new device (PS5) ==> I can see my server but no library. The server seems offline.
.