Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Transmission problem, can't see files downloaded via Transmission in Windows

Featured Replies

I've setup Transmission on Unraid and it seems to be running fine without any dramas.  I can download torrents and seed them, however I am unable to see any torrents when I browse to my share via Windows.  I have confirmed through command line that the files are in fact there and the files are seeding. 

 

Is there something simple which I'm missing in order to make the files visible.

 

I would be greatful if someone could point me in the right direction.

 

Thanks in advance.

what version of unRAID are you running, what does the settings.json file look like, and what does an ls -al on the files downloaded return.

Not a solution to why they appear to be hidden, but have you tried to view hidden files option in windows?  Normally under folder options.

Check the file permissions of the downloaded files.  (ls -all as prostuff mentioned).  I was having some permissions issues the other day and noticed that files with certain permission levels were not visible when viewed from certain OSes and users.  In particular, ensure that the second and third octets (group and other) permission levels have read access.  I suspect Group is only the one that's important, but I didn't test it fully.

 

If the permissions look something like:

-rwx-------------

then chime back in.

  • Author

Ok I'm running Unraid 4.7, this is the my setting file:

 

    "alt-speed-down": 50,

    "alt-speed-enabled": false,

    "alt-speed-time-begin": 540,

    "alt-speed-time-day": 127,

    "alt-speed-time-enabled": false,

    "alt-speed-time-end": 1020,

    "alt-speed-up": 50,

    "bind-address-ipv4": "0.0.0.0",

    "bind-address-ipv6": "::",

    "blocklist-enabled": false,

    "dht-enabled": true,

    "download-dir": "/Storage/Downloads",

    "encryption": 1,

    "incomplete-dir": "/Storage/Downloads/Incomplete",

    "incomplete-dir-enabled": true,

    "lazy-bitfield-enabled": true,

    "lpd-enabled": false,

    "message-level": 2,

    "open-file-limit": 32,

    "peer-limit-global": 240,

    "peer-limit-per-torrent": 60,

    "peer-port": 51413,

    "peer-port-random-high": 65535,

    "peer-port-random-low": 49152,

    "peer-port-random-on-start": false,

    "peer-socket-tos": 0,

    "pex-enabled": true,

    "port-forwarding-enabled": true,

    "preallocation": 1,

    "proxy": "",

    "proxy-auth-enabled": false,

    "proxy-auth-password": "",

    "proxy-auth-username": "",

    "proxy-enabled": false,

    "proxy-port": 80,

    "proxy-type": 0,

    "ratio-limit": 2.0000,

    "ratio-limit-enabled": false,

    "rename-partial-files": true,

    "rpc-authentication-required": false,

    "rpc-bind-address": "0.0.0.0",

    "rpc-enabled": true,

    "rpc-password": "{384c1f08c332f1fb028baf3178049a25a74731f7zC2ufQ5R",

    "rpc-port": 9091,

    "rpc-username": "",

    "rpc-whitelist": "127.0.0.1, 192.168.0.2",

    "rpc-whitelist-enabled": true,

    "script-torrent-done-enabled": false,

    "script-torrent-done-filename": "",

    "speed-limit-down": 100,

    "speed-limit-down-enabled": false,

    "speed-limit-up": 100,

    "speed-limit-up-enabled": false,

    "start-added-torrents": true,

    "trash-original-torrent-files": false,

    "umask": 18,

    "upload-slots-per-torrent": 14

 

and as for file permissions, I've checked the folder and parent folder permissions as well as the file which was downloaded the permissions are drwxrwxrwx and rwxrwxrwx respectively.  I've tried mucking around with the file permissions from the command line to no avail and set the permissions to 666 and 777 for both file and folder but this didn't seem to fix the issue.

 

Interestingly enough however, when I access file browser from Unmenu and look at the folder permissions under the mode catgegory it shows permissions for the parent folder of drwx--x--x.  I wonder if this is potentially causing the issue or if the permissions are somehow not being updated correctly even though if I do a "ls -l" from the command line it displays the permissions correctly.

 

 

so is /Storage a drive you have set up yourself outside of the array?

 

You probably should visit the Transmission thread and download the newest package I put up.  It looks like you are running an older version of the package which has a lot of stuff being saved to the flash drive... this is not a great thing to do as it will cause the flash drive to were out much faster.

 

 

It appears someone else has a problem with this, too:

 

http://mybookworld.wikidot.com/forum/t-176898/what-umask-to-use-with-transmission-to-have-proper-samba-acc

 

umask=18 is the value by default, and the user in the above thread says they were unable to access files over Samba, also.

 

They claimed changing it to umask=0 corrects it.

 

Yeah, check this out:

 

https://trac.transmissionbt.com/wiki/EditConfigFiles

 

umask: Number (default = 18) Sets transmission's file mode creation mask. See  the umask(2) manpage for more information. Users who want their saved torrents to be world-writable may want to set this value to 0. Bear in mind that the json markup language only accepts numbers in base 10, so the standard umask(2) octal notation "022" is written in settings.json as 18.

 

For octal 666, use 438 in the settings.json.

Your problem is the way samba is mapping the file permissions to windows file attributes.  Background is available here.

 

The solution is to change your file's permissions to 700 (rwx------) and directories to 711 (rwx--x--x).  Some people prefer to change Samba's behavior to not map file permissions to Windows attributes, but IMO that is treating the symptom, not solving the problem ;) If you want to go that route, you can search the forum and find the info, I don't remember the setting off the top of my head.

 

For existing files/directories you can use the following from the command line to fix the permissions:

for files:

find /path/to/affected/files/ -type f -exec chmod 700 {} +

for dirs:

find /path/to/affected/files/ -type d -exec chmod 711 {} +

 

just replace the /path/to/affected/files/ with the correct path.

 

It sounds like defected07 has the correct solution going forward in changing the umask that transmission uses, however I would set it to 0077 not 0000.  Setting it to 0000 effectively sets new files to 777 which is what they are now...

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.