New Transmission add-on thread

[absincog]

Thanks for the suggestion. I have uninstalled and reinstalled the add-on multiple times and I've also tried to enable it several times in succession. I want to avoid a factory reset - too much data to restore. I read somewhere that reinstalling the NAS firmware may correct the problem, so will try that.

[Mr_B]

Good luck. I'm having a similar issue, and like you, i'm not that hot on the idea of a factory reset, but the firmware updating thingy didn't do it for me, sadly.

Best of luck tho.
B!

[absincog]

Yes - especially since I had just done a factory reset and installed Transmission on top of a "vanilla" firmware install. I've since restored my data to the NVX and don't want to go through the process again...

Good luck

[absincog]

I reinstalled the NVX firmware - still no luck.

[Andreas75k]

For me nothing after transmission 2.11 works, but that version works fine. Same with firmware 4.1.9 on my duo (sparc).

[absincog]

Andreas75k - thanks, your post got me experimenting. I installed 2.11 and it worked. So I upgraded to 2.13 and it worked, as did 2.22. Beyond 2.22 though I get the dreaded, "Transmission service failed to start" message. I tried 2.32, 2.33, 2.52, 2.60.

Maybe that will give the community some clues...

[absincog]

I got version 2.60 working again. After installing v2.22 I disabled the add-on throughout Frontview and made the following updates to the settings.json file:
- set "download-dir" to a share/folder that exists on my NVX (I had removed the 'media' share, which didn't seem to impact earlier versions of the add-on)
- set "incomplete-dir" to a share/folder that exists on my NVX (again, the default involves the 'media' share)
- set "incomplete-dir-enabled" to false (not sure this is necessary but I'm ok with partials in the same directory as completed downloads)
- set "watch-dir" to a share/folder that exists on my NVX (same explanation as above)
- set "watch-dir-enabled" to 0 (I don't create torrents)

After making these changes I re-enabled the add-on to confirm it worked. I then disabled it, installed 2.60 and it worked (was actually enabled when I viewed the 'Installed add-ons' page in Frontview; didn't even need to enable it).

After going through this process, I noticed a few differences when I reviewed the settings.json file of the "working" add-on (don't know which, if any of these are significant):
- "rpc-port" set to 8181 for "working" add-on (was 9090 or some such for the "non-working" add-on)
- "rpc-username" set to 'admin' (was blank)
- "rpc-whitelist" set to * (was 127.0.0.1)

Maybe this will help others with similar issues...

[dCon0ne]

Where Do I find Version 2.60, all I can find is 2.42 for Duo V1 (Sparc)?????

[absincog]

Looks like 2.42 is the latest version for the Duo (Sparc).

[Mr_B]

Latest version is 2.61, however, it's not packaged in a neat "push to NAS" file, and set up for the average user. I couldn't get it running on my NAS even if i wanted, but thats where they get the later versions.
B!

[pugilares]

Is there any other way round the permissions problem then to assign the whole media share to nobody/nogroup? I have media share assigned to an user but within this share I have a folder assigned to nobody/nogroup. Transmission is set to write to this folder and it returns an error message when trying to write to this folder. Is there easy way to run Transmission as a particular user?

[Deaf_Raiders]

Tranmission 2.42 not install on the latest RAIDiator 4.1.9

[Deaf_Raiders]

Tranmission 2.42 not install on the latest RAIDiator 4.1.9. Even tried a different browser

[JarnoG]

Pugilares, have you checked whether all the folders Transmission uses (download, partial files, torrents, etc) have the right permissions?

[pugilares]

It seems that I somehow managed to get it working on my Duo (v1) thanks to the tips above. The only thing was that I don't want my whole media share to be owned by nobody/nogroup. It didn't work with just a specific folder within the media share set to nobody/nogroup (permission denied error). So I had to create separate share dedicated for Transmission downloads, assign it to nobody/nogroup, give proper rights to this share, change setting for incomplete downloads in settings.json and it works fine for few hours now. Thank you guys!

Anyway, it would be nice in the further versions of Transmission to make it possible to set ownership matters somehow other way than just nobody/nogroup.

Cheers!