last announce = N/A, could not connect to tracker

[shape]

i'm getting both of these messages on about 6 different trackers. if it was only 1 tracker i would assume it's a tracker issue, but in this case it's every one of them. none are working, my port is open/green, & i've checked it at http://canyouseeme.org/. PEX, DHT, & local peer discovery are all checked in the peer prefs. i've rebooted my computer + router and relaunched T to no avail. any ideas?

using T 2.42 & OSX 10.6.8

[shape]

ok, well in the message log i only had a few errors and they said "http response code 0 (no response)". info shows tons of scrape errors: could not connect to tracker. debug shows "learned IPv4 peers from DHT" these are trackers that normally connect fine daily so it's strange all of them had these errors at once. i am getting some DHT peers now though but still have the other errors.

[feju]

Hi,

I've been having the same problem recently. It appears that after I put my Mac to sleep and wake it up again, Transmission won't be able to connect to any trackers or peers. After rebooting my machine all torrents start downloading at maximum speed.

I get this from Console.app:

07/02/2012 23:32:02.715 Firewall: Transmission is listening from 0.0.0.0:9091 proto=6
07/02/2012 23:32:02.715 Firewall: Transmission is listening from :::49152 proto=6
07/02/2012 23:32:02.715 Firewall: Transmission is listening from :::49152 proto=6

That IP does not look right at all (the one above from the log). Disabling the Firewall and simply relaunching Transmission won't help. I'm running version 2.42 on a OS X Lion 10.7.3 install.

Any ideas?

[feju]

I've come across another case, where the announce actually works. I can see the number of seeds and leechers in the inspector. However, for some reason the availability remains at 0 (the entire corresponding bar in the UI is red). I know the tracker. There is no way of this staying that way and I have encountered this a number of times. After rebooting this torrent will fly.

Any ideas, except the pause before sleep method? This used to work just fine up until some tie ago :/