New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)

Firstly, my thanks to Tarobun, super-poussin and anyone else involved in keeping the ReadyNAS Transmission effort going! Up until recently I was using the last stable version I found (being 2.11) which worked fine for me.

I recently upgrade my Duo 1 to 4.1.12 and reinstalled everything, and found that Transmission 2.82 is available! Fantastic Ive given it a go and it seems to work perfectly.
Hoever there might be something Im doing wrong, when I modify the whitelist config in any way, Transmission refuses to start. Even setting whitelist to false and the service just refuses to start. Change it back, and it starts fine. In fact it appears that any change I make to settings.json causes transmission to fail on startup. Even restarting the NAS didn't help.

Any ideas on what I might be doing wrong? Im editing the config via my mac using TextEdit. Im reverting the changes I make by editing again in TextEdit. Also all changes are made when transmission is offline, of course.

Thanks
John

i'm in trouble! i have a few problems after upgrading to 2.82 and readynas 4.1.13.

1) I can't seem to get readynas to go through my router. I've open the port on the router (dir-655) I can confirm it is open when i point it to my laptop. I can confirm that the port is open on the readynas (netstat -a | grep 61688) but it always shows as closed on transmission. I don't see any mention on the log (using --logfile) this is what it looks like at startup:

Question: any advice on how I can debug this? I've spent hours on it :'(

bau:/etc/frontview/addons/bin/TRANSMISSION# cat /var/tmp/transmission.log
[19:13:57.025] Transmission 2.82 (14160) started (session.c:738)
[19:13:57.026] RPC Server Adding address to whitelist: * (rpc-server.c:828)
[19:13:57.026] RPC Server Serving RPC and Web requests on port 127.0.0.1:8181/transmission/ (rpc-server.c:1035)
[19:13:57.026] RPC Server Whitelist enabled (rpc-server.c:1039)
[19:13:57.026] RPC Server Password required (rpc-server.c:1042)
[19:13:57.026] Port Forwarding Stopped (port-forwarding.c:183)
[19:13:57.027] DHT Generating new id (tr-dht.c:310)
[19:13:57.027] Using settings from "/c/addons-config/Transmission" (daemon.c:526)
[19:13:57.027] Saved "/c/addons-config/Transmission/settings.json" (variant.c:1217)
[19:13:57.027] transmission-daemon requiring authentication (daemon.c:546)
bau:/etc/frontview/addons/bin/TRANSMISSION# cat /var/tmp/transmission.log
[19:13:57.025] Transmission 2.82 (14160) started (session.c:738)
[19:13:57.026] RPC Server Adding address to whitelist: * (rpc-server.c:828)
[19:13:57.026] RPC Server Serving RPC and Web requests on port 127.0.0.1:8181/transmission/ (rpc-server.c:1035)
[19:13:57.026] RPC Server Whitelist enabled (rpc-server.c:1039)
[19:13:57.026] RPC Server Password required (rpc-server.c:1042)
[19:13:57.026] Port Forwarding Stopped (port-forwarding.c:183)
[19:13:57.027] DHT Generating new id (tr-dht.c:310)
[19:13:57.027] Using settings from "/c/addons-config/Transmission" (daemon.c:526)
[19:13:57.027] Saved "/c/addons-config/Transmission/settings.json" (variant.c:1217)
[19:13:57.027] transmission-daemon requiring authentication (daemon.c:546)

2) are blocklists disabled on 2.82? This is the url I have but it always says there are zero rules, used to work on 2.42

"blocklist-enabled": true,
    "blocklist-url": "http://list.iblocklist.com/?list=bt_level1",
    "cache-size-mb": 200,

I have an NV+ with 1GB of ram, upgraded by removing 2.42, installing 2.82 (thanks for building it!!!) and then moving my settings.json to 2.82. Everything seems to work fine except (1) I can't get through the firewall (2) blocklists don't seem to work (obviously not as important as (1))

Just sticking it in here for reference. Updated the NV+ firmware to 4.1.13, with transmission 2.82 installed. No issues. (So far. Been running for an hour)
B!

Cool. Try setting the port right in chrome, and saving it, then it "should" work from Firefox.
B!

I figured it out (sort of).
It's a browser bug! I'm using Firefox v26.0 (the latest release for OSX). I don't know how to embed an image in this posting, or I'd include a screen shot of what I see. It's similar, but different than your screen shot. For example, the button to donate is a simple text button, labeled "Donate via Paypal". I don't get a spiffy orange Paypal button. I have a button labeled "Create Torrent" that's missing from yours.

Unless I connect to my Duo using Chrome. Then I see what you see. Must be something in the water.

No, it sounds like we are on the same page, but something still isn't the same. Just means i have no idea where the text-box went.

B!

Nope - no text box for the Transmission RPC Port.
On my Duo, the Installed Add-ons page contains a section titled "Transmission. P2P Client". In the upper-right corner is a little green dot (indicating that the add-on is active, I presume).
Below that, it says: Please disable the add-on before modifying the /addons-config/Transmission/transmission-daemon/settings.json file
Below that is a button titled "Transmission Interface", and another button "Create Torrent".
Finally, an invitation to send a donation via PayPal.
Lower-right corner has v2.82.

Perhaps you're referring to another web page?

NAS-t wrote:
Thanks for the pointer to Transmission Remote GUI. I may check it out, but things seem to be working right now, and I'm not sure I want to add yet another layer of new software.

Do IT *tries to sound like Peanut, from/in "Spark of Insanity"* No really. Your just adding a magnet url handler. It pops up like any torrent client, has virtually no CPU usage, since it's not actually DOIN anything, the NAS does it all. And, when you don't use it, you just kill it off, and the NAS doesn't care.

NAS-t wrote:
I tried looking for \\"YourNASHere"\addons-config\Transmission\settings.json Actually, I looked for //nas/addons-config/Transmission, since OS X uses forward-slashes instead of back-slashes. But no such folder is found.

Weird. I'm guessing the share isn't added, or it's shared "as something else". Since my NAS speaks Swedish i can only guess, but i think you need to look under "shares" and see if there is anything there that seams to point at configuration stuffs for the addons.

NAS-t wrote:
You suggested that I put 9091 in the textbox on the web-gui page, and then push Save. Are you referring to the web page on FrontView which lists the Transmission add-on? On my Duo, there's no place to enter a port number.

Wait... What? Right above the "Show Web Interface" button for the Transmission GUI, i have "Transmission RPC Port (from settings.json):" and a text box to enter info in. Thats where you should put 9091. You don't have that text box?
B!

@ Mr_B,
Confirmed - PHP not required. Transmission seems to be running fine right now on my Duo, and I've not installed a PHP package.

Thanks for the pointer to Transmission Remote GUI. I may check it out, but things seem to be working right now, and I'm not sure I want to add yet another layer of new software. Transmission Remote won't help me since it's a Windows program and I have a Mac.

I tried looking for \\"YourNASHere"\addons-config\Transmission\settings.json
Actually, I looked for //nas/addons-config/Transmission, since OS X uses forward-slashes instead of back-slashes. But no such folder is found.

You suggested that I put 9091 in the textbox on the web-gui page, and then push Save. Are you referring to the web page on FrontView which lists the Transmission add-on? On my Duo, there's no place to enter a port number.

Regardless, since I now know how to access the web page (at http://nas:9091), I don't need to go fiddling around with the port number.

Cheers!

NAS-t wrote:
I've discovered that the Transmission Interface for v2.82 can be accessed at http://nas:9091/transmission/web/

Put 9091 in the textbox on the web-gui launch page, and see what that does for you. If it works... Push "save" before closing the page.
B!