Transmission add-on thread before MAY 2K10

[super-poussin]

Just installed Transmission 1.74.

Installation appeard to have deleted all existing folders on my Media share (Photos, videos, etc) - Now only one folder - BitTorrent

Space available on the disks still appears as if the folders still exist.

Your urgent help would be appreciated.

Thanks,

Doug

Pls excuse for posting in more than one thread.

take a look here : viewtopic.php?f=36&t=32865&start=0

[hawkeypunk]

The torrents I have downloaded using 1.61 are set to read-only. How do I prevent this from happening. I have downloaded the latest version and thought this problem had been fixed.

Also, how can I change the permissions on the files I have already downloaded so I can move/delete them? It will not allow me to change the permissions. I would really like to delete some of these files as they are occupying a lot of disk space.

Bump to this... did anyone find a solution to this problem? I just updated to v1.74 and the same thing is happening to me. I'm using a Mac (OS X 10.5.8; not Snow Leopard), and when I check the Sharing & Permissions settings for new torrents I've downloaded since updating to 1.74, this is what I see:

Code: Select all

You have custom access

NAME                 PRIVILEGE
nobody               Read only
nogroup              Read only
everyone             Read only

I try to change these settings, but it doesn't stick. The rest of the torrent download files that started before updating to 1.74 have Read & Write as the privilege for all users and groups, which is the default for the share. Is there another way to change these settings? How do I update the downloading settings to ensure that everything saves with Read & Write permissions?

Thanks much for your help!

[skyn3t]

Yes, in Transmission 1.74 for SPARC is an error in the permissions for the files.

When I want to delete a file from a downloaded torrent the file is not accessible.

Didn't have this issue in the before used version 1.72 (I never used 1.73).

But you can "repair" it for the downloaded torrents to access them:

(Sorry, I use the german GUI and dont know the exactly english labels of the GUI)

1. Start the ReadyNAS GUI
2. Goto "Share Overview"
3. Then click the "CIFS" options of the "media" share (that is the default for transmission)
4. Then click "Advanced Options"
5. Now mark the checkbox where all permissions set to the above named rights (in the german GUI the first checkbox from top)
6. Apply.
7. After a while you get a system notice that all rights were set

After that, you have access to files .

[Blues]

This permissions issue has appeared before and then super-poussin fixed it. I know that 1.72 did not have this issue, but 1.73 does. I've not tried 1.74 yet, but it sounds like it's there too.

The solution that skyn3t proposes works fine. If you know a little about the command line and can ssh as root to the directory where the files are, you can use the chmod or chown commands to change the permissions manually.

It may seem daunting and the possibility exists that if you enter other commands you can screw things up. However, chmod with permissions set at something like 775 for the file(s) in question will do the trick and may take less time than using the Permissions in the Advanced Options.

Either way, it will not prevent you from having to do it again when you receive a new file.

Perhaps super-poussin will change this in a new release.

[super-poussin]

what it the value of umask in settings.json ?

[skyn3t]

what it the value of umask in settings.json ?

In transmission v 1.74 for SPARC it is:

"umask": 18

[super-poussin]

When it's a fresh install I set it to 0

but when it's an upgrade I did not touche the value

stop transmission and set umask to 0

[hawkeypunk]

1. Start the ReadyNAS GUI
2. Goto "Share Overview"
3. Then click the "CIFS" options of the "media" share (that is the default for transmission)
4. Then click "Advanced Options"
5. Now mark the checkbox where all permissions set to the above named rights (in the german GUI the first checkbox from top)
6. Apply.
7. After a while you get a system notice that all rights were set

After that, you have access to files .

stop transmission and set umask to 0

Both of these fixes worked! Thanks skyn3t and super-poussin!

[super-poussin]

Hello guys,

I have been using Transmission for few days, happy with the experience, nice work super-poussin, thank you!
The only problem to me is I had a few dodgy torrents They stop occasionally by telling me 'Tracker returned an error : Requested download is not authorised for use with this tracker', I know its something to do with the tracker side not transmission...
Keep restarting and eventually I had them downloaded without problem. So is there any way to let transmission auto-restart/retry failed tasks? Keep checking the transmission ui few times a day to make sure torrents are running fine is a little annoying

Any advise is appreciated. Thank you

1.75 beta 2 should solve this , let me compile it and test

[super-poussin]

1.75b02 fo sparc

1.75b02 fo x86

[skyn3t]

When it's a fresh install I set it to 0

but when it's an upgrade I did not touche the value

stop transmission and set umask to 0

Sorry, could test it not before today.

With setting umask to 0 its working! Thanks

[Omez]

Hi,

I tried to search for it but didnt get any hits, so if this is covered before Im sorry.

The case is with private trackers.
I get the error "Tracker Returned an error: Invalid passkey! re-download the torrent"
I have the newest version of Transmission on a NV+ readynas.

This is for all private trackers as far as I can see.

The exact same torrents works on any local installation of torrent clients (utorrent, bittorrent, azureus)
The NAS and computer is on the same local net. only difference is the local IP.

Any tips ?

[a10thunder]

I just got my Duo and I am enjoying the Transmission add-on. I'm having trouble setting up transmission-remote-dotnet 3.11. I have turned off HTTP access on the Duo.

Does HTTP have to be on and with authentication turned off in order to run transmission-remote-dotnet?

Do I have to port forward 8181?

Host: [My IP]
Port: 8181
Secure (SSL): checked
User: Admin
Password: password1

[super-poussin]

can you try admin not Admin ?

[a10thunder]

I guess my question is if it's possible to set up Transmission Remote for access outside my LAN. Do I need to set up some kind of proxy for access outside my home network?

Host: [My IP]
Port: 8181
Secure (SSL): checked
User: admin
Password: password1