DSM-G600, DNS-3xx and NSA-220 Hack Forum

indiematt wrote:

I still have Clutch installed on my DNS-323 from an older incarnation of transmission. While it seems to work fine with 1.73, I'd really like to get with the times and use transmission's native web interface. What is the best way for me to drop Clutch and make this transition? FYI: I'm running funplug .05 on a DNS323 and the latest 1.08 beta firmware.

Thanks!

Since Clutch has been integrated into Transmission, you can simply acccess it by directing your browser to http://<ip of your nas>:9091
The interface should appear.
Via command-line you can change the port on which the interface can be reached, and you can also set a login and password.

Lighttpd is not needed anymore, since Transmission basically brings its own (tiny) web server.

Please please please help!!
I decided to completely format and reinstall ffp because i just could not seem to get transmission working before. This time around i've gotten much further. Now when i go to http://192.168.1.101:9091 i get the following:

403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

So i looked at my settings.json and this is what i have:

{
    "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": "\/\/Downloads",
    "encryption": 1,
    "lazy-bitfield-enabled": true,
    "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,
    "rpc-authentication-required": true,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-password": "{deleted_stuff",
    "rpc-port": 9091,
    "rpc-username": "moebius",
    "rpc-whitelist": "192.168.1.101","192.168.1.1","127.0.0.1"
    "rpc-whitelist-enabled": true,
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 100,
    "speed-limit-up-enabled": false,
    "umask": 18,
    "upload-slots-per-torrent": 14
}

I tried changing the rpc-whitelist-enabled to "false" and it didn't help.
Please help me. I've been fighting with this for WEEKS!

Last edited by moebius (2009-08-21 06:22:38)

KyleK wrote:

Do you have the latest version of Transmission? Also make sure to use the latest version of the web interface (which comes with Transmission). The web UI requires Javascript to be active in your browser.

I have the latest Transmission. What is Automatic? Do i need that?

Apparently the "beta test" went well, because now v1.74 stable is available.

Link is in the first post.

OK, I'm stumped. I removed v1.52, and have installed 1.74. I'm pretty sure that I have everything configured again, all permissions are set to nobody, and directories to 777.

When running through the web interface, the downloads start, connect, and find peers. I then get an error, "no such file or directory (/home/nobody/downloads/filename).

The thing is I have my directory set to "download-dir": "\/mnt\/HD_a2\/downloads\/",  in settings.json, and that shows up in the web interface preferences as /mnt/HD_a2/downloads/.

My rpc whitelist is: "rpc-whitelist": "127.0.0.1, 192.168.*.*", so I think that's ok.

I've even deleted the whole transmission-daemon directory and had it recreated on startup.

Any ideas?

thanks, Jim

Any ideas?

Somehow Transmission became banned on one of my Trackers, specifically Build 8992-8996, but
8998, 9007 and 9009 aren't, any chance to get a newer built?

:edit:
Talked to Tracker-staff, unbanned it till further tests.

Last edited by NASewise (2009-08-30 18:10:39)

SkyNet wrote:

Just upgraded to 1.74. It seems to be faster than 1.73 and works like a charm.
I have a (small) problem as it seems.
Before upgrading I changed ownership of the torrents dir to nobody.
I then installed the 1.74 and after that I launched the Transmission WEB GUI.
In the Web Gui all the torrents which were / are seeded now are marked with a red upload arrow (except 1 or 2) but they seem to seed normally.
Any idea what this means and how to resolve it?

There's a red upload arrow in the web GUI? Where? :)

Anyway. It could mean that the tracker is currently down, but seeding still works because of peer exchange and/or DHT. I noticed that a lot of torrents stopped properly working in the last couple of days, most likely because of the TPB switchover.

Maybe the trackers block you for some reason or other? If they're private, they may ban certain versions of Transmission. (Or maybe they have a whitelist of allowed clients, and Transmission 1.74 isn't on there yet).


You could check if there's something of help in the logfile. It sits (by default) at /mnt/HD_a2/.transmission-daemon/transmission-daemon.log.

If there's nothing specific in there, you could raise the log level.

There's 2 ways to do this:

First method
 - Quit Transmission (wait a while, it takes some time to shut down)
 - Open /mnt/HD_a2/.transmission-daemon/settings.json
 - Change the setting "message-level" to 4
 - Restart Transmission

If you still can't see anything particular now, you can enable debug logging. Please note that this produces a MASSIVE amount of log messages, so you should only run T for a couple of minutes with it enabled.

Second method
 - Quit Transimssion
 - type "export TR_DEBUG=1"
 - type "export TR_DEBUG_FD=1"
 - Restart Transmission

To disable debug logging:

 - Quit Transmission
 - type "unset TR_DEBUG"
 - type "unset TR_DEBUG_FD"
 - Restart Transmission

Sorry maybe I was not clear.
I am indeed talking about the Transmission Remote GUI.
Does anyone have similar problem?

As i wrote, I have the same "problem"
just ignore it and wait for an update or use Transmission Remote dotnet from here

:edit: waited too long to click on submit...

Last edited by NASewise (2009-08-30 21:21:52)

Hi KyleK,

I installed Transmission 1.74 two days ago and it working fine until this morning. I just notice that it was down, i tried to start but when i connect thru web browser it seems  that it was not responding. I tried to stop it also and nothing happens.  i use this command to stop transmission "killall -9 transmission-daemon". I also tried to reinstall but still no luck. Can you help me?

It's working now. Thanks! But before when i tried "transmission-remote -l" it returns couldn't connect to server. I haven't tried 'top' before when the problem occurred but when i tried it now the %MEM is 29%. I only load 3 downloading torrents and 14 seeding. Is 29% of %MEM normal?