Deluge Forum

I'm tunneling my connection via ssh.(Using my ssh server at home)

I can't seem to connect to this tracker: I keep getting 'Alert:timed out' error with every connection attempt.

Is anyone else having this problem?

Thanks in advance.
Deluge version: 0.5.7.1

I was just wanted to ask the same thing.
Yup! Me too can't connect to denis stalker.

I also have difficulties trying to connect to;
http://eztv.sladinki007.eu:60500/announce

My Deluge crash when trying to connect to the sladinki tracker.
I was downloading Cane.S01E13.HDTV.XviD-NoTV (eztv)

Other torrent like those which are not by eztv, I can download without crashing at all.
It crash only when I start Cane only.

Sometimes it also crash when I download multiple torrents at once.

Thanks in advanced coz you guys have done a very good job.

Merry Christmas too to everyone (Both developers and user) !

Roonaldo_7 wrote:I'm tunneling my connection via ssh.(Using my ssh server at home)
I can't seem to connect to this tracker:

Code: Select all

http://denis.stalker.h3q.com:6969/announce

I keep getting 'Alert:timed out' error with every connection attempt.

If you're using one of the L1 blocklists from Bluetack (i.e. via a plug in or via PeerGuardian or its variants), their IP was listed in Level1 the last time that I checked. I don't know what the current status is.

Bluetack forum: http://www.bluetack.co.uk

Hi,

I am not using any block lists.

I too am receiving this error:
On a different tracker, though. If I update tracker enough, I eventually get a connect, but then it will have the same status some time later. I'm uncertain if this is just a problem with the tracker I am connecting to or if it is Deluge. I've moved from using uTorrent in wine (this is Ubuntu Linux, BTW) to Deluge recently... do not recall ever receiving an error like this with uTorrent.

This is a private tracker, with stats keeping, which is very important and my worry has been that stats are not being kept properly.

Any ideas?

EDIT:

Also, I am using no blocklist either...

Most likely a tracker problem. I get this error too sometimes. If you notice it happening, pause the torrent for a bit of time and resume until you get a "sane" announce. Unfortunately ul/dl bytes between last "OK" announce and the error don't get recorded at the tracker stats (at least at the tracker that I am).