On 11/25/2024 at 11:42 AM, thany said:

I'm having some trouble with file permissions being wrongly set. Turns out the UMASK setting is the culprit. The default is of course 022 but I have to set it to 000 to fix it. I don't fully understand what it means, because until lately I didn't have a problem with it. I would suppose something regarding this feature must've changed recently.

 

I created a bug for it: https://github.com/linuxserver/docker-transmission/issues/295

 

But it looks like this is specific to Unraid. So for Unraid only then, would 000 not be a more sensible default? It doesn't seem useful that completed downloads cannot be deleted.

I have same problem. Can you explain where and how to set umask 000

@thany

Edited December 27, 20241 yr by sersh

Unraid system:Unraid server Plus, version 7.0.0
transmission 4.0.6-r2-ls281

trying to configure
 

Bandwidth

alt-speed-enabled: Boolean (default = false, aka 'Turtle Mode') Note: Clicking the "Turtle" in the GUI when the scheduler is enabled, will only temporarily remove the scheduled limit until the next cycle.

alt-speed-up: Number (KB/s, default = 50)

alt-speed-down: Number (KB/s, default = 50)

speed-limit-down: Number (KB/s, default = 100)

speed-limit-down-enabled: Boolean (default = false)

speed-limit-up: Number (KB/s, default = 100)

speed-limit-up-enabled: Boolean (default = false)

upload-slots-per-torrent: Number (default = 14)

but the settings.json gets overwritten when the docker is restarted. 
tried
"add configuration" > variable 
under the docker settings in unraid but nothing was changed in settings.json
how is this done correclty?

Hello all
A little question.
Do it possible to make few extra auto load folders in transmission to sort torrent files before downloading?
Or it's only possible in default folders?

Is there a way to set a layout in a json file? I would like to have the same column-layout in every browser window. Right now I have to set that separately on every device.

Lost 150-200 torrents when updating Transmission.

Usually update containers around once a month, this time it went some months before updating.
But when doing so, 150-200 torrents disappeared. About 5 of 30 torrents added yesterday was still there, all other torrents added from 2025-02-06 until update was removed from the Transmission client, if all torrents before that date is still there or if I lost random torrents at those dates as well I don't know.

How can I avoid that from happening again?
Would stopping transmission manually before update have saved me?

Edited April 10Apr 10 by tshorts

Is there a way I can change the default layout? I have a layout I like, but every time I open it in a new browser or new computer I have to spend a while setting up my preferred layout. It would be nice if I could just change the default on the server side.

is there a work around or reason why transmission even though its 99 100 uid pig and the umask is 022 that sometimes transmission cant move files off the download drive to the array permission denied or when it does i loose right to alter the file i get

644 permission

or some files

777

766

755

666

but the 644 i cant change... why does transmission do it? or is there a work around other then the new permissions? but is there a variable i need to add.. this is been going on for serveral years i just keep doing new permissions but its getting dumb i gotta do it... is there something i need to alter? so it works fine everytime and not when it decides to do... frig who knows if its when transmission updates...

is there a work around or reason why transmission even though its 99 100 uid pig and the umask is 022 that sometimes transmission cant move files off the download drive to the array permission denied or when it does i loose right to alter the file i get

644 permission

or some files

777

766

755

666

but the 644 i cant change... why does transmission do it? or is there a work around other then the new permissions? but is there a variable i need to add.. this is been going on for serveral years i just keep doing new permissions but its getting dumb i gotta do it... is there something i need to alter? so it works fine everytime and not when it decides to do... frig who knows if its when transmission updates...

Transmission has been chaotic for me last couple of weeks. It went into orphan when adding new share, and I had to re-install it.
After that everything creates with wrong permissions:

Folders: drwxr-xr-x
Files: -rw-r--r--

Changing umask in /mnt/user/appdata/transmission/settings.json didn't affect it.

Found you can change umask in "Update Container". Changed it to 000, I stopped being able to connect to transmission.
Changed it to 001. All torrents updated to same "added on" timestamp and and get stuck in status "Queued" and set the download directory to /root/download/ ...wft.

It's all totally broken. By stuff like umask that shouldn't affect anything at all.

edit:
It also can't download anymore after correcting umask. It keeps downloading at full speed but doesn't write anything to disk, it seems to download and send it into nothingness. With umask 010.


it starts to download again if I change back to umask 022. But...with the wrong permissions (the umask 022 permissions above where only server root can change the files)

Edited June 3Jun 3 by tshorts

@tshorts

whats working for me for now anyways is

i stopped transmission

i edited the settings file and changed umask from 022 to 000

i ran Tools/New Permissions on the drive or location of the transmission incomplete files

let it finish then run transmission and that seems to be working

now that worked for me i not sure if works for you but if you try it in that order maybe it works for ya

and time will tell if i get that 644 permission but stay at 666

Edited June 4Jun 4 by comet424

2 hours ago, comet424 said:

@tshorts

whats working for me for now anyways is

i stopped transmission

i edited the settings file and changed umask from 022 to 000

i ran Tools/New Permissions on the drive or location of the transmission incomplete files

let it finish then run transmission and that seems to be working

now that worked for me i not sure if works for you but if you try it in that order maybe it works for ya

and time will tell if i get that 644 permission but stay at 666

You only edited settings.json and not the UMASK variable in the container settings?

Weird, changing settings.json did nothing for me. Can you check what UMASK is set under your transmission container settings (it's under "Show more settings")?

edit: BTW, it didn't crash by changing container settings to 000 after I updated transmission to latest transmission version that came today or yesterday. So all good in the hood now!

Edited June 4Jun 4 by tshorts

@tshorts

i dont have a umask in the container maybe cuz i installed transmission like 5 6 years ago i only have UID GID so the 99 100

so i edited the transmission settings json and changed the umask in there so back then no umask in the container

12 minutes ago, comet424 said:

@tshorts

i dont have a umask in the container maybe cuz i installed transmission like 5 6 years ago i only have UID GID so the 99 100

so i edited the transmission settings json and changed the umask in there so back then no umask in the container

Looks like we're not using the same container.
Repository for mine is: lscr.io/linuxserver/transmission

You can try "Add another Path, Port, Variable, Label or Device"
Config Type: Variable
Name: UMASK

Key: UMASK

Value: 000

@tshorts my repository is

linuxserver/transmission

you can try my setup minus the extra completed folder locations i made them 5 6 years ago or longer when i was learning transmission and the downlload location stuff

Edited June 5Jun 5 by comet424