Open GoogleCodeExporter opened 9 years ago
I occasionally have the same problem. The sample "invalid" torrent file is
attached.
Original comment by avsi...@gmail.com
on 18 Jun 2012 at 8:58
Attachments:
I have the same problem.
have read a lot of comments on trackers forums and have no any solution.
OS: Windows 7 x64
Transmission: 2.50
Remote: 3.24
OS: Windows xp x32
Transmission: 2.50
Remote: 3.24
attached torrent file modified to prevent passkey publishing.
Original comment by roman.de...@gmail.com
on 21 Jun 2012 at 4:45
Attachments:
Today I faced the same problem. But after downloaded the source of the project,
and found the source of the problem. It was the creation date. This is a type
of long, but it can't be added to 1970-01-01 cause it's much more bigger than
it can be handled by .net (for addseconds and addmilliseconds too. It was
713341318629574). So in case of this exception I just put the DateTime.Now to
the creationDate. I now it is just a workaround, but maybe a help for the
developers...
Best Regards,
Laca
Original comment by hasa...@gmail.com
on 3 Dec 2012 at 6:04
Szép volt Laca!
It was nice Laca!
Original comment by joco1...@gmail.com
on 3 Dec 2012 at 6:28
i have similar problrm. I used my ASUS router to run transmissions. I could not
open some of the torrent files using the remote interface, it returned an error
saying invalid torrent file. I have no problem opening the torrent using
bitcomet on my PC and start downloading. I also could upload and open the
torrent file using transmission's web interface... seems something wrong with
transmission-remote.
Original comment by kchon...@gmail.com
on 31 Jan 2013 at 7:38
similar (or exactly same) problem. some of the .torrent files cannot be added
to the download list via transmission remote because of "invalid torrent file
specified". This torrents are easily added via web-interface.
transmission v2.82 (14160) on the router zyxel keenetic ultra
transmission remote v3.24 b3 on w7 x64
Original comment by dej...@ngs.ru
on 21 Oct 2014 at 2:18
Original issue reported on code.google.com by
joco1...@gmail.com
on 1 May 2012 at 8:22