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

Seeders Dissappear When Using Anonymous VPN #9495

Closed
gw1500se opened this Issue Sep 13, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@gw1500se

gw1500se commented Sep 13, 2018

Please provide the following information

qBittorrent version and Operating System

V 3.3.7
CentOS 7

If on linux, libtorrent and Qt version

rb_libtorrent.x86_64 1.0.9-2.el7 @epel
PyQt4.x86_64 4.10.1-13.el7 @base

What is the problem

When downloading a torrent without a VPN connection there are many seeders. When an anonymous VPN connection is established most, if not all, seeders disappear. Most of the time there are no seeders with VPN.

What is the expected behavior

Number of seeders should be the same with or without a VPN connection.

Steps to reproduce

Start downloading a torrent. When more than 0 available seeders is confirmed, establish a VPN connection.

Extra info(if any)

Since this forum question has received no responses I am guessing it must be a bug perhaps related specifically to the CentOS 7 implementation of qBittorrent.

@Seeker2

This comment has been minimized.

Show comment
Hide comment
@Seeker2

Seeker2 Sep 14, 2018

Some seeders may only work using uTP, which uses UDP packets that VPNs may not support well - and some proxies won't support at all.
Some seeders are firewalled. If the VPN or proxy is firewalled as well, a connection between them is difficult (using uTP UDP NAT hole-punching) to impossible.

There are likely bugs in qBitTorrent/libtorrent as well that can prevent connections...likewise the destination seeds may also have other connectivity problems and/or be running buggy BitTorrent.software.

More precise testing of qBT needs to be done (such as on a LAN and even local loopback on 1 computer) to rule out all the possibilities to narrow down whether this is a bug with qBT, the VPN, or other issues are involved.

Seeker2 commented Sep 14, 2018

Some seeders may only work using uTP, which uses UDP packets that VPNs may not support well - and some proxies won't support at all.
Some seeders are firewalled. If the VPN or proxy is firewalled as well, a connection between them is difficult (using uTP UDP NAT hole-punching) to impossible.

There are likely bugs in qBitTorrent/libtorrent as well that can prevent connections...likewise the destination seeds may also have other connectivity problems and/or be running buggy BitTorrent.software.

More precise testing of qBT needs to be done (such as on a LAN and even local loopback on 1 computer) to rule out all the possibilities to narrow down whether this is a bug with qBT, the VPN, or other issues are involved.

@ngosang

This comment has been minimized.

Show comment
Hide comment
@ngosang

ngosang Sep 16, 2018

Member

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

Member

ngosang commented Sep 16, 2018

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

@ngosang ngosang closed this Sep 16, 2018

@gw1500se

This comment has been minimized.

Show comment
Hide comment
@gw1500se

gw1500se Sep 17, 2018

Unfortunately that version is not yet supported on CentOS 7 and I cannot find any compatible RPMs or sources. Version 3.3.7 is all that can be obtained at this time.

gw1500se commented Sep 17, 2018

Unfortunately that version is not yet supported on CentOS 7 and I cannot find any compatible RPMs or sources. Version 3.3.7 is all that can be obtained at this time.

@ngosang

This comment has been minimized.

Show comment
Hide comment
@ngosang

ngosang Sep 17, 2018

Member

Anyway, even if we fix it you won't get it until CentOS updates the package...

Member

ngosang commented Sep 17, 2018

Anyway, even if we fix it you won't get it until CentOS updates the package...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment