Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not connecting to some peers #7155

Closed
janot opened this issue Jul 23, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@janot
Copy link

commented Jul 23, 2017

3.3.14 64-bit on Win 10

I noticed that qBittorrent doesn't connect to some peers while uTorrent 2.2.1 instantly finds them.

I wasn't able to connect to sole seeder on private tracker and asked ppl to help (download and seed to me). Somebody started downloading and qBittorrent started downloading from them. Then I hibernated PC and badumtsss... next day that guy downloaded 100% files, but now qBittorrent isn't connecting to this seeder. Then one more seeder appeared but still no luck.
So, currently on this torrent qBittorrent connects to 0/3 seeders while uTorrent to 2/3.

@Seeker2

This comment has been minimized.

Copy link

commented Jul 24, 2017

qBitTorrent may be needing a close and restart after hibernation...if it's anything like sleep:
#7104

@janot

This comment has been minimized.

Copy link
Author

commented Jul 24, 2017

I've restarted it before submitting this issue (should've write about that, sry).

@Seeker2

This comment has been minimized.

Copy link

commented Jul 24, 2017

I also have an old uTorrent 2.2.1 running on 1 computer and qBT 3.3.14 running on another. They are on different internet connections which do not seem to be crippling BitTorrent...though if 1 was, I'd suspect it'd be the uTorrent/ComCast one.

On a very huge public torrent (~150 GB in size) that never seems to get many seeds... Peers take days if not weeks to download it all. That torrent is on both BT clients, using the same trackers.
uTorrent is connected to 10 peers, qBitTorrent connects to 6-7 peers. Both allow uTP, although uTorrent doesn't allow uTP outgoing...so uTorrent should have fewer peers. uTorrent is also using initial seeding mode, which can cause peers to disconnect "in disgust" from getting nothing from it for hours. uTorrent is also set to not connect outgoing to listening ports often used for other services and/or prone to DoS attacks.

Similar problem at qBitTorrent forums:
Issues connecting to peers while seeding https://qbforums.shiki.hu/index.php/topic,5179.0.html

@XQ6FOD

This comment has been minimized.

Copy link

commented Nov 8, 2017

I often observe the same behavior: On a specific torrent, at this moment, qBitTorrent reports 0(2) seeds and 1(2) peers. That one peer it's connecting to is obviously downloading the file at this very time at a slow rate from one or both of those seeders qBitTorrent can't connect to, and every two minutes or so he completes a piece of the file, and I then get that piece it from him at a fast download rate. Then it completed, and the datarate drops to zero until that peer completes the next piece and passes it on to me. So I'm downloading the file using that peer as a repeater station or middleman...
I have been watching this many times, on differnet torrents, and my computer with qBitTorrent just absolutely cannot connect to many seeds and peers that are obviously online and delivering data to others.

I haven't tried other clients, so I can't say whether the problem is related to qBitTorrent or to my connection. But Seeker2's comment suggests it's somehow related to qBitTorrent.

The version I'm using is 3.3.16.

@Balls0fSteel

This comment has been minimized.

Copy link

commented Feb 9, 2018

Well, it is absolutely possible that the peers are picky and it's not qBittorrent's fault. I mean, as many libraries and clients are out there - they all behave differently. Don't get me wrong, if you can pinpoint which clients did not connect, we could trace this down, check things. But without detailed information, there is only this much we can do.

So please, next time you encounter such anomaly, screenshot or just copy out the affected peers (from both clients), mark which one cannot connect. Should take only 5 minutes. Thank you! (Also, please check if you enable Encryption in qBittorrent, and check which "transfer protocol" you are using. Also please state if you use a proxy, VPN, and if you have active port forward.)

@kwhat

This comment has been minimized.

Copy link

commented Apr 16, 2018

I am seeing similar behavior from time to time with peer connections. Port forwarding is setup correctly, it would be helpful if I could somehow get logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.