Closed GoogleCodeExporter closed 9 years ago
Hi, same problem here.
TRG 1.3.2 + Transmission 1.91
Original comment by boguslaw...@gmail.com
on 10 Mar 2010 at 12:02
I switched back to Tr 1.76 for now. I had some performance and stability issues
on my
NMT, I suspect the new transmission.
Original comment by jude...@gmail.com
on 10 Mar 2010 at 1:31
Had the same problem with TRG 1.3.2 + Transmission 1.91. Restarting the
transmission
daemon solved the problem.
Original comment by martverm...@gmail.com
on 12 Mar 2010 at 12:34
If TRGUI shows that the "tracker did not respond" - go to the web interface
Transmission and look - all in order. It seems that TRGUI can not determine
retracker
and reports an error ...
Original comment by vladimir...@gmail.com
on 12 Mar 2010 at 3:45
Could you please raise priority for this to High, as many people are impacted
by this.
Original comment by rlav...@gmail.com
on 18 Mar 2010 at 5:24
TrGUI 1.3.2 & w/ Transmission 1.92 (91,90)
same problem as described above, and one more - many that error:
Tracker: tracker gave HTTP Response Code 502 (Bad Gateway)
In web interface and transmission-remote - all ok.
Daemon restart solve this for not long time.
Original comment by z...@yopmail.com
on 20 Mar 2010 at 7:25
Have the same problems, 502 also.
TrGUI 1.3.2, Windows 7, Transmission-daemon 1.91
Original comment by liquidbl...@gmail.com
on 14 Apr 2010 at 4:57
Same prob reports #202 and #206.
Original comment by leshekb
on 24 Apr 2010 at 8:38
Should be fixed by r250 and r252.
Original comment by j...@cp-lab.com
on 30 Apr 2010 at 3:56
Original comment by j...@cp-lab.com
on 30 Apr 2010 at 3:56
trGUI 1.93 get the same problem here.
Original comment by shawn.zh...@gmail.com
on 6 Oct 2011 at 8:37
Original issue reported on code.google.com by
jude...@gmail.com
on 24 Feb 2010 at 3:28