I have upgraded before finding this post…, so I have managed to install the plex version from ChuckPa (thanks for this) but all my movies are unavailable, only the info and posters are showing but can not be played. So my question: Is this going to be fixed in the update that we are waiting for or I have to uninstall Plex and make clean installation and add all my media from scratch? Thanks in advance.
If content is unavailable ----
you forgot about giving user PlexMediaServer (system internal user class) permission to read it.
Give a read here –
Follow through to “Migration Process”
Also pay attention to the final message I show during installation about how to give permission for your media on DSM 7
1 Like
I’ve gave Full Control of the user:
I’ve also applied it for the subfolders. When I try to add new library I see my volumes but can not see my Movie and TV Shows folders, I think that the paths or something like that broke during the upgrade.
Thanks for the directions, I understand it now, we must give permissions for every folder that we want plex to see in. Everything is fine now. Thanks for the help.
You don’t need full control
Read/Write is the most it will evre need
Read (to play)
Write (to record or optimize)
Not sure if it adds a ton to this thread but I got it all to work directly going from dsm6 to dsm7 rc. Tried it first on a vm which I would recommend.
- followed chucks steps ( thanks so much for the work )
- used his package from gdrive and made sure its newer than my dsm6 version
- uninstalling the old app otherwise you have cruft lying around in the var app folders
- my plugins continued to work the folder is in var packages
- I had one or two error issues ( didn’t create the log folder ) but a fix and second press worked
- all my data is still there
So basically I guess I would recommend waiting for the final version I had one or two heart stop moments but it all seems to work hopefully stays like this. 
. Thanks again for the help didn’t want to wait till end of July or whenever synology has the final version.
My Gdrive version is DSM 7 - ONLY. It’s not for DSM 6
Where is your data??? Stil in the Plex shared folder ?
If in the Plex shared folder then you didn’t migrate / install DSM 7.
1 Like
I meant that I upgraded from dsm6 directly to dsm7 rc without going through beta first, I understand that it’s a bit risky but it all worked well. The data got moved from my plex share to the var packages (@appdata ) folder. As far as I can see everything worked exactly as it should. Sorry for not being more precise. I know this thread is for issues so if you want it clean I can remove my post I just thought I give a data point that things worked out well for me following your steps. In case that info helps someone. Also thanks for your hard work and so xlosely following this thread, feels nice to have this kind of reactive support. I also liked the ability to store the logs somewhere easily reachable, I just kept the plex share for the log folder.
Good. Thanks for clarifying.
I was concerned you still had things in Plex share.
You’re good now on DSM 7. 41222 or 41882.
41882 is the last I will support until Syno settles down and gives us final product.
1 Like
To all others who may have not got this to work. I discovered that I had to convert the permissions to Windows ACL for the Plex folders in order to be able to set the custom permissions. Could not find that requirement anywhere.
Hope that helps other. Plex is now up and running.
just how many ACLs had you previously placed on the Plex share?
Setting a “Full Control” ACL in the GUI does not require “Windows ACLs”.
When my instructions are followed, this is the result.
user:PlexMediaServer:allow:rwxpdDaARWcCo:fd--
A “Windows” ACL has no merit or context here. This is a Linux machine where the data is not user-facing.
Can I ask what the status is regarding plug-ins? I saw in another post that due to changes in DSM 7 they may be going away permanently. The reason I ask is that I have two custom meta-data agents for populating information that live inside “Plug-ins”. Interestingly, they hadn’t been working after my DSM 7 RC upgrade and today I started looking into it and seeing the mess with DSM RC and Plex, which lead me to ChuckPA’s custom 1.23.2.4600 build which I’ve installed and hey, my agents are working again… so I’m just wondering what the plan is or the status might be with these going forward after Synology stop playing games and everything settles down.
@ChuckPA, thank you for your very informative and helpful posts. Just reading the messages from the past couple of days have helped me where I don’t have to ask about 6 different questions in the forums and I appreciate you making a build out-of-band for us DSM 7 RC users. Thank you!!!
The “Official Dirt” on Plug-ins:
-
User-plugins where officially deprecated in 2018.
Discontinuation of Plugins, Watch Later, Recommended, and Cloud Sync -
The Movie scanner was rewritten in C++. Python no longer needed.
-
The TV series scanner was rewritten in C++. Python no longer needed.
-
There is one piece which still used Python. It’s now being rewritten in C++.
That all having been said, and for as long as they work, AND don’t cause problems, You can manually install your own.
Be advised:
-
If a user-installed plug-in breaks PMS, it’s on you. We will point to the problem but it’ll be up to you to work with the plug-in developer for resolution.
-
When that final component using Python is remove, ALL of Python will be removed and ALL Python-based plug-ins will immediately stop working.
As it pertains to Synology:
-
DSM 7 forced a complete overhaul of how PMS works on the platform.
-
DSM 7 removed ALL “administrative” (root) permissions from all packages. PMS can’t even install itself anymore. It must ask DSM 7 to setup everything. It also must ask DSM 7 for access to the hardware every time it starts.
-
DSM 7 did not allow me to keep the “Plex” shared folder. I was required to use their storage locations & structure.
-
DSM 7 forced me to change the username (now it’s “PlexMediaServer” which is also the new package name)
-
If you can make plug-ins work, without breakage on DSM 7, then enjoy.
Synology overall:
-
DSM 7.0 “Release Candidate” (7.0-41882) introduced breaking changes to my packaging. I’ve mitigated those breaking changes and Engineering will be incorporating them soon.
-
UNFORTUNATLY, due to the impending changes Synology has notified us about, having discussed at length with our management, we cannot continue to devote resources to an unstable platform. DSM 7.0-41882 (specifically the packaging format) is the final version we will support until after DSM 7.0 is Public Release and stable with developer’s documentation available to us.
1 Like
I remember reading that plug-ins were going to disappear a couple of years ago but I’ve always been glad that they still work. Installing plug-ins now on Synology is a real pain because of the way the package gets installed. Totally get the “you’re on your own” theory - I’m savvy enough to futz with it to get it working and smart enough to let it go if it doesn’t. I was just more curious as to what underlying changes would/could prevent them from working.
Similarly I understand why they don’t let you use root (potential security issues) but it needs to be documented and stable with a workable way for you to install and run. I also understand your frustration and approach to further releases, until Synology stop changing things on you, you can’t be expected to provide working packages (so the idiots who keep saying “it doesn’t work, fix it” just need to be slapped with a sledgehammer). For me, right now, I have a fully-working Plex (thanks to your 1.23.2.4600 drop) and have nothing to complain about. I’m quite happy to wait patiently for Synology to go stable then Plex can go stable on it. I’d suggest people do the same thing and I imagine most will. Again, thank you for all your efforts and I hope it all gets shaken out soon and we can move on.
1 Like
Before converting to ACL, the option “other” under permissions were not present. I’ve only set read/write, but I weren’t able to access the permission editor before converting to ACL. Don’t know why.
It sounds like you got bitten by the same problem we did with DSM 7.
The reason I’m asking is because the procedure / instructions , which I show in the popups (as installation fails each time… with each iteration moving closer) is how to make it happen entirely from the GUI.
My final check is as I show. I look for that ACL to be present.
When it is, I know I have Full Control Linux ACL as user PlexMediaServer which now puts the entire share contents exactly as I need them to complete migration of the DSM 6 data under user plex to DSM 7 under user PlexMediaServer and move the data to the new DSM 7 location.
This is why “Windows ACLs” have no context. The data however it may have been stored, will end up in Linux ACL permissions in a new location.
It is a complete and clean break from the past. (and a pain to get there too)
This is the only way non-privileged user PlexMediaServer can move so much data so quickly.
Hi Chuck, I have DS218+ connected to Wi-Fi plus ethernet to newish Samsung Smart TV.
Keen to go to dsm7 for new Synology Photo apps I desire to use for a major project…
However with the Plex issues caused by DSM7 platform stability issues. I am hesitant to upgrade to DSM7 given its stability issues.
I don’t want to break Plex for home use… I’ll get too much grief…haha but true
Is there a version of plex on dsm 7 that is relatively low risk, that I could use?
I’m not a techy but know enough to be dangerous… So don’t want to break the synology and PMS environment.
If you are still on DSM 6, I strongly recommend you stay on DSM 6.
Synology will eventually release DSM 7.
My recommendation is to wait as long as possible before committing to DSM 7 because you cannot downgrade back to DSM 6 if you don’t like 7.
As for Plex,
-
The same Plex which runs on DSM 7, also runs on 6. I use the same programs as given to me by Engineering.
-
To work in DSM 7, I had to change
a. The package configuration (how it runs on DSM 7)
b. The location of where all Plex’s files are stored
c. Plex’s “service username”.
d. Most importantly, all the tools which install and run PMS.
I agree moving to DSM 7 is attractive but, given this is my career,
- DSM 7 isn’t in stable form yet. Synology is still making design changes.
- Any operation platform which has design changes made is not "Release Candidate status. It means “BETA” status at best,.
Please read my announcement again.
IF –
If you’re already using DSM 7. builds 41222 (Beta) or 41882 (Release Candidate) then
-
Freeze at that point. Don’t upgrade the firmware until we all have a more clear picture of the environment and how PMS will work.
-
Use the temporary packages I’ve created.
-
My temporary changes have been approved by QA and Engineering will start using them with their next main update. (not sure which version that is but VERY soon).
I hope this helps ?
3 Likes
Hi Chuck, firstly thank you for your prompt response…
Appreciate the comprehensive comments and recommendations.
Will wait for the official Plex DSM 7 version.
All the best
Paul
Auckland, NZ
Hi Chuck. I upgraded from DSM 6 to DSM 7 RC 41882 and with your help on the forum and temporary plex package my Plex server works as expected 
So thank you for that and keep up good work!
I have one tip to others that want to use default DSM 7 photo folder as photo library on plex. As I struggled with permissions and plex couldn’t access photo folder even when PMS user had read/write access I followed this steps:
How do I assign ACL permissions for sub-folders of the shared folder “photo”?
and finally plex has also access to photo folder!
1 Like
