• Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Torrents

    Tracker gave HTTP response code 404 (Not Found)

    Uploading
    4
    5
    284
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      ni240sx last edited by

      tried to find this topic (even a search didn't come up with results), thus posting my common situation regarding seeding active files.

      my torrent client is transmission.  and I'd be able to seed (up to ratios of 0.76 or 1.39 or 2.05), then I'd get this scrape error message:  Tracker gave HTTP response code 404 (Not Found).  and this file would stop seeding, even though the original file are in same folders after being downloaded.  and the file names have remained intact.  no changes.

      it would happen to some files.  some files continue being active (as with being able to complete seeding limit ratio) with no issues.  and other files would get the scrape error message (and stop seeding).  no consistency here.

      any ideas?  and thank you.

      1 Reply Last reply Reply Quote 0
      • T
        tediczek last edited by

        have exactly same problem with the tracker. I'm using transmission on a media player and none of my torrents snatched from gaytorrent.ru is seeding.

        The gaytorrent.ru website says I have zero torrents in upload. Trasnmission says 'seeding' but also gives Scrape error: "Tracker gave HTTP response code 404 (Not Found) ".

        below is the info on a sample torrent from transmission, maybe admins could look into that. Thank you.

        *****.m4v
        Activity
        Have:
        1.17 GB (100%)
        Availability:
        100%
        Downloaded:
        1.31 GB
        Uploaded:
        1.22 GB (Ratio: 0.93)
        State:
        Seeding
        Running Time:
        2 days, 20 hours
        Remaining Time:
        Unknown
        Last Activity:
        30 minutes ago
        Error:
        None
        Details
        Size:
        1.17 GB (1,121 pieces @ 1.00 MiB)
        Location:
        /tmp/transmission_link/Downloads
        Hash:
        6a9c242739c66f99f8b9ada1d64e5d4d87d3b645
        Privacy:
        Private to this tracker – DHT and PEX disabled
        Origin:
        Created by QuickTorrentMaker V1.5 on Tue Feb 05 2013
        Comment:
        This torrent was created by QuickTorrentMaker V1.5

        Bear-Minded.m4v
        Tier 0

        http://tracker.gaytorrent.ru:2710
            Last Announce: Today 02:08:28 PM (got 0 peers)
            Next announce in 21 minutes
            Scrape error: Tracker gave HTTP response code 404 (Not Found) - Today 02:04:31 PM
            Seeders: 101
            Leechers: 3
            Downloads: N/A

        1 Reply Last reply Reply Quote 0
        • P
          Popper Global Moderator last edited by

          That is not the full right tracker announce URL. Either you have shorten it on purpose, because it contains your secrete personal passkey or it is the cause of that error.

          The right tracker URL should look like http://tracker.gaytorrent.ru:2710/HereYourSecretPasskey/announce

          where "HereYourSecretePasskey" is a long sequence of letters and numbers. Never publish that passkey. Even moderators can't see it on purpose.

          1 Reply Last reply Reply Quote 0
          • E
            evolutionofx last edited by

            Sorry for the bump, but I'm experiencing this issue too. Rolling over the tracker URL shows that it does have my correct passkey in the URL.

            However, my upload stats are NOT updating (site says 0.00 KB uploaded) and I get that error code on my seeding torrents.

            1 Reply Last reply Reply Quote 0
            • P
              Popper Global Moderator last edited by

              Our tracker got the scrape function switched off for increased privacy. A torrent client has to join the swarm as "active" peer to get information on the peers. If the torrent is just queued, a scrape error will be shown. So if your torrents are just queued, it is "normal" and you might change the priority settings or force start to get them running.

              If your torrents are in "Seeding" or "Downloading" status (means not queued downloading or seeding), the cause is another and we have to look for other solutions than starting them.

              1 Reply Last reply Reply Quote 0

              • 1 / 1
              • First post
                Last post