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

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!

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.

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

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!

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))

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

dudeishere wrote:
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:

Look in settings.json for ""port-forwarding-enabled":" and make sure it says "true" as argument. Then log on to your D-link router and make sure uPnP is enabled, it's under advanced network settings. If your running a old enough Firmware, your not going to have that setting, and will need to update first, then it will be supported. After that, you should be able to ignore it, more or less. It should always just work.

Now that i sort of fixed your issue, or, well, hopefully at least, here comes the kicker.
If, for what ever reason, the router / firewall whatever thats in between the ReadyNAS with Transmission, and the rest of the world is restarted, Transmission doesn't seam to notice that the uPnP port forwarding no longer works, and you go deaf. From what i see, it looks like new torrents will set up new forwarding, but the old stuff remains broken. Restarting the NAS will fix the issue. I assume this is something it inherits from the Transmission code it self, and that it has nothing to do with the ReadyNAS adaptation. But i thought i should put it out there. Might simply be my Firewall that is overly anal as well. (Smoothwall SWE3.0)
B!

Sorry for the noob question but I am having some issues. I got Transmission 2.82 installed and it looks like it is running but when I use Transmission Remote GUI to start a download, I get an error about tracker connection failed. I don't know if there are some settings I need to make on router or what because torch works fine on laptop. Currently running dd-wrt ver 24 sp 2. Let me know how to post screenshots or any other information you might need

My old ReadyNAS DUO SPARC has decided to update itself to 4.1.3 and Transmission stopped working. I restarted, removed Transmission, reinstalled 2.82, started the service.
The daemons seem to be running fine, the service appears in the addons menu and I can start and stop it.
However the link to the UI just goes to a "blank" page. Looks like the WebUI isn't available via Apache.
Any ideas?
Thanks

By default the web ui is available at port 9091 of your NAS (ie. http://a.b.c.d:9091/transmission/web/)

If it's not coming up, try reloading/refreshing the web page or try with another browser.

If it still doesn't work try rebooting the NAS.