Announce timed out / tracker did not respond

[aibt]

I'm unable to seed anything due to a Scrape error. This is the case since version 1.83 and forced me to downgrade to 1.82 several times (means I've tried the Nightly builds). I hoped it will change with 1.90 but it didn't.
The Torrent Inspector is telling me "Announce times out" and "Scrape error: tracker did not respond". With 1.82 and 1.76 everything works fine. Version 1.90 is not blacklisted on the trackers.

Any help would be appreciated.

[InternetzUser]

I have the exact same Problem.
I went back to version 1.82 and it is working just fine.

[drscoot]

I too am having this problem with Version 1.91 Announces fine with version 1.76

[drscoot]

I tried the newest night release and now the torrents stall. 1.91+ (10307)

[Marc31]

Having used 1.91 (running OS X 10.6.2) for a couple of days now, this afternoon I noticed these same announce time-outs with 6 out of 8 private trackers I frequent.

First, modem reset. No change. Second, app relaunch. Some improvement: 3 trackers previously unresponsive are ok now; the other 3 stayed dead. However, 1 of 2 that responded normally first, now time out.

Glad to supply any additional info needed to help out.

cheers,

<edit> one hour later, all trackers appear to gradually spring back into life.

[iamse7en]

I was having the same issue. I quit Transmission and opened it again, and all trackers announced fine.

[aibt]

Thank you, most likely it got fixed by upgrading libnatpmp and miniupnp. 1.92 seems to have solved the issues =)

[ourmanflint]

Im getting several errors with the new 1.92 update.

Announce Timed Out issues
Scrape Error: Timed Out
and
Tracker gave HTTP response code 504 (Gateway TIme Out)

Whats up with that?

[ourmanflint]

Nevermind, seems to be working ok now.

[WebScud]

I'm having the same problem with 1.92 for Mac. It started few weeks ago and I switched ti µTorrent for a few days, then Transmission started working again. Since then I've done a complete clean install (without restoring from anything type of backup) and the problem has started again. Any thoughts?

[WebScud]

You shouldn't have announce issues with 1.92 stable. If a tracker doesn't respond then you need to contact them for an explanation.

Thanks for the response. It was happening across several private trackers, which is why I thought I'd post here first.

Enjoy your afternoon.

[despicere]

Peer list request timed out ...
Got a scape error "tracker did not respond"...

- is not blacklisted on the trackers
Transmission-gtk 2.13 (11501), ubuntu ~11.04a
Please check it out.

[Moe]

Peer list request timed out ...
Got a scape error "tracker did not respond"...
Please check it out.

Do you know whether the tracker was online or offline? Did you try loading the announce address in a browser?