Closed GoogleCodeExporter closed 9 years ago
"CORRECTION" :
2. Add a new torrent file in transmission remote located in a server,
with THE TORRENT which has been saved on the local machine
It would be very useful to have the possibility in the next version to change
the
passkey by adding a new tracker url for the torrents or change the the current
one.
Original comment by sai...@free.fr
on 20 Oct 2009 at 10:56
I use a number of passkey trackers and have never had any issue with using their
torrents using transmission-remote-dotnet. Really, all
transmission-remote-dotnet is
doing is passing the torrent to transmission-daemon, so if there's a valid
passkey in
the announce URL there shouldn't be a problem.
There could be a number of reasons that the tracker is refusing your passkey.
Perhaps
there's issues on that site, or maybe transmission but I think that's unlikely.
Have a look if the passkeys match in the trackers tab in this application and a
local
client like uTorrent.
Original comment by AlanF...@googlemail.com
on 8 Nov 2009 at 10:49
Original issue reported on code.google.com by
sai...@free.fr
on 18 Oct 2009 at 10:08