A connection attempt failed in download

darkeden

"TRACKER CONNECTION ERROR: CONNECTION TIMEOUT"

I restarted torrent client so many times. But still timing out. Zero peers connected. Anyone else having issue?

darkeden

I tried again but this time using a VPN at a US(Atlanta) location and suddenly everything is running again. I'm scared to dc now so im gonna stay on and will update again if running without VPN is the issue.

DirtyNick

@darkeden-0 I was able to connect without using VPN. but took me almost an hour or so before all my torrent worked. One by one they just started to connect.

yepyep7891

Same problem for me... only 402 of 800-something are connected

Vincent9756

Restarted my client 2 hours ago. Right now, 502/545 have connection errors. Keeps changing.

MrMazda

@darkeden-0 I just had to change your passkey. You posted it in public view, which is a very BAD idea as this allows anyone to download content from your account.

tnar

@Vincent9756 Restarted my client 8 hours ago or so. After an hour or so, most were connected, but now I'm back to 200 of 250 timed out. Not fixed.

DirtyNick

It varies each day

MrMazda

For what it's worth, I have been able to duplicate the issue we are having with the tracker.

It works just fine on my torrent tower in my basement, as this connection only has IPv4.

If however I try it on a dual stack IPv4/IPv6 connection that I have access to, all kinds of problems start happening. If I either disable IPv6 on that network, OR if I use a VPN that will force me into IPv4 only, the problem goes away.

So if you're having issues still, I would encourage you to try turning off IPv6 in your computer's network adapter settings and see what happens.

john32123666

Still on-going timed out issues and keep updating ...
When the client exited, those active torrent being seeded will not be cleared @ your profile ...
So when you re-start your client, it will trigger the rest and become unstable ...

However when there are no active torrents and restart client, all are stable and tracker update immediately ...

spiffyweasel 0

@MrMazda This hasn't been my experience. I just forced the use of IPv4 with my VPN and yet the client is having trouble getting the tracker to respond to its requests in a timely manner. Perhaps the number of torrents you are using on your IPv4-only setup is too low for the issues to manifest. For reference, the tracker seems to work fine for my setup for roughly the first 50-100 torrent announce requests and then starts timing out for subsequent requests.

tnar

@MrMazda
disabling IPv6 seems to be working for me. All ~250 torrents I am seeding are now showing a normal status - none are timed out. I'll check back in the morning and see if that's still the case.

yepyep7891

@john32123666 They eventually will be cleared... can take 15-30 minutes. At least for me...

MrMazda

We have found a hardware issue at the server, which may be a part of the issue many people are having. We have since resolved that problem, so it will be interesting to see if things now finally start to come back up.

On a side note, I have more than 3000 torrents in the list, so it should be enough to trigger the issue.

DirtyNick

Let's hope.

john32123666

I did re-started my PC and client several times and all my torrentz came back to life ...
I am no longer seing period timedout/updating issues ...
And those torrentz reset succesfully and cleared @ profile stats, so hoping the issue is gone ...

tnar

@tnar said in A connection attempt failed in download:

@MrMazda
disabling IPv6 seems to be working for me. All ~250 torrents I am seeding are now showing a normal status - none are timed out. I'll check back in the morning and see if that's still the case.

Update: ~12 hours later, I'm back to 2/3 of the torrents timed out.

john32123666

@tnar ...
Yes it came back ...
Tracker glitch is acting up again, and it has nothing to do w/ your network ipv4/ipv6 settings ...
If your client setting is unstable then the rest is affected ...
The issue is coming from here ...
Not on your end ...

yepyep7891

Still not solved for me... it was good... for a while...

Vincent9756

It seems a little better after unchecking IPv6 in Windows Network settings. Now, instead of "unreachable", I get connection timeouts.

Regardless, there's always some amount of errors when I check my client during the day. The problem is still not solved for me either.