@jademonkeeit doesn't work for me anymore after adding it SLSKD_VOLATILE: receives a message SQLite Error 1: 'no such table: Transfers'.

23 minutes ago, Kulis said:

@jademonkeeit doesn't work for me anymore after adding it SLSKD_VOLATILE: receives a message SQLite Error 1: 'no such table: Transfers'.

I've just started getting that error, too, but haven't yet tried to solve it

Perhaps try it not in Volatile mode.

The reasoning behind using Volatile mode is here: https://github.com/slskd/slskd/blob/master/docs/known_issues.md#devices-using-a-copy-on-write-filesystem-such-as-btrfs-or-zfs

It may not apply to you.

Also have a look at https://github.com/slskd/slskd/issues/1554

Thank you, but that doesn't solve the problem. You can actually go down a version and use "SLSKD_VOLATILE:".

I read GitHub, and in my opinion, there are questions everywhere about file access rights, chmod 777, and unmask 000, and in Unraid there is a problem with the file owner. In Unraid, it is saved as root and not as nobody.

I checked the docker from binhex-slskd and it seems to not have this problem, but I have a problem setting where the shared media is located. And the weight of the docker is very large compared to the light and official slskd docker.

I used the slskd guides to create the app. I'm happy to adjust the app template if you figure out that there is an issue with it. But I don't see any at the moment. Sorry that I can't help, I am not contributing to slskd - I just made the template.

@manrw I would like to thank you very much. Everything works. I had to add 99:100 in the Extra parameter, and now it saves files correctly as nobody.

17 hours ago, Kulis said:

@manrw I would like to thank you very much. Everything works. I had to add 99:100 in the Extra parameter, and now it saves files correctly as nobody.

That was what I mentioned needed to be done in the original post I linked you to...

18 minutes ago, jademonkee said:

That was what I mentioned needed to be done in the original post I linked you to...

Sorry one other question, i added that and it saves as nobody which is good, but it still saves as "-rw-rw-rw" so i cant read or write it, how do i fix this? It now saves as nobody but i still cant copy the files?

quick edit: i should also note i cant even manually change the perms to read/write for all via the unraid file explorer, it doesnt apply the perms change

second edit: sorry, looking into it more, it seems it does have the right perms for read write, but im still getting file access errors when i attempt to copy it. Unsure what the issue is now....

Edited December 16, 2025Dec 16 by Tpole

On 3/13/2025 at 4:21 PM, jademonkee said:

As per the documentation, I also had to create two variables in the Docker UI:

SLSKD_UMASK with value 000

SLSKD_FILE_PERMISSION_MODE with value 777 (to match Unraid's default perms)

Did you also add these? It's hard for me to diagnose your problem when I don't have a clear understanding of what your settings are.

8 minutes ago, Tpole said:

second edit: sorry, looking into it more, it seems it does have the right perms for read write, but im still getting file access errors when i attempt to copy it. Unsure what the issue is now....

Are you trying to copy from Windows? There's a chance that maybe the paths are too long? I sometimes get weird file errors when renaming files if the directory length is longer than 260 characters.

Just a guess, though, as it's usually reading or renaming those long files that causes those issues, not moving them.

And just to double check: the files are new files (since changing the Docker perms), right? The changed permissions won't be applied retroactively to any files.

If you want to fix any existing files, run the "Docker Safe New Perms" tool under the "Tools" menu in Unraid.

Edited December 16, 2025Dec 16 by jademonkee

4 minutes ago, jademonkee said:

Did you also add these? It's hard for me to diagnose your problem when I don't have a clear understanding of what your settings are.

I havent currently, i'll add these in now.

2 minutes ago, jademonkee said:

Are you trying to copy from Windows? There's a chance that maybe the paths are too long? I sometimes get weird file errors when renaming files if the directory length is longer than 260 characters.

Just a guess, though, as it's usually reading or renaming those long files that causes those issues, not moving them.

Yes windows, i've tried playing with the paths, i THINK i may have susssed the issue, i'm just trying to confirm now. I think the issue is the folder im trying to copy to was created with slskd and had inherited the old no write perms, however after i have changed them manually its still not allowing the copying.

1 minute ago, jademonkee said:

And just to double check: the files are new files (since changing the Docker perms), right? The changed won't be applied retroactively to any files.

If you want to fix any existig files, run the "Docker Safe New Perms" tool under the "Tools" menu in Unraid.

literally running this as we speak trying to confirm the above suspicion.

14 minutes ago, jademonkee said:

Did you also add these? It's hard for me to diagnose your problem when I don't have a clear understanding of what your settings are.

Sorry last one, just because im stil fairly new at tinkering like this, do i add these values like below?

1 minute ago, Tpole said:

Sorry last one, just because im stil fairly new at tinkering like this, do i add these values like below?

I have mine set up like this: (note that those are my own notes under "Description." Though it wouldn't hurt for you to add them, too.

1 minute ago, jademonkee said:

I have mine set up like this: (note that those are my own notes under "Description." Though it wouldn't hurt for you to add them, too.

perfect, ok copied this, i'll let it run for a tad and see if this fixes all my import and access issues! thanks so much for all the help <3