• Debian torrent tracker is down

    From Alexander V. Makartsev@21:1/5 to All on Tue Dec 21 16:10:02 2021
    This is a multi-part message in MIME format.
    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
    ⠈⠳⣄⠀⠀⠀⠀


    <html>
    <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    </head>
    <body>
    It looks like Debian torrent tracker ( bttracker.debian.org )
    doesn't work for a few days, but the host itself is up.<br>
    Can anyone confirm this?<br>
    <br>
    <pre class="moz-signature" cols="72">--
    With kindest regards, Alexander.

    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ <a class="moz-txt-link-freetext" href="https://www.debian.org">https://www.debian.org</a>
    ⠈⠳⣄⠀⠀⠀⠀
    </pre>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mattias Wadenstein@21:1/5 to Alexander V. Makartsev on Tue Dec 21 17:00:01 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alexander V. Makartsev@21:1/5 to Mattias Wadenstein on Tue Dec 21 20:20:02 2021
    This is a multi-part message in MIME format.
    On 21.12.2021 20:51, Mattias Wadenstein wrote:
    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
    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?

    --
    With kindest regards, Alexander.

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


    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div class="moz-cite-prefix">On 21.12.2021 20:51, Mattias Wadenstein
    wrote:<br>
    </div>
    <blockquote type="cite"
    cite="mid:alpine.DEB.2.21.2112211649580.156161@lenin.acc.umu.se">On
    Tue, 21 Dec 2021, Alexander V. Makartsev wrote:
    <br>
    <br>
    <blockquote type="cite">It looks like Debian torrent tracker (
    bttracker.debian.org ) doesn't work for a few days, but the host
    itself is up.
    <br>
    Can anyone confirm this?
    <br>
    </blockquote>
    <br>
    Hi!
    <br>
    <br>
    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.
    <br>
    <br>
    I can also load the stats fine. What exactly isn't working for
    you?
    <br>
    <br>
    /Mattias Wadenstein
    <br>
    </blockquote>
    My torrent client (Tixati) reports "Connection timed out" for URL:<br>
    <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/announce">http://bttracker.debian.org:6969/announce</a><br>
    <br>
    Here is magnet link for one of the torrents, but I don't think it
    matters:<br>
    <a class="moz-txt-link-freetext" href="magnet:?xt=urn:btih:fdcvdfxvo5j4icwow35vqyl6ngk2p3o3&amp;dn=debian-11.2.0-amd64-netinst.iso&amp;tr=http%3A%2F%2Fbttracker.debian.org%3A6969%2Fannounce">magnet:?xt=urn:btih:fdcvdfxvo5j4icwow35vqyl6ngk2p3o3&amp;dn=
    debian-11.2.0-amd64-netinst.iso&amp;tr=http%3A%2F%2Fbttracker.debian.org%3A6969%2Fannounce</a><br>
    <br>
    This is odd, because many other torrent trackers and hundreds of
    torrents work just fine.<br>
    I don't know how to check if it is working. A plain simple 'wget'
    request gives:<br>
        $ wget -O- <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/announce">http://bttracker.debian.org:6969/announce</a><br>
        --2021-12-21 23:32:43-- 
    <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/announce">http://bttracker.debian.org:6969/announce</a><br>
        Resolving bttracker.debian.org (bttracker.debian.org)...
    130.239.18.158, 2001:6b0:e:2018::158<br>
        Connecting to bttracker.debian.org
    (bttracker.debian.org)|130.239.18.158|:6969... connected.<br>
        HTTP request sent, awaiting response... No data received.<br>
        Retrying.<br>
    <br>
    And if I send same request to another tracker I get.. well at least
    something:<br>
        $ wget -O- <a class="moz-txt-link-freetext" href="http://tracker.humblebundle.com:2710/announce">http://tracker.humblebundle.com:2710/announce</a><br>
        --2021-12-21 23:39:44-- 
    <a class="moz-txt-link-freetext" href="http://tracker.humblebundle.com:2710/announce">http://tracker.humblebundle.com:2710/announce</a><br>
        Resolving tracker.humblebundle.com (tracker.humblebundle.com)...
    104.154.156.79<br>
        Connecting to tracker.humblebundle.com
    (tracker.humblebundle.com)|104.154.156.79|:2710... connected.<br>
        HTTP request sent, awaiting response... 404 Not Found<br>
        2021-12-21 23:39:47 ERROR 404: Not Found.<br>
    <br>
    Could it be that Debian torrent tracker blocks out requests from Tor
    network?<br>
    <br>
    <pre class="moz-signature" cols="72">--
    With kindest regards, Alexander.

    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ <a class="moz-txt-link-freetext" href="https://www.debian.org">https://www.debian.org</a>
    ⠈⠳⣄⠀⠀⠀⠀
    </pre>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mattias Wadenstein@21:1/5 to Alexander V. Makartsev on Thu Dec 23 15:20:02 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alexander V. Makartsev@21:1/5 to Mattias Wadenstein on Thu Dec 23 18:40:01 2021
    This is a multi-part message in MIME format.
    On 23.12.2021 19:18, Mattias Wadenstein wrote:
    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
    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.

    --
    With kindest regards, Alexander.

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


    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div class="moz-cite-prefix">On 23.12.2021 19:18, Mattias Wadenstein
    wrote:<br>
    </div>
    <blockquote type="cite"
    cite="mid:alpine.DEB.2.21.2112231515430.156161@lenin.acc.umu.se">On
    Tue, 21 Dec 2021, Alexander V. Makartsev wrote:
    <br>
    <br>
    <blockquote type="cite">On 21.12.2021 20:51, Mattias Wadenstein
    wrote:
    <br>
    This is odd, because many other torrent trackers and hundreds of
    torrents work just fine.
    <br>
    I don't know how to check if it is working. A plain simple
    'wget' request gives:
    <br>
        $ wget -O- <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/announce">http://bttracker.debian.org:6969/announce</a>
    <br>
        --2021-12-21 23:32:43--
    <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/announce">http://bttracker.debian.org:6969/announce</a>
    <br>
        Resolving bttracker.debian.org (bttracker.debian.org)...
    130.239.18.158, 2001:6b0:e:2018::158
    <br>
        Connecting to bttracker.debian.org
    (bttracker.debian.org)|130.239.18.158|:6969... connected.
    <br>
        HTTP request sent, awaiting response... No data received.
    <br>
        Retrying.
    <br>
    <br>
    And if I send same request to another tracker I get.. well at
    least something:
    <br>
        $ wget -O- <a class="moz-txt-link-freetext" href="http://tracker.humblebundle.com:2710/announce">http://tracker.humblebundle.com:2710/announce</a>
    <br>
        --2021-12-21 23:39:44--
    <a class="moz-txt-link-freetext" href="http://tracker.humblebundle.com:2710/announce">http://tracker.humblebundle.com:2710/announce</a>
    <br>
        Resolving tracker.humblebundle.com
    (tracker.humblebundle.com)... 104.154.156.79
    <br>
        Connecting to tracker.humblebundle.com
    (tracker.humblebundle.com)|104.154.156.79|:2710... connected.
    <br>
        HTTP request sent, awaiting response... 404 Not Found
    <br>
        2021-12-21 23:39:47 ERROR 404: Not Found.
    <br>
    </blockquote>
    <br>
    I get the first behaviour with wget. You could something that
    doesn't actually exist, like /stats or something that does, like
    /stats?
    <br>
    <br>
    <blockquote type="cite">Could it be that Debian torrent tracker
    blocks out requests from Tor network?
    <br>
    </blockquote>
    <br>
    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.
    <br>
    <br>
    /Mattias Wadenstein
    <br>
    </blockquote>
    Here is the wget output I get over plain Internet:<br>
        wget -O- <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/stats">http://bttracker.debian.org:6969/stats</a><br>
        --2021-12-23 20:43:18--  <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/stats">http://bttracker.debian.org:6969/stats</a><br>
        Resolving bttracker.debian.org (bttracker.debian.org)...
    130.239.18.158, 2001:6b0:e:2018::158<br>
        Connecting to bttracker.debian.org
    (bttracker.debian.org)|130.239.18.158|:6969... connected.<br>
        HTTP request sent, awaiting response... 404 NotFound<br>
        2021-12-23 20:43:18 ERROR 404: NotFound.<br>
    <br>
    And here is the wget output I get over Tor network:<br>
        $ http_proxy=127.0.0.1:81 wget -O-
    <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/stats">http://bttracker.debian.org:6969/stats</a><br>
        --2021-12-23 20:55:05--  <a class="moz-txt-link-freetext" href="http://bttracker.debian.org:6969/stats">http://bttracker.debian.org:6969/stats</a><br>
        Connecting to 127.0.0.1:81... connected.<br>
        Proxy request sent, awaiting response... 503 Forwarding failure<br>
        2021-12-23 20:56:40 ERROR 503: Forwarding failure.<br>
    <br>
    So that explains it. Host "bttracker.debian.org" or its hosting
    provider blocks traffic from Tor network.<br>
    I've configured an exception for this tracker to use open Internet
    instead of Tor network and now it works fine.<br>
    Thanks for assistance, Mattias.<br>
    <br>
    <pre class="moz-signature" cols="72">--
    With kindest regards, Alexander.

    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ <a class="moz-txt-link-freetext" href="https://www.debian.org">https://www.debian.org</a>
    ⠈⠳⣄⠀⠀⠀⠀
    </pre>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)