TODDLT

I've had some earlier posts, about the permissions granted for files that are generated by the Plex DVR using the LinuxServer.io docker. I started a new thread in the general forum looking for more help on the subject : https://forums.unraid.net/topic/82188-file-permissions-issue-with-plex-docker-linuxserverio/?tab=comments#comment-763917 I've had some help there and the most likely issue is the UMASK variable and I'm posting the basic info here so someone can look into a permanent fix. This would only be a problem for someone using the Plex DVR feature and then also wanted to be able to move or delete files that have been created by Plex. I know you can delete files from inside Plex, but 1. I dont want anyone logged in on a TV in my house to be able to make that mistake, and 2. There would still be a host of files and directories that can only be modified by plex, unless the "new permissions" utility is run. There is a lot more information if you go follow the thread in that link, but here are the highlights: Here are the permissions shown using the ls -al /mnt/user0 command: This folder was created using the Plex DVR drwxr-xr-x 1 nobody users 33 Jul 30 20:05 Bxxxxxg\ (2019)/ a similar folder that was created from the old plex (Limetech docker) DVR reads like this drwxrwxrwx 1 nobody users 52 Mayt 15 22:31 Bxxxxxxx\ (2017)/ His comment was: The umask 0000 needs to be called in the docker after the filesystems are created - in whatever entrypoint script is being used. I'd file this as a bug with the LS.IO guys on github or in their support thread. You can readily prove that the UMASK isn't being set properly; EDIT: attached is a screenshot of the file/folder stats created by the Plex DVR. I hope this is enough to get something going. If this is incorrect and the UMASK setting is correct already please let me know.

Can someone explain the variables for PUID and PGID in the Docker settings (at the end)? The default values are 99 and 100 respectively. These are User ID and Group ID settings, correct? What do the values mean, or is this where it determines the user ID the docker operates and creates files under? I posted a thread in the General forum https://forums.unraid.net/topic/82188-file-permissions-issue-with-plex-docker-linuxserverio/ and after a little investigation this was the summed up message: The Limetech docker did not have this permissions issue and also did not set values for PUID or PGID, or if it did, there were no adjustable settings for it. Is it possible these settings are what is causing the issue? Can they be changed or what happens if I delete them? Thanks as always.

I can't be the only one using Plex to have this issue. How do you fix this?

to be clear, the only files I"m having issues with are files the Plex DVR creates. For some reason they have permissions restricted to the user "nobody"... I dont think Plex actually uses "nobody" I think its a blank in the file when it's created so unRaid is calling it "nobody." I also dont think this is due to the Plex update, I remember having this when I first started using the Plex DVR. I can't recall what was done to get over the issue, it was a couple years ago.

My windows user is same user/pw as the administrator on the unRaid machine. It should have read/write to everything. However it doesn't have permissions to the DVR movies that Plex creates until I run "New Permissiosn" Odd, but I can't figure it out.

I don't use either of those. I've searched through every setting I can think of and can find no reason for it to be doing this.

yes that works, but I have to do it every time. There has to be a way to stop it from creating secured files.

so how do you fix that? Plex didnt have this problem on the previous install. Can you change the "user" for Plex?

Yes, it works. I'm guessing because unRaid is seeing Plex as the user "nobody" and but not seeing me as "nobody" when I'm trying to delete from my PC. (see image). The question is why are the files restricted to "nobody" for write/delete access?

I have that function disabled to avoid someone's accidental deleting a video. When I had the old plex docker running I could delete files through explorer as any other file. this is a permissions issue with the new plex docker install. I think I had a similar issue when I installed Plex on the Limetech docker years ago. I can't recall how it was fixed and can't find any thread in my history here either. That being said, I will turn it on just to give it a try.

So the only outstanding issue is Plex DVR recordings having restricted permissions so I can't delete them without first running "new permissions"

got it.. yes makes sense now Thanks all

ahh, OK so the docker settings correlates /transcode to /mnt/user/transcode... yes?

Where do I find the run command? Isn't this set up in the background? I didn't create a command to run the Plex Docker. The transcode path in the docker is identical to what you see in the plex image attached.

I have the same pathway set in the docker, and inside the transcode settings in the Plex GUI.

They are both on the cache drive, but different folders. Transcode is /mnt/user/Transcode/ Transcode is located solely on the cache drive. Docker is located /mnt/user/appdata/PlexMediaServer/ appdata is also solely on the cache drive. Is there something else I should be looking for?

Still working through some bugs since installing Linuxsever.io Plex. I had two movies streaming from Plex. 1 was being transcoded, one direct play. Nearing the end of both, I get this warning on unRaid. It crept up to 83% until the first movie stopped and then I got a "return to normal" message. Docker high image disk utilization: 2019-07-27 10:05 Warning [-SVR] - Docker image disk utilization of 80% Docker utilization of image file /mnt/cache/Dockers/docker.img I can't find anywhere to raise the size of the size of the image file or space allocated. The Cache drive is 250GB and only 24GB used by dockers. I'm sure transcoding is taking up some space but how could that possibly fill that drive? Any thoughts appreciated. EDIT: I found this, but no idea how to increase the size of a container of if that is the issue The old Plex is not running, just haven't removed it yet, but I do notice it's a bigger container. I had as many as 4 or 5 streaming continuously before and never had that warning. Name Container Writable Log --------------------------------------------------------------------- binhex-krusader 2.23 GB 18.9 MB 66.2 kB binhex-minidlna 1.42 GB 1.49 MB 598 kB DiskSpeed 939 MB 1.21 MB 29.1 kB PlexMediaServer 526 MB 354 kB 229 kB PlexLinuxserver.io 355 MB 309 kB 4.33 kB tautulli 256 MB 122 MB 3.04 MB

Thanks will adjust this tonight. Any thoughts on the access rights issue to files created by Plex on the server?

So last night I migrated over to the Linuxserver.io docker from Limetech. Everything came up just as I was looking for. However, I have one issue, and one question.... Issue: Any DVR recorded file is being setup with the username "nobody" and I can't delete any of the video files created until I run the "new permissions" utility. This happened once before I can't for the life of me remember what I did to fix it. (see image) Question: How do I confirm where transcoding is taking place (temp folder)? In the Linuxserver.io docker settings it is set to mnt/user/transcode... The "Transcode" is on my cache disk only. Inside Plex, the transcoder settings originally had \\cache\transcode. When I first tried to record after the new install, I was out of space errors. The \\cache\transcode would seemingly be a bad pathway, I can't recall when I plugged that in and it must have been held over from the old setup. However, it was working previously. I deleted that pathway in the Plex transcode setup, and the errors went away. Here is the question: Where is it transcoding to? With the actual plex software transcode location blank, is it respecting or using the location designated in the docker? I do want it using the cache drive for transcoding, there is plenty of room. Thanks in advance for any help.

yes. Linuxserver defaults to appdata/plex, but I pointed it manually to the old appdata/PlexMediaServer BEFORE Applying the settings the first time. You have to extend the "more settings" section at the bottom to see this. Everything pulled right up for me. The only other step is to map your share pathways exactly as they were in the old docker setup. You can "Edit" them and change each. Let me know if this is confusing and I'll send more on it tomorrow. This option is in Linuxserver. I didn't see it in my old Limetech, though I thought there used to be a way to tell it what version.

yes just tried it, and worked fine. Thanks!!

I believe I would like to migrate from the Limetech Plex Docker to Linuxserver's Docker. This really has to do with the speed at which updates for Plex are released and while I appreciate the conservative view in not running to fast into new updates, I am about to lose my DVR service over an update and can't seem to get a response on when the update will be added to the respository. So with all respect to them, I have a friend who uses Linuxserver and has not had any issues. The question I have for this group is how do i install a new Plex docker and point it to my old Plex database? I'd rather not have to re-scan and make manual adjustments to my libraries. Is this even possible?

Separate question to the above. I have now realized there are 5 different docker containers for Plex and I don't see much explanation of why one would be different over the others, except for who maintains the docker. Very simply, is there any real difference between them? If I was going to migrate (to Binhex) Can I install the new docker and will it point to the same Plex database? IE can I keep both set up and just change which one "auto-starts" with unRAID until I confirm it's all up and running correctly? If not what would the process be? I have a rather large media collection with quite a bit of custom tweaking of the database, IE how movies are organized. Starting over would be extraordinarily painful. Thanks again.

Hello to any Plexusers who do 4K video and/or use GPU accelerated transcoding: I am a PlexPass user on unRAID server. I am just moving into 4K videos. After doing a 1st test run, I’m finding that my CPU which can manage 4 or 5 1080 transcodes simultaneously is pretty well tapped at 2 - 4K transcodes. The CPU is an intel E3-1241 v3 and scores 10,000 passmarks. So that said, I’m now looking at how much my GPU in the PC speeds up the H264/265 encoding when ripping movies and wondering if using GPU hardware acceleration will do the same for transcoding Plex Streaming. I’ve read the page on the Plex website with some pros/cons and the page suggests what while faster / smoother the use of GPU accelerated encoding can reduce overall quality and create a blurry/blocky look. I’m looking for some real world feedback on the use of GPU accelerated encoding before going too far down the road with my server. I would have to purchase the GPU and replace my MB to make this work (one slot short) and not wanting to go through that expense if ultimately it will degrade the quality that much as it would be a non starter for me. I think this will cost me somewhere between $275-350 do, but going to an E5 processor would be far worse. I also know implementing this in unRAID has an additional set of complexities and will work on those separately. I have some bookmarked pages I need to read before bothering to ask any questions on that front. Does the use of GPU encoding make a difference that anyone has noticed? Is this driven by the quality of the GPU or is this for all GPU’s in general? How high end of a GPU do you need to accomplish a meaningful change and not reduce quality? I was thinking an nVidea GTX 1050 or 1060, thoughts? Am I understanding correctly that Plex either only uses GPU or CPU for encoding, not both? Does the use of GPU accelerated transcoding affect how Plex DVR works? Any other thoughts based on your experience that I should know or consider before going down this road? Thanks in advance.

Thanks, After watching this for a few days it appears the exclusions have solved my issues too.