A connection attempt failed in download
-
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 ...
-
@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.
-
@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. -
@john32123666 They eventually will be cleared... can take 15-30 minutes. At least for me...
-
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.
-
Let's hope.
-
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 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.
-
@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 ... -
Referenced by
john32123666
-
Still not solved for me... it was good... for a while...
-
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.
-
IPv4 uses globally unique public addresses for traffic and “private” addresses.
IPv6 uses globally unique unicast addresses and local addresses
Can you use both IPv4 and IPv6?
Yes. A device that supports dual-stack IPv4/IPv6 addressing can interoperate equally with IPv4-only,
IPv6-only, and other dual-stacked IPv4/IPv6 devices.
When two communicating devices are both dual stacked, they agree on which IP version to use.
SEE : https://www.juniper.net/us/en/research-topics/what-is-ipv4-vs-ipv6.htmlIPv4 vs IPv6: what are they and what's the difference?
SEE : https://cybernews.com/what-is-vpn/ipv4-vs-ipv6/ -
@yepyep7891
No timed out connections for 24+ hours now. Seems to be fixed for me, finally. -
@tnar I haven't had any connection errors in the last 12 hours. I've been checking since 6:00 am (CST) this morning. Hope it stays this way.
