@ChuckPa Thank you so much. I really appreciate your awesome customer service on these forums. I’m still debating where or not I want to go with a direct install or try using Docker. NASes, Linux, and Docker are all new to me so I’m trying to figure out what is best. I’ll keep watching for any future announcements but understand why they can’t be discussed right now.
Unless you have docker mastered, and can make it dance when using docker compose or docker run at the command line, then i would stay with the app.
I cannot provide any support for docker on Synology at this time as I do not have a local resource
you want to map the host /var/packages/PlexMediaServer/home directory to be the new /config .
EDIT: I forced docker to work with the new structure. It required editing the container’s ‘run’ script after the environment was set but can be done. Not something a beginner should attempt. Changes do not survive container upgrades.
Hi. Had the same issue with forbidden access to the photo folder. I solved it by following next steps:
- Delete Photos app
- Delete photo folder
- Create photo folder by myself
- Configure access to it for Plex
- Add photo folder into plex library (check that everything works)
- Install Photos app
- Enable shared space (not sure how it’s called in English localization) in Photos (check that everything works)
For now it looks ok.
No need for full access, rw is enough on plex folder
Warning –
If performing migration – FULL CONTROL is REQUIRED
Full Control ACL is the only one which permits changing from user plex to service account PlexMediaServer by PlexMediaserver . (so the automation works)
@ChuckPa
I agree with you that Plex does only need Read Only rights. I think that media management software should never be able alter original media content.
I installed plex on my DSM7 using the following steps:
- Download package from Plex Downloads and installed it.
- Create local group, for example “plex”.
- Login via SSH on a terminal.
- Add the system account “PlexMediaServer” to local group “plex”
sudo synogroup --member plex PlexMediaServer
- Add local group “plex” to shared folder “Media” with Read-Only rights.
The upside is that I can see and use my local group “plex” to configure security. I prefer setting security using groups over individual accounts. The downside is that in DSM, I do not see the user PlexMediaServer as a member on this local group, which it is as can be seen using the command “sudo synogroup --get plex”
Hi, I’m completely lost and have no idea what to do. I didn’t read the instructions before upgrading to DSM 7.0 from DSM 6.0 and don’t know how to fix things.
–I uninstalled my Plex Media Server and selected the ERASE function.
–I reinstalled Plex Media Server and gave plexmediaserver full control ovefr my shared folders
–Now my server doesn’t work but when I go to my IP address and /web it shows me a new Plex server.
How do I manually move over my libraries to this new server?
thank you kind sir!
I went with the “erase” option
used the “get claim token” for installation
and, unfortunately, am greeted to the “not authorized you do not have access to this server” screen 
@ChuckPa ok. I’ll stick with the app for now. It’s installed and working, just need to rebuild some metadata and playlists at this point.
As couple others I do not have “custom” for permissions, I believe this is due to being on ext3 as it does not support Windows ACL. Is there any other workaround to giving the installer the needed access when Windows ACL is not in play?
Whoever came up with that term should be shot.
-
There are no “WIndows ACLs” on a Linux file system. “Linux ACLs” . of course and that’s what we’re using there.
-
Any Volume created in DSM 6 will minimally be EXT4.
Can you show me an example of a DSM system being EXT3 ?
Here is mine, running 7 using EXT3. I been using the same volume over multiple versions/devices so this predates 6
To add,
admin@nas:/volume1$ synoacltool -get Plex
(synoacltool.c, 489)It’s Linux mode
When was that volume created? DSM 4?
I have a DS216 currently, I don’t remember the DSM version but it was created on a DS210. It never has been a limiting factor for me until now 
RE: ACLs & Failure to migrate (ONLY)
This bothers me.
admin@nas:/volume1$ synoacltool -get Plex
(synoacltool.c, 489)It’s Linux mode
because it means someone / something performed a manual chmod after installation. chmod 755 will drop the acl every time.
I expressly set ACLs in the DSM 6 installer.
ACLs I set in the installer are:
synoacltool -del $PLEX_LIBRARY_PATH
synoacltool -add $PLEX_LIBRARY_PATH group:administrators:allow:rwxpdDaARWc--:fd--
synoacltool -add $PLEX_LIBRARY_PATH user:admin:allow:rwxpdDaARWc:fd--
synoacltool -add $PLEX_LIBRARY_PATH user:plex:allow:rwxpdDaARWcCo:fd--
To demonstrate EXT3 is not the limitation here:
(notice the ACL flag in ls -la)
[root@localhost mnt]#
[root@localhost mnt]#
[root@localhost mnt]# mount | grep mnt
/dev/sdb1 on /mnt type ext3 (rw,relatime,seclabel)
[root@localhost mnt]# ls -la
total 32
drwxr-xr-x. 4 root root 4096 Jul 11 13:14 .
dr-xr-xr-x. 21 root root 4096 Sep 12 2020 ..
drwx------. 2 root root 16384 Jul 11 13:13 lost+found
drwxrwxr-x+ 2 root root 4096 Jul 11 13:14 x
[root@localhost mnt]# getfacl x
# file: x
# owner: root
# group: root
user::rwx
user:root:rw-
group::r-x
mask::rwx
other::r-x
[root@localhost mnt]#
I believe the solution here:
- STOP manually performing
chmodon anything in DSM. - Set the following ACLs, via the SSH command line, adjusting for /volume1 or /volume2, etc.
synoacltool -del /volume1/Plex
synoacltool -add /volume1/Plex group:administrators:allow:rwxpdDaARWcCo--:fd--
synoacltool -add /volume1/Plex user:admin:allow:rwxpdDaARWcCo:fd--
synoacltool -add /volume1/Plex user:plex:allow:rwxpdDaARWcCo:fd-
synoacltool -add /volume1/Plex user:PlexMediaServer:allow:rwxpdDaARWcCo:fd-
- Now uninstall & ERASE
- Install DSM 7 package.
- Observe “Installing” as migration runs.
I appreciate the help. Will keep the file system in mind.
I tried the delete,
admin@nas:/volume1$ synoacltool -del /volume1/Plex
(synoacltool.c, 588)Unknown error
also tried an add,
admin@nas:/volume1$ synoacltool -add /volume1/Plex user:admin:allow:rwxpdDaARWcCo:fd–
(synoacltool.c, 268)It’s Linux mode
I was basing the ACL issue off of what Synology published,
- Windows ACL does not support ext3 file system. For users using ext3 file system, you need to create at least one ext4 or Btrfs volume to use Windows ACL permissions. This means that you have to format at least one drive and re-create a volume. Formatting Synology NAS will result in erasing all stored data and settings. Please make sure all your data is backed up before processing.
You MUST be root.
Admin user has no permission for the operations.
Re Synology. They’re talking about compability with Windows itself for CIFS/SMB mounts which is an entirely different animal.
It is true, EXT3 does not support all that extra information Windows wants to assign if you are trying to set WIndows permissions on a Linux file across the “Mapped drive”.
What we’re discussing here always is within the scope of Linux.
Synology handles how DSM talks to Windows. We handle how we talk to DSM from the Linux perspective.
1 Like
I tested with sudo as well, but here are root attempts
root@nas:~# synoacltool -del /volume1/Plex
(synoacltool.c, 588)Unknown error
root@nas:~# synoacltool -add /volume1/Plex group:administrators:allow:rwxpdDaARWcCo–:fd–
(synoacltool.c, 268)It’s Linux mode
Stand by please … investigating further.
I have a DS1815+ , with original file system, and it’s EXT4
I just upgraded the drives and volume over the years
