New Transmission add-on thread

Deaf_Raiders wrote:
Does transmission 2.42 definitely not work on 4.1.9 Duo v1

On my duo V1 :
transmission 2.42 wasn't stable at all with RAIDiator 4.1.9

Since i have change cache-size-mb from 200 to 2 in settings.json ; it works perfectly :lol:

I can't even upload mines!!

Hi there,
Thought I'd post in the dedicated Transmission thread.
Basically Ive just changed internet providers and Im setting up the passthrough's on my new router's firewall. I can see Transmission from inside and outside my firewall, but I can only upload torrents if I have first downloaded the file first, e.g. pasting the URL to the public torrent doesn't add anything.
Im thinking I need to open a port or something on my firewall as it worked with my previous provider so I must have opened something up on the old router, but can't see what Im missing. :(

Any suggestions (other than switching back to the old provider lol) are very welcome!

Thanks
John

Hairy wrote:

Hi there, Thought I'd post in the dedicated Transmission thread. Basically Ive just changed internet providers and Im setting up the passthrough's on my new router's firewall. I can see Transmission from inside and outside my firewall, but I can only upload torrents if I have first downloaded the file first, e.g. pasting the URL to the public torrent doesn't add anything. Im thinking I need to open a port or something on my firewall as it worked with my previous provider so I must have opened something up on the old router, but can't see what Im missing. :( Any suggestions (other than switching back to the old provider lol) are very welcome! Thanks John

It not a provider issue. It a setting issue nobody has a solution for it yet or not that I know of.

Thanks for the reply, Im a bit stuck.

Do you have the same issue?
Just to clarify I cant upload by url from within or from outside my firewall, but I can upload by file.

Had a thought, I'll temorarily disable the firewall completely and see if it then works, if it doesn't its nothing to do with the firewall. If it does I could try to isolate port ranges. Fun fun FUN! :wink:

Cheers
John

I have an issue Downgrading my firmware.

Hello all,

I am totally brand new to the ReadyNas and just purchased a Duo V2, with the latest firmware.
I've managed to install Transmission and got it working for downloading torrents.

I wanted to get some advice for optimising the use of Transmission. How do I get faster downloads - do I need to set up port-forwarding on my router? Looking on the router page, Transmission has automatically created port-forward setting at a different IP address to the NASdrive. Also, in the Transmission setting it states that the corresponding port no. is CLOSED, is that what it's meant to be?

At the moment download speeds are quite slow, much slower than when using BitComet on the laptop!
Any advice would be much welcome - thanks for your time and patience!

If the IP address that has been reserved by Transmission is wrong, the upnp service of your NAS might be confusing the network interfaces. I've got no idea how you can solve this in a nice way. However, there is an option in Transmission to disable port-forwarding using upnp, I think the option is called "use port-forwarding from my router" in the preferences window (though it might be named differently in the Kettu interface). Turn this option off and then manually forward the port in your router to the right IP address.

Guys.

I'm on a ReadyNAS Duo (1). Updated Radiator to 4.1.9.
Had Transmission 2.42 installed (Working, but with the occasional spontaneous shutdown).
Wanted to change some settings in the json file now. But I can't stop the service. When I click Stop, it immediately pops up Transmission Service Stopped. But it didnt stop. If I refresh the page the light's still green, and it's still available on port 8181.
Tried to Remove the addon. It does the same thing. Immediately pops up "Uninstalled successfully". But when I reaload it's still there. Running.

Tried to install v2.22. Installs successfully, but the same problems remain.

Any pointers?

Turned out that I had to close Internet Explorer in between start-stopping the service. I think it had something to do with cookies.
When I close the browser in between I can start, stop or remove transmission just fine.

Changed the cache size to 2 in stead of 200 in the settings.json file which seems to have fixed the crashing of transmission.