Debian torrent tracker is down

Alexander V. Makartsev

unread,

Dec 21, 2021, 10:10:03 AM12/21/21

to

It looks like Debian torrent tracker ( bttracker.debian.org ) doesn't work for a few days, but the host itself is up.
Can anyone confirm this?

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

Mattias Wadenstein

unread,

Dec 21, 2021, 11:00:02 AM12/21/21

to

On Tue, 21 Dec 2021, Alexander V. Makartsev wrote:

> It looks like Debian torrent tracker ( bttracker.debian.org ) doesn't work
> for a few days, but the host itself is up.
> Can anyone confirm this?

Hi!

I'm not seeing any issues with the torrent tracker, I even tried from home
(external to the datacenter where it is hosted), and could download a
torrent fine and the torrent client indicated that it saw lots of peers
from the tracker.

I can also load the stats fine. What exactly isn't working for you?

/Mattias Wadenstein

Alexander V. Makartsev

unread,

Dec 21, 2021, 2:20:03 PM12/21/21

to

My torrent client (Tixati) reports "Connection timed out" for URL:
http://bttracker.debian.org:6969/announce

Here is magnet link for one of the torrents, but I don't think it matters:
magnet:?xt=urn:btih:fdcvdfxvo5j4icwow35vqyl6ngk2p3o3&dn=debian-11.2.0-amd64-netinst.iso&tr=http%3A%2F%2Fbttracker.debian.org%3A6969%2Fannounce

This is odd, because many other torrent trackers and hundreds of torrents work just fine.
I don't know how to check if it is working. A plain simple 'wget' request gives:
    $ wget -O- http://bttracker.debian.org:6969/announce
    --2021-12-21 23:32:43-- http://bttracker.debian.org:6969/announce
    Resolving bttracker.debian.org (bttracker.debian.org)... 130.239.18.158, 2001:6b0:e:2018::158
    Connecting to bttracker.debian.org (bttracker.debian.org)|130.239.18.158|:6969... connected.
    HTTP request sent, awaiting response... No data received.
    Retrying.

And if I send same request to another tracker I get.. well at least something:
    $ wget -O- http://tracker.humblebundle.com:2710/announce
    --2021-12-21 23:39:44-- http://tracker.humblebundle.com:2710/announce
    Resolving tracker.humblebundle.com (tracker.humblebundle.com)... 104.154.156.79
    Connecting to tracker.humblebundle.com (tracker.humblebundle.com)|104.154.156.79|:2710... connected.
    HTTP request sent, awaiting response... 404 Not Found
    2021-12-21 23:39:47 ERROR 404: Not Found.

Could it be that Debian torrent tracker blocks out requests from Tor network?

Mattias Wadenstein

unread,

Dec 23, 2021, 9:20:03 AM12/23/21

to

On Tue, 21 Dec 2021, Alexander V. Makartsev wrote:

> On 21.12.2021 20:51, Mattias Wadenstein wrote:
> This is odd, because many other torrent trackers and hundreds of torrents
> work just fine.
> I don't know how to check if it is working. A plain simple 'wget' request
> gives:
>     $ wget -O- http://bttracker.debian.org:6969/announce
>     --2021-12-21 23:32:43-- http://bttracker.debian.org:6969/announce
>     Resolving bttracker.debian.org (bttracker.debian.org)... 130.239.18.158,
> 2001:6b0:e:2018::158
>     Connecting to bttracker.debian.org
> (bttracker.debian.org)|130.239.18.158|:6969... connected.
>     HTTP request sent, awaiting response... No data received.
>     Retrying.
>
> And if I send same request to another tracker I get.. well at least
> something:
>     $ wget -O- http://tracker.humblebundle.com:2710/announce
>     --2021-12-21 23:39:44-- http://tracker.humblebundle.com:2710/announce
>     Resolving tracker.humblebundle.com (tracker.humblebundle.com)...
> 104.154.156.79
>     Connecting to tracker.humblebundle.com
> (tracker.humblebundle.com)|104.154.156.79|:2710... connected.
>     HTTP request sent, awaiting response... 404 Not Found
>     2021-12-21 23:39:47 ERROR 404: Not Found.

I get the first behaviour with wget. You could something that doesn't
actually exist, like /stats or something that does, like /stats?

> Could it be that Debian torrent tracker blocks out requests from Tor
> network?

Not as far as I know. But I guess if that particular exit node had been
particularly nasty in the past, there might be filters upstream from it.

/Mattias Wadenstein

Alexander V. Makartsev

unread,

Dec 23, 2021, 12:40:03 PM12/23/21

to

Here is the wget output I get over plain Internet:
wget -O- http://bttracker.debian.org:6969/stats
--2021-12-23 20:43:18-- http://bttracker.debian.org:6969/stats

Resolving bttracker.debian.org (bttracker.debian.org)... 130.239.18.158, 2001:6b0:e:2018::158
Connecting to bttracker.debian.org (bttracker.debian.org)|130.239.18.158|:6969... connected.

    HTTP request sent, awaiting response... 404 NotFound
    2021-12-23 20:43:18 ERROR 404: NotFound.

And here is the wget output I get over Tor network:
    $ http_proxy=127.0.0.1:81 wget -O- http://bttracker.debian.org:6969/stats
    --2021-12-23 20:55:05-- http://bttracker.debian.org:6969/stats
    Connecting to 127.0.0.1:81... connected.
    Proxy request sent, awaiting response... 503 Forwarding failure
    2021-12-23 20:56:40 ERROR 503: Forwarding failure.

So that explains it. Host "bttracker.debian.org" or its hosting provider blocks traffic from Tor network.
I've configured an exception for this tracker to use open Internet instead of Tor network and now it works fine.
Thanks for assistance, Mattias.