A connection attempt failed in download
-
@raphjd
with all due respect, a number of people here have said they are only seeing it on this tracker. Personally, I am seeing nothing like this on the other 5 trackers I use regularly, and I've been seeing it here solid for 5+ days. -
At home, I'm only doing torrents from here, using uTorrent 2.2.1 and I'm not seeing it.
I use SeedIt4Me as my seedbox provider and I'm seeing red torrents from both porn and non-porn sites. My 3tb seedbox that I only use for porn always runs fast, but my 5tb mixed torrent is always sluggish.
Even my personal (torrent-only) account here isn't acting up like it seems some people are claiming.
I'm not saying that you guys are wrong, I'm just adding my experience to the mix, hoping something can be figured out.
-
@raphjd I think the hypothesis that there is an "over-eager" DDoS setting on the tracker has merit. Raph, do you really see no problems when you try to download 50 freeleech torrents at the same time? Or are you downloading one or two?
Of course normally you should only be able to connect to 15 simultaneously. But when the first of those 15 are complete, another of the red ones should be free to connect. That's not what's happening now. The system seems to detect 50 current attempted downloads and freak out, locking out all of them. Every now and then, over the course of hours, it will recognize some requests as valid. But it takes 10x as long to download 50 torrents as it used to. This is not sustainable.
-
At home, I usually only load maybe 30 at a time. Of course they don't DL at the same time due to the restrictions
Seeding is whatever currently is seeding. It can be anything from a few to hundreds.
I'll run some tests to see what I come up with based on what I'm reading here, but @MrMazda is more computer-savvy than me.
-
Overly restrictive DDoS settings could be the cause. Definitely possible that Cloudflare made some changes and didn't tell anyone... but at least one other tracker that also uses Cloudflare is not having this problem. I use four trackers and this is the only one with timeout errors.
Or perhaps something happened that overloaded the server, about a week ago, and now it's timing out because of load. The problem seems to get worse at certain times of the day but that is compatible with both DDoS and server overload explanations.
Tixati does not have this problem at all. rtorrent and qbittorrent do. The only difference that makes sense to me is the default timeout value for initial contact with the tracker. I can't find any way to change this setting in either rtorrent or qbittorrent. (The rtorrent documentation is non-existent; I couldn't even find explanations of the settings in the source code.)
However there is an advanced setting in Tixati called upc_mss_init, default value 1212 ms, minimum value 300 ms, max value 1800 ms.
If your torrent client is having this problem, and you can find the setting for initial tracker contact timeout value, please increase it to at least 1.2 seconds and let us know if the problem goes away...
PS qbittorrent has more documentation but I could only find one use of "timeout" and it seems to only take effect when a torrent is stopped, not started:
"Stop tracker timeout — (default: 5 s) is the number of seconds to wait when sending a stopped message before considering a tracker to have timed out. This is usually shorter, to make the client quit faster. If the value is set to 0, the connections to trackers with the stopped event are suppressed."
-
I have been keeping an eye on the situation and have noticed that at times, many torrents will time out, but after some time, come back to life. I have notified the sysop of this.
The only difference between martyrdom and suicide is press coverage! -
@MrMazda FYI: Over the last couple of days, the tracker will start responding to my torrents and I can get to 100% seeding. After about an hour, maybe two, the tracker stops responding for a few hours and I get down to almost 0% again. Couple hours later, it repeats. It has been going up and down consistently. Right now it's in the getting better stage.
Torrents from other sites have no problems and are seeding 100%.
-
@urx585 said in A connection attempt failed in download:
Tixati does not have this problem at all.
Yes it does, at least in my own experience.
I've not been able to connect to the tracker in Tixati, Deluge, or qbittorrent.
-
I'm not able to connect to the tracker AT ALL now. New downloads can't connect, and none of my completed downloads are seeding,
Like other users, I was previously able to connecct intermittently (but only for a short time abd only for a small number of torrents) but now the tracker isn't working at all.
The trackers for other sites (private and public) are alk working fine, it's just the torrents that use the tracker from this website that are showing as errors.
-
Update: The older version v4.6.0 qbittorent is not working for me anymore. Only a handful are seeding. I can't download anything. It seems the site the problem.
-
I'm also having this problem. Only with this tracker. It started about 1 week ago. Using qBitorrent 4.6.4.
My error is "skipping tracker announce (unreachable)".
Happening with 200-544 different torrents throughout the day. Always different number of torrents. Always same error. Always and only this tracker.
-
@MrMazda said in A connection attempt failed in download:
I have been keeping an eye on the situation and have noticed that at times, many torrents will time out, but after some time, come back to life. I have notified the sysop of this.
Thank you.
There are side effects to this issue besides hassles with downloading and missing out on opportunities to seed. If the tracker can't be contacted again for a torrent after a download finishes, the site doesn't know that the torrent has been downloaded, for example there is no voting prompt near the top of the torrent's page. I expect this also means that if a torrent is downloaded fully during a Freeleech period, but the tracker can't be contacted again for that torrent until after the Freeleech period ends, the download may not register as free. I've tried testing this, but the torrent I downloaded to test has not been able to connect and update the tracker after download finished and the Freeleech time for it has expired.
-
I reset my passkey yesterday, which updated my tracker announce URL, and that seems to have fixed my connectivity problems.
The updated tracker is connecting and i've been able to download and seed torrents.
Updating the passkey of course means that the tracker in each of my completed torrents had to be manually changed in order for them to seed, which is annoying, but at least i can download/seed now.
-
@ryan0202012 How did you do that?
-
PASSKEY Info : https://www.gaytor.rent/faq.php#16
OVERVIEW :
What's a 'passkey'?
A passkey is a key associated with your account that uniquely identifies you as a gaytorrent.ru user.When a .torrent file is downloaded from your account, the passkey is automatically added to the announce URL in the .torrent file. Therefore whenever that .torrent is used the tracker will associate it with your account, no matter what IP you are connecting from.
Make sure you keep your passkey and .torrent files private at all times.
Do not give .torrent files you downloaded at gaytorrent.ru to someone else, do not upload it to other websites! Everybody connecting to the tracker using your .torrent file will leech from your account!How do I reset my passkey?
Go to your page and request a new passkey. Note that by using this you will invalidate all the .torrent files that you may have previously downloaded, and will have to download them again.
What's your .torrent/passkey sharing policy?
In order to prevent our .torrents from being uploaded to public sites (in effect turning this into a public tracker), there are a number of security measures in place. First among them is the following: if, at any time, there are more than 5 distinct IPs simultaneously using the same passkey with the same torrent, the account associated with the passkey will be automatically get a new passkey. This will also invalidate all your previously downloaded torrents!
You may still seed/leech the same torrent from several PCs as long as you are careful not to exceed this limit.
Note that this takes into account simultaneous connections only. If you have a dynamic IP and have to change it 100 times while downloading a torrent that it will not trigger this mechanism. (As long as you exit your client properly, there will only be one peer/IP at any time.)
- Keep in mind that resetting your PASSKEY will invalidate all your active torrents that will result in Failure/Unregistered torrent ...
-
@john32123666 said in A connection attempt failed in download:
PASSKEY Info : https://www.gaytor.rent/faq.php#16
OVERVIEW :
What's a 'passkey'?
A passkey is a key associated with your account that uniquely identifies you as a gaytorrent.ru user.When a .torrent file is downloaded from your account, the passkey is automatically added to the announce URL in the .torrent file. Therefore whenever that .torrent is used the tracker will associate it with your account, no matter what IP you are connecting from.
Make sure you keep your passkey and .torrent files private at all times.
Do not give .torrent files you downloaded at gaytorrent.ru to someone else, do not upload it to other websites! Everybody connecting to the tracker using your .torrent file will leech from your account!How do I reset my passkey?
Go to your page and request a new passkey. Note that by using this you will invalidate all the .torrent files that you may have previously downloaded, and will have to download them again.
Just for further clarity, you request a new passkey via your 'Profile' page by clicking your username in the top-right and then selecting 'Profile'.
There's a checkbox to 'Reset passkey' a few lines above 'Browse default categories' section.
I just checked the box and hit Submit Changes at the bottom.
Hope it works for you too
-
@freakgeek see below
-
@ryan0202012 ...
resetting PASSKEY is not a solution ...
it will revert to Timed Out status or updating after a period of time ... [a system glitch]- so do not reset your PASSKEY if you haven't done so far ...
It's coming from the site, regardless of client ...
However not all of us aren't affected yet ...
Hoping the SYSOP can figure out what's goin' on ... -
@MrMazda
I just took a peek and it seems now only ~20 of ~250 torrents are timed out. Hopefully this a sign of things improving... -
@tnar ...
Fortunately It's fine right now ...
I just exited my client restarted PC and client and observe, all the active torrent [Tracker] updated immediately ...
So this issue occurs when maintenance happen, seems like a leftover bug ...
I'm pretty sure this Timed Out will Go Away [soon] and not to annoy again ...
