i use transmission to download time to time and when i wanna rename files i get error that i cant using nobody it says in windows

i googled about checking file perm

stat -c "%a %n" *

and what i get is 644 in front of the files.. now it doesnt do this always to all files sometimes i can rename files sometimes i cant so i do the New Permissions on my download drive and the folder on the array transmission moves the files from the download drive to the specific location on the array..

and transmission is set to PUID 99 PGID 100

so why does this happen? is it because its moving from drive pool which my download drive i use is a 2tb drive and it moves the files to the array is it happning there? is there something i can fix or add etc its always happening

and even if i make a root share through the unassigned devices i still cant rename under it

is there a something thats a perm fix or you need to run like script that runs everyday to new perm... like why does this stuff happen as before unraid i was always using Windows Home Server 2003 and 2011 so no permissions just copy and thats it..

so i not sure if this is an unraid thing, a linux thing, a transmission thing so i dunno

and i have no idea what 644 means google says 6 = own.. well is that the 6th owner who is owner number 6?

as i have like 15 users + root user which user out of 16 is number 6 as its not my samba connected from windows to unraid box

i ran stat -c "%a %n" *

in another folder of my temp downloads transmission moves too i get

777

766

755

666

like they should be all the same or if i move files from one folder to another i guess you get different permissions but why does it happen why doesnt a user just have same permissions or what not

and also transmission sometimes says it cant move the file to the array because it doesnt have the permissions... but the 99 100 supposed to allow it so i dunno why this happens

Edited June 3Jun 3 by comet424

In appdata for transmission, what do you have in settings.json for umask?

the umask says "022" whatever that means

and i didnt reboot so here is the diagnostic

tardis-diagnostics-20260603-1123.zip

i googled what 022 means anyone can read or run them i guess

but only the owner can modify it

but if the owner is 00 100 supposedly thats nobody.. then eitehr nobody can modify it or its anyone can modify it..

these permissions stuff drives me nuts sometimes

and if you copy from windows to a folder on the array should that be all access? as i noticed some of the files i either copy from hot swap ssd in my array but i move off the drive and onto the array using windows i just have a auto share on it gets a different permission and i guess if i use a move in unraid file manager that be a different permission and if i use krusader thats a different permission?

33 minutes ago, comet424 said:

the umask says "022" whatever that means

umask is a bit of a difficult thing to wrap your head around. See here for one result of a google search:

https://www.geeksforgeeks.org/linux-unix/umask-command-in-linux-with-examples/

Basically, umask of 022 turns off the write bit for 'group' and 'other'. Unraid does not want you to do that! With today's Unraid default security access mode, access for most users will be through the 'group' permissions. Particuliarily if you are using the 'Secure' or ;Prinvate' security modes.

You can read a bit more about what is going on in this thread:

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/

Understand that many Docker Containers run under Linux and access the Unraid file system directly using standard Linux file commands. Further if the container was not specially prepared to work with Unraid (and many are not!), they may use the standard Linux file permissions which are 755 for directories and 644 for files as these re the current security recommendations for most Linux distributions.

@Frank1940 with my dyslexia and learning disabilityi have to re read those 2 links i read the first one a bit and ya brain not functioniing to understand it fully yet

and ya most of the or all my shares are private and i got 1 public share,, and some shares that are - dash i guessing thats because i dont export it

so basiclly unraid has gone a different route for permissions then basic linux permissions from how i understanding what you were saying

and how do you know if a docker container for unraid is perpared for unraid... is there something i can fix transmission or the krusder or windows that prevents messed up permissions? i like the permissions of the users they can get read write for this share or that share..

so is there a way to mod transmission to change the 644? and what is the permission should be fore files? since the files are 644 and i cant alter them.. but it doesnt do it to all the files transmission downloads.. its like hit and miss when you can alter the files why is it hit and miss?

so is there something i can add to transmission docker to fix the issue?

so regular linux uses 755 and 644 so what does unraid or windows use when we copy to unraid from windows

12 minutes ago, comet424 said:

and how do you know if a docker container for unraid is perpared for unraid...

I am not the best expert for Docker Containers. But f you left-click (#1 in the figure) on container's icon, you will see the drop-down menu. then click on #2 and see where the support thread is and take a look at it. If it is on the Unraid User Forum, you are part way home. You need to check to see how well it is supported. Even if support is minimal, you can still ask your questions there about fixing this issue. Most containers are configurable using the 'Edit' tab in the figure below. You can add new configuration variables but you have know the exact name and spelling.

21 minutes ago, comet424 said:

so is there a way to mod transmission to change the 644?

Yes, run the 'New Permissions' tool in the TOOLS menu. Be sure to read the instructions and cautions about not running it on certain shares!!!!!!! You want to run it only on those shares which have the problem. Note that this will only fix the problems that currently exist. If you run the container again, you will probably have to run the tool again afterwards.

28 minutes ago, comet424 said:

so regular linux uses 755 and 644 so what does unraid or windows use when we copy to unraid from windows

Unraid sets and expects the permissions to be 777 (directories) and 666 (files) that it writes using Samba and NFS (Linux). Group will always be "users" but the owner is often the name of the Share User. (Some folks have told me that 'nobody' sometimes is assigned as 'owner'. I know that Samba can be set up to force the 'owner' to be a specific user name. So I am always careful not to say that this is the way things are absolutely. I don't pretend to be a SAMB/SMB expert. I do understand a fair amount about how it works and I can only share that info.)

@Frank1940 ya thats what i normally do is set the new permissions so ya i read you dont wanna use the new permissions on appdata.. i have done that in the past as i wasnt able to delete certain folders unless i was using like krusader or midnight commander... its frustrating ... and why dont you want to use new permissions on all the the folders really... if we are only doing users with certain read write access to the specific shares it shouldnt matter right?

so i guess the only work around is user script that runs like twice a day or so that does new permissions on shares so it doesnt mess stuff up?

and what is the reason you really dont wanna run new permissions on the appdata... dont you want everything to be nobody..

so you mentioned "nobody" is an assigned user... do you mean under users they made a user account nobody... and if so is that some kind of work around

i appreciate your help so far it is frustrating with these permissions etc..as you think jus copy a file or move and its just how it is as i been a windows user for 40 years and you never needed to deal with permissions really sure you had in the properties of a file but really copy and paste or what not and boom bobs your uncle lol

i see the transmission support page is on unraid site so ill ask there for help too..

1 hour ago, comet424 said:

so you mentioned "nobody" is an assigned user... do you mean under users they made a user account nobody... and if so is that some kind of work around

'nobody' is a very special user that was required by the Linux kernel many, many years ago. google nobody linux user

2 hours ago, comet424 said:

and what is the reason you really dont wanna run new permissions on the appdata... dont you want everything to be nobody..

The reason is the the appdata share is intended to be used by Docker Containers and, perhaps, some VM's. As a result, any files in that share should never by accessed by an Unraid user. It is the location where the configuration variables are stored and any files that are only used by the container. Thus the owners, groups and permissions for the files/directories are set for use by the container. If you run the new permissions tool against that share, you may break some containers!

2 hours ago, comet424 said:

so i guess the only work around is user script that runs like twice a day or so that does new permissions on shares so it doesnt mess stuff up?

No. The solution is to get support from the Docker Container support thread to assist you to configure their container so that it works with Unraid. Unfortunately, there are a lot of apps shown in the APPS plugin that are not well supported. The ones mark 'Official" or "Limetech" are generally properly configured to work with Unraid. If you don't find one so designated, then look at all of the apps offered and try and find one that has a active support group to use.

@Frank1940

ah ok ya i guess i get frustrated too like some of the apps you gotta alter the configuration file after you install.. and when i access file from windows accessing the appdata i cant i dont have write

all i can do is that darn nano and its not as nice as note pad... and that frustrates me but i guess the root has the nobody has writes over everything universal god mod.. as i also find sometimes i cant delete an appdata folder app in windows or krusdader.. i found if i run

rm -r <container name>

is the only time i can delete something as i uninstall apps and try to get rid of the old stuff.. so i found that is frustrating too..

so how does it break some cointainers if you make appdata all nobodys god mode.. as if you have a different owner wouldnt it just go along with nobody user.. i dunno i dont understand this linux stuff my linux days stopped 25 years ago with redhat 5 and i i had to do tricks just do mount a cdrom in the gui i got fed up and stuck with windows.. and then when i out grew windows home server 2003 and 2011 and ms doesnt make home server os anymore... so i found unraid but still learning..

ill look for more offical thats what i usally install... what drives me nuts too if there ins a app and there is 4 version one says offical, another says linuxserver, another says tools and one other i saw like i never know what one to install be nice not to have dupes,, especially with the info text is the exact same across the 4 types.. so you never know what to install... like the krusader there is like 2 or 3 but you trully never know what to install

madding at times

from the one site i read i guess nobody is the lowest secure so basiclly i guess its like public access like for sharess public secure private

and the 99 100 is the low level nobody account that anyone should be able to access and the 22 umask supposed to give the default access

something like that i did post in the transmission forums to see why it glitchs and gets the 644 but who knows if i get answer but i asked

22 minutes ago, comet424 said:

ah ok ya i guess i get frustrated too like some of the apps you gotta alter the configuration file after you install.. and when i access file from windows accessing the appdata i cant i dont have write

You shouljd be able to do that using the 'Edit' from the dropdown menu.

IF you require greater access to the files of the container, you should use the 'console' choice from the dropdown mennu. (See the screenshot above in this thread.)

You have to realize that any Docker container is an totally independent OS from Unraid. Some Containers use the storage space on the Unraid server just as you do when you save a file via a user share. You do expect that you will have unrestricted access to the files of all the user share users on your server, do you? You are not intended to access any files in the appdata share via Unraid!!! If/when you do you are hacking the container!

@Frank1940 ya edit no good

cuz like the program Caddy,, you gotta edit the configuration file under appdata/caddy

well you cant edit it with the notepad ,, as you cant save always tells you to save a different file as you cant save

so you gotta nano the configuration file

so Edit is for the Docker container template but u still gotta edit the configuration file

same with Plex and Jellyfin or autheli Authelia you gotta modify the json or the settings.xml file and they usually write protected so i have to nano edit them.. and notepad is better easier to edit..

and i tried your goto the console to be able to edit a configuration file.. but there is no "nano" in console of the dockers

but i hear ya u dont wanna bugger up the container i just figured if you new permission it to nobody with the lowest that anyone can edit even if the container had higher write access or what not it wouldnt harm it?

but like you already know i dont really know that much iabout the permissions i just figured if you reset all them to a lower restriction the user with the higher access not going to ruin it cuz its like same user or less security

sorry my dislexia may messed up my explanation sorry in advance..

but always learning something new everyday... that when your modify the container your hacking it..

Just set umask to 000

@comet424
Since I also since recently have issues with the transmission docker and the permissions it gives:

What do you have under UMASK here in the container settings?

That should be 000 (that equals 777 for folders, and 666 for files, or drwxrwxrwx / -rw-rw-rw- ), and the container variable SHOULD be the authority regarding the dockers umask, not the settings inside the applications settings file.

Except it doesn't start at all when I set it to 000. So I'm curious if the same applies to you.
(If you gonna try it, make a backup of the appdata-files first cp -r /mnt/user/appdata/transmission /mnt/user/appdata/transmission.bak
, it broke my torrents after reverting back to 022, and had to restore that directory to restore the torrents (restore: mv -f /mnt/user/appdata/transmission.bak /mnt/user/appdata/transmission )

edit: Updated to latest transmission version now, and nothing broke when changing to 000. Either a bug in that last container version that was broken that's fixed in the latest, or just one unlucky try.
I'd still do a backup before you change the umask setting though. A lot of work manually restoring until I remembered I had a backup.
But remember to change it in the container settings above, not in /mnt/user/appdata/transmission/settings.json, it's authoritative and recursive to the app settings. While app settings is not recursive to container settings.
BTW. I think the UMASK 022 (drwxr-xr-x / rw-r–r–) was changed with an update of the container, and was 000 before (transmission has always written files with drwxrwxrwx / -rw-rw-rw- for me until very recently), that would explain why you get another permission when you move. If you downloaded the file when container was at umask 000, and moved it when container had changed to umask 022.

Edited June 4Jun 4 by tshorts