Transmission

From what I have learnt in these months the "could not connect to tracker" message does not prevent the torrent from downloading: I guess that when T. cannot get peers from trackers it starts a DHT session to fetch some. A definitive proof of this behaviour would be: 1) when T. is in a &qu...

Mattneub: does it happen on udp trackers only? Or even with th http ones?
Can you restart transmission and copy here the first 20 lines of the log?
(set it on "information" before )

instead of deleting .plist file could you try just changing the port in the settings and restart transmission?

I perfectly understand your problem: even my Transmission sometime connects to http tracker with no problem but fails on udp.. I ask you 2 things: - do you have a mac? - can you post the first entries of the transmission logs upon startup? IE: I have set the log level to "Debug", here's wh...

I always had the same problem. It is a problem with Transmission. Firewall has nothing to do with it; just use uTorrent with the same port and you can verify that it will connect without any issues. This is UDP-specific. If another tracker is added with a HTTP protocol, it will work, even when the ...

Never heard of IATP-highPri, I doubt it is ever used on my mac except by transmission..
Anyway I will try sticking to a higher port (let's say 50000) and see if the problem occurs again..

Lion firewall with the default settings and Transmission is already allowed to transmit. I tried disabling it, nothing changes.. Okay, so you don't use PG2, L'il Snitch, Norton Firewall, or the like? I wonder about your ISP? No other firewalls; the situation is the same with or without Lion builtin...

Seems like 2 issues. • Unresponsive trackers which use Port 80 from your example and which may be normal or temporary. I thought so but the unresponsiveness of the trackers only verify when following the procedure in my second post. ie: if I follow that procedure the tracker are NEVER responding, i...

I managed to isolate the problem: 1) put some torrent running 2) change port in preferences 3) quit transmission without stopping downloads 4) reopen transmission: - the "Couldn't bind IPv4 socket" message will appear - now the torrents do not connect to trackers 5) choose a random port 5a...

Hello, I have a recurring problem with transmission. I am using version 2.50 (13236). Sometimes when I add some new torrent to download, transmission seems not to be able to start them becouse it gets tracker errors. For example, using a torrent of a popular tv shows that uses: udp://tracker.example...

for two reason: 1) I usually download torrents with the external drive disconnected, when I get home I move it to the drive. 2) Sometime, for very large files, moving causes the download to stop and/or Transmission to freeze (I'm talking about quite large torrent ~5/10 GB) plus, sometime I simply mo...

Is it possible to change the behaviour of the "Move data file to.." function in Transmission? Scenario: I download a very large file on my local hdd. Then I usually move it to an external hard drive but I would like to keep seeding when the external drive is connected. Present interface: -...