New Transmission add-on thread

I'm using the latest version of Transmission on a ReadyNAS NV+ and it seems that it doesn't manage to communicate with trackers whose URLs start with udp://. Anyone else having this problem?

Seraph wrote:
I'm using the latest version of Transmission on a ReadyNAS NV+ and it seems that it doesn't manage to communicate with trackers whose URLs start with udp://. Anyone else having this problem?

Having the same problem, UDP should work but doesn't... :(

Seraph wrote:
I'm using the latest version of Transmission on a ReadyNAS NV+ and it seems that it doesn't manage to communicate with trackers whose URLs start with udp://. Anyone else having this problem?

Seems similar to the trouble I'm having with Transmission on a ReadyNAS Duo

viewtopic.php?f=36&t=57240

UDP torrents seems to lock up Transmission and make the interface (via Web or Transmission UI) unable to connect to the daemon, but I'm not sure if Transmission is actually doing any real work.

Having big problems with latest Transmission 2.34 beta 04 on my ReadyNAS Duo with 4.1.8.

I can get everything up and running, and I can start downloads without problems. But as soon as the first torrent is finished downloading Transmission crashes and I have to log in to Frontview and restart it. Only today I've had to restart it 5-6 times already and that's only with a total of 3 torrents being downloaded/seeded...

Is this on the radar already and worked on?

Similar issues here. Got them with 2.31 so am on the 2.34 beta now Transmission keeps stopping. Sometimes the processes are still running on the NAS and sometimes not - but when it dies I can't connect via either web or Transmission remote.
Status of torrents is now reported as 'unknown' - even after a 'check'. Download speed is erratic now and often drops to zero for minutes at a time.
Never gets much above 1MB/s download speed but on the PC it goes to straight to 3.5-3.6MB/s within about 10 seconds using utorrent (but sadly I've always had that issue. :( )
Have never had these stopping issues before when on 2.11. May try going back to that.

Could have done something stupid but just installed Transmission on my NVX and it has trashed my Media shared folder (sort of).

DLNA shares are still showing everything that's in the Media folder but browsing to the Windows share shows an empty Media share..

I have had a quick look through the forum to find a fix but there are so many Transminssion threads it's a bit tricky to find. Happy to resolve myself if someone can point out the right thread..

Oke, i am banging my head, crying my eyes out and so on. Shortly: i am lost.
I have the readynas ultra 6, raider 4.2.19 in combination with macbook air.

I fresly installed the add-on transmission, did the update and now i want to use the version 2.40.02.
I did not change any settings, just tried to start a download. I go to transmission via raid-ar>add-on>transmission interface.
I opened a torrentfile, and then after a while (this differs from time to time and can be after completing 5,7,21,53,72%)i get the error: permission denied

After pressing resume, i get another error: Error: No Data found! Ensure your drives are connected or use "Set Location". To re-download, remove the torrent and re-add it.

I have read a lot of posts on the permission denied problem but none solved my problem. I do not know what is wrong, can someone please help me?

First thing I'd check is if you've enabled ssh access connect to the system use "ps -ef | grep transmission" to see who the process is running as (should be user nobody). Then go to /c/media/BitTorrent and make sure that user has full access to that directory and all of it's subdirectories. Something tells me I had the same issue after I installed it and fixed it this way.

I'm running into an issue installing 2.40.03 - I had 2.40.02 installed, and attempted the auto-update, but when it completed, it said that I was still running 2.40.02, and an update was available. Also, once the update was complete, the service would not start.

I wasn't able to do the update despite several attempts, so I went back and downloaded 2.34.04, and installed it from the BIN file - it installed fine, and listed. 2.40.03 as being available. I tried to update again, and it did... and the installed version was listed as 2.40.02, with an update (2.40.03) being available. It looks like the version number may be wrong in the new update?

Reverted back to 2.11 and all my problems are gone. I'm officially never updating Transmission again!