A connection attempt failed in download
-
Since yesterday, most of the torrents I try to download are experiencing this error below, in addition I have more than a thousand torrents as seed and now because of this error only 90 appear as seeding. Can someone help me?
"A connection attempt failed because the connected component did not respond correctly after a period of time, or the established connection failed because the connected host did not respond"
-
@zullu Yes, the tracker seems to be non-responsive for me too.
-
Me too. Seems to vary, sometimes it's so bad only a few torrents are active, sometimes it's nearly normal. I tried increasing the torrent client's sync time from 600 to 900 ms but that didn't help.
-
Same error for me. Tried to access the tracking in my browser but was Unresponsive.
-
I'm also having the same problem, very frustrating
-
Not sure if this is the same problem, but all the torrents I've downloaded as of today are registering as having 0 seeds and peers.
The torrents download fine (there is no error message that appears), but can't start as it seems to be dead (even though there appears to be plenty of seeds/peers on the torrent page).
The tracker status is showing as 'Not working'.
I've tried Steps 1 and 2 on the relevant troubleshooting page. Step 3 is going to be a little more troublesome - the uPnP option doesn't seem to be working, and a manual reconfiguration of the router is going to be a little bit of a hassle to figure out, so I'm hoping someone can confirm whether this is a general tracker issue before I have to dig around for my router manual.
-
Further information in separate post because I can't find a way to edit my previous post.
I happen to have a torrent from weeks ago that I had left paused. That torrent works just fine (it detects seeds/peers even while paused, and promptly connects and starts downloading when I Resume).
It seems like its only the torrents downloaded from today that aren't working.
If it helps, I'm using qBittorrent.
-
I concur with the observations above: sine 1~2 days most torrents are in trouble…
-
Referenced by S spiffyweasel 0
-
@Douseikekkon More recent reports of connection issues: https://community.gaytorrent.ru/topic/64831/most-of-my-files-are-red/
-
I thought I'm the only one!. It seems to work after a couple hours of not doing anything but still it's a hassle to improve your ratio.
-
FWIW: There seems to be one thing in common with all these cases... uTorrent 3.6.0, BitTorrent 7.11, qBitTorrent 4.6.2, and a few others that are based on the same Libtorrent base as qBitTorrent is.
I think you may find that rolling back your torrent client to a previous version will help with this.
The only difference between martyrdom and suicide is press coverage! -
It happens on qbittorrent v4.3.9 (old) and rtorrent / rutorrent 4.0 (the latest). It does not happen with Tixati.
qbittorrent 4.3.9 is at least a few years old so I don't think rolling back will help.
I think the only difference between these clients is the "default tracker timeout" value. Based on what I've seen, Tixati has a much longer default timeout so it doesn't have this problem. rtorrent says "Tracker: timeout reached" and qbittorrent says "skipping tracker announce (unreachable)."
Unfortunately I can't find any way to change the default tracker timeout value on any of these three clients. I thought I found the setting in rtorrent but it was the GUI sync timeout not the tracker timeout
This started 5-6 days ago and seems to get a little better sometimes. It might be load related.
Another possibility, has the site's tracker software been updated or changed recently?
I hope you can get this fixed, it's a real PITA.
-
@urx585 All those mentioned torrent clients run on the libtorrent base. That could be why.
The only difference between martyrdom and suicide is press coverage! -
@MrMazda thanks for the reply!
Found these two snippets online:
-
The rTorrent torrent client is a digital software that allows users to engage in peer-to-peer file sharing. The software was first released in 2005. It uses the C++ language and is based on the libTorrent (not libtorrent) libraries for Unix.
-
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
I don't think rtorrent uses anything from libtorrent (lowercase T) because libtorrent, as used by qbittorrent and bittorrent, was still in beta in 2005.
I was told by another mod here that this was the reason rtorrent doesn't deal with padding files correctly: it doesn't use libtorrent.
The other suggestions about the DDoS protections being too strict make perfect sense, but if nobody made any changes to the site, the tracker software, or the DDoS protections about six days ago, it's still a total mystery.
-
-
Did reverting to older versions work for any of you?
-
Update: After trying a few older versions of qbittorrent, I find version v.6.0 works for me. Its not really a fix cause it took awhile for it to connect to the site maybe an hour or less. Compared that to the latest version that took 4 hours to connect to the site.
-
I currently have the issue that the Tracker Status is stuck with "Updating..."
Using qbittorrent v4.6.4 -
Also having this problem. No new software on my side for about a year.
-
@MrMazda Have server-side changes been looked at so far (the entire stack from the DDoS protection to the actual tracker service)? To my mind, there has been sufficient evidence to indicate that none of the affected users have changed anything in their client.
I'm down to seeding barely 100 torrents down from approximately 16,000, and I'm seeing a steady uptick in the number of reseed requests since the start of the outage. If a fix is not found soon, I plan to stop seeding entirely for the time being.
-
Only @Joker would know if backend settings were changed unless he said something on the staff Discord, which I haven't seen but could have missed.
I'm seeing a bunch of trackers (porn and non-porn) having this issue lately, so it seems like it's something common with them all, like Cloudflare or something.
