Common Torrent problems

[Deadfire]

See The First post for common problems. Below states Problem Connecting to/with Tracker

7, 'getaddrinfo failed' (aka 10007)

• That means that your client can't get a connection to the Tracker's IP address.
• Here are some possible reasons:
  1. Your client can't get through your firewall.
  2. Your ISP's DNS server is down.
  3. Your ISP's DNS server can't resolve the trackers domain to an IP address.
  4. The Tracker is down and isn't responding.

47, 'address family not supported' (aka 10047)

• This error is generated only because of incorrect network settings in Windows.
• Make sure you:
  1. Have "Client for Microsoft Networks"
  2. Install the Microsoft version of "TCP/IP"
  3. You're logged in and have a current IP address. You can use "winipcfg" or 'ipconfig/all' from the Command Prompt.
  4. Test other network applications for proper operability

54,'Connection reset by peer' (aka 10054)

This occurs when an established connection is shut down for some reason by the remote computer, just ignore it.


55, 'No buffer space available' (aka 10055)

• A lot of routes in your routing table (due to a misconfigured router, or misconfigured default route)
• Or lots of stale connections in your connection table
• Or a lot of data that is pending for sending or receiving on a current connection(s), which can't be sent or received for some reason (destination System dead or unreachable, for example).
• Or opening too many sockets at the same time.
• Or maybe you don't have enough free space on your hard drive.

60, 'Operation timed out' (aka 10060)

• That error means that the tracker is down or too busy to process your request. Just keep trying - leave your torrent open, if it doesn't see some action in about 20 -30 minutes try again later, the tracker may just be busy that's all.
• It may also be your BT Client, try a different client
• If after a few days your download still does not start or continue and you are sure you have correctly configured your environment (i.e. made sure you have read all the FAQs about configuring your client), then you can safely assume the tracker/torrent is gone.

61, 'Connection refused' (aka 10061)

• This means that you cannot for whatever reason establish a connection to the Tracker needed to download a file.
• This is commonly caused by firewalls/routers, trackers/servers going down or being too busy, or your net connection going down.
• You may also be banned from using this tracker because of leeching from it.
• More often than not with this error you can simply leave your client window open and it will sort itself out, or you can close the BT Client and try resuming the torrent.
• If the problem is persisting make sure the Tracker you wish to connect is operating, and make sure your firewall/router is not interfering with TCP traffic on the BT ports.
• If after a few days your download still does not start or continue and you have correctly configured your environment, then you can safely assume the tracker is gone.

65, 'no route to host' (aka 10065)

• This can be caused by the remote host appearing to be down (which could be the port chosen being blocked at the said host).
• This could also be down to a system admin at work having noticed unusual traffic and blocked a port or banned an IP then.
• I would say try connecting for a couple of days, if you are still having problems with the same error message then I suggest you find another .torrent.

111, 'Connection refused' (aka 10111)

Just let the torrent run in your client and the client will keep checking the tracker and should resume eventually.

HTTP Error -1

Leave your torrent running in your client. The client will keep checking the tracker and it should resume eventually.

HTTP error 404: Page cannot be displayed/found The requested site is either unavailable or cannot be found. Please try again later.

• It might be that the server the .torrent file is stored on is busy. Try it again in a few minutes.
• It could be an old .torrent file. Try to find a new link to the torrent.
• Your internet address may have changed since you downloaded the .torrent file. Did your line drop? Did you have to disconnect? Simply re-download the .torrent file. If necessary, restart your machine. Your BT Client will re-check anything it has download so far and then resume from where it left off.
• If this is your first torrent, that MAY mean you have not configured your internet/proxy or BT Client settings correctly. Try another torrent that other users have been able to download successfully

HTTP error 503: service unavailable

Have you tried to check on the tracker's status? Maybe the tracker is down for a rest or something bad happened


Unrecognized Host

• Probably a private tracker (or one that requires passkeys) - go there and sign-up (or download the torrent from there).
  
• If this is your first torrent, that MAY mean you have not configured your internet/proxy or BT Client settings correctly. Try another torrent that other users have been able to download successfully

[Deadfire]

This part only Deals with the Stuck @ ~95% Issue some people get.

1. You're Still Getting Good Transfer Rate (But More Hash Fails)

What's happening behind the scenes in your BT Client (if you look at the console or other debugging info) is that a particular piece of data is being detected as bad by the integrity checking function ("hash failure").

The most common cause of this problem is a bad router that is consistently corrupting a specific piece-data packet.

Some routers employ a routing trick called "game mode," where they rewrite the internal and external IP address bytes found within the payload of incoming and outgoing packets. This allows older games, which hard-code IP addresses within their messaging format, to function from behind a NAT setup.

However, when such an address byte sequence is coincidentally present within a file (and that doesn't mean an IP address), when that file is sent via Torrent protocol, the router mistakenly rewrites the data matching the "IP address" it found. This changes the actual received piece data contents, causing them to fail hash checking.

Any incoming packet that has a byte sequence that just happens to match the address byte sequence is susceptible to corrupting, which is estimated to randomly happen about once every 4GB of data.

There are several ways to fix or get around the problem:

1. Please note: There is a possible solution that will only work once for every download and only when your ISP assigns a dynamic external IP address to you. Simply disconnect / reconnect to the internet and hope that the IP changes. If that happens, your router will corrupt another (different) byte sequence and you might be able to finish the download. But the next time a block contains the new byte sequence that'll happen again, thus it's only a temporary solution if you can't disable game mode / DMZ on your router.
   
2. Do not run your router in DMZ (Demilitarised Zone) mode (where packets not explicitly forwarded are routed by default to a single machine), as many routers seem to employ game mode-like corrupting by default for DMZ-bound traffic. Instead, you should enable explicit port-forwarding on your router for the your BT Client's incoming port;
   
3. If your router has such a game mode option (many do not, even though they corrupted anyway), turn it off;
   
4. If you have done the above two, try connecting directly to the Internet (i.e. bypass your NAT router entirely, by switching to bridge mode or by taking out your router if it's separate from your modem) to finish off the last piece. Be sure to have all your latest OS patches and make sure you have a decent firewall otherwise your computer will get compromised in minutes.
   

Also, make sure you use the latest version of your BT Client.


2. Your Transfer Rate Has Dropped; Hash Fails No More Than Usual

This is probably an anti-leech protection feature to make sure that you share your pieces of the file with others. Some BT Clients may do this.


3. Your Transfer Has Stopped Completely

Some routers / firewalls detect data that matches address byte sequences as IP Spoofing. Check your router / firewall security log for IP spoofing entries. If you find entries for the incoming port of your BT Client, you need to disable IP spoofing detection. You may need to disable the firewall function entirely.


4. Other Possible Solutions

Check what the remaining 0.1% is. Open up the torrent details and go to the Files tab and see what files are incomplete.

• If the file is Thumbs.db, desktop.ini, or .DS_Store, choose not to download them. Check the Help / FAQ / Manual of your BT Client to see if and how this option is supported. Operating systems sometimes will generate these files automatically when you browse the directory. Because they are hidden system files they are protected and can't be replaced with the 'correct' versions your BT Client downloads, so it will discard it, fail the hash check, and download again -- forever.
  
• If the file is a textfile/readme file that you don't need to use the product, you can do the same thing if the file is not essential.

If all else fails, try stopping and starting the torrent again, and if that doesn't fix it, stop all transfers, shut down your BT Client, turn off your computer and modem / router, wait a couple of minutes, turn everything back on, restart your BT Client, and start only that torrent for completion.

If it's a video, it might still play.. however thats up to you to try