starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

"Use proxy for peer connections" doesn't proxify peer connections #9105

New issue

Closed

opened 2026-02-21 19:59:31 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-21 19:59:31 -05:00

Owner

Originally created by @emanruse on GitHub (Sep 9, 2019).

qBittorrent version and Operating System

4.1.7, openSUSE Leap 15

If on linux, libtorrent-rasterbar and Qt version

1.1.13.0
5.9.4

What is the problem

"Use proxy for peer connections" doesn't proxify peer connections.

What is the expected behavior

It should do what it says.

Steps to reproduce

Set up and start a local tor service
In QBT set Proxy Server Type=SOCKS5, Host=127.0.0.1, Port=9050
Activate also "Use proxy for peer connections"
Monitor connections using:

watch 'ss -tuapn | grep -i qbittorrent | grep -vi 127.0.0.1'

Result:

Actual direct (not proxified) connections to peers are visible, matching the same IP addresses of the seeders and leechers which can be seen in QBT.

Extra info(if any)

Connections to tracker work (through Tor).

"Disable connections not supported by proxies" stops any and all connections (0 B/s). I don't know if this is normal and how to set it correctly in order to fully torify everything. If possible please explain.

Originally created by @emanruse on GitHub (Sep 9, 2019). ### qBittorrent version and Operating System 4.1.7, openSUSE Leap 15 ### If on linux, libtorrent-rasterbar and Qt version 1.1.13.0 5.9.4 ### What is the problem "Use proxy for peer connections" doesn't proxify peer connections. ### What is the expected behavior It should do what it says. ### Steps to reproduce 1. Set up and start a local tor service 2. In QBT set Proxy Server Type=SOCKS5, Host=127.0.0.1, Port=9050 3. Activate also "Use proxy for peer connections" 4. Monitor connections using: ``` watch 'ss -tuapn | grep -i qbittorrent | grep -vi 127.0.0.1' ``` #### Result: Actual direct (not proxified) connections to peers are visible, matching the same IP addresses of the seeders and leechers which can be seen in QBT. ### Extra info(if any) Connections to tracker work (through Tor). "Disable connections not supported by proxies" stops any and all connections (0 B/s). I don't know if this is normal and how to set it correctly in order to fully torify everything. If possible please explain.

deekerman

2026-02-21 19:59:31 -05:00

closed this issue
added the
Proxy/VPN
label

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Sep 9, 2019):

https://legaltorrents.com/tor/#Tor_for_torrenting_4_downsides_you_must_know_about
https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea
https://www.reddit.com/r/TOR/comments/2u3j6m/why_exactly_is_torrenting_over_tor_bad_and_how/
Probably a bad idea to torrent over Tor.

Actual direct (not proxified) connections to peers are visible, matching the same IP addresses of the seeders and leechers which can be seen in QBT.

"Disable connections not supported by proxies" stops any and all connections (0 B/s).

Are those connections over UDP? If yes then it is expected and explained in the above links.

@Chocobo1 commented on GitHub (Sep 9, 2019): https://legaltorrents.com/tor/#Tor_for_torrenting_4_downsides_you_must_know_about https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea https://www.reddit.com/r/TOR/comments/2u3j6m/why_exactly_is_torrenting_over_tor_bad_and_how/ Probably a bad idea to torrent over Tor. >Actual direct (not proxified) connections to peers are visible, matching the same IP addresses of the seeders and leechers which can be seen in QBT. > >"Disable connections not supported by proxies" stops any and all connections (0 B/s). Are those connections over UDP? If yes then it is expected and explained in the above links.

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@emanruse commented on GitHub (Sep 9, 2019):

Are those connections over UDP?

No. TCP - all of them.

@emanruse commented on GitHub (Sep 9, 2019): > Are those connections over UDP? No. TCP - all of them.

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@Seeker2 commented on GitHub (Sep 10, 2019):

Could be related to this probably libtorrent related bug:

http://dev.deluge-torrent.org/ticket/2149 deluge ignoring proxy settings
"I just monitored Deluge with Wireshark and found that Deluge is connecting directly to peers despite having a working proxy. However I have noticed some interesting behavior:
If I change one number in the proxy IP, for example, to a non-working proxy, no downloads work; everything is frozen. So Deluge will only download given a working proxy; it's just not using that proxy."

@Seeker2 commented on GitHub (Sep 10, 2019): Could be related to this probably libtorrent related bug: http://dev.deluge-torrent.org/ticket/2149 deluge ignoring proxy settings "I just monitored Deluge with Wireshark and found that Deluge is connecting directly to peers despite having a working proxy. However I have noticed some interesting behavior: If I change one number in the proxy IP, for example, to a non-working proxy, no downloads work; everything is frozen. So Deluge will only download given a working proxy; it's just not using that proxy."

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@emanruse commented on GitHub (Sep 10, 2019):

If I change one number in the proxy IP, for example, to a non-working proxy, no downloads work; everything is frozen.

That is not a bug. Wrong proxy would result in inability to connect to tracker too, i.e. no way to find the peers.

@emanruse commented on GitHub (Sep 10, 2019): > If I change one number in the proxy IP, for example, to a non-working proxy, no downloads work; everything is frozen. That is not a bug. Wrong proxy would result in inability to connect to tracker too, i.e. no way to find the peers.

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@Seeker2 commented on GitHub (Sep 10, 2019):

You misunderstood the point there -- the poster used that example to demonstrate that Deluge was recognizing the proxy and connecting to it...but Deluge wasn't using the proxy for peer/seed connections!

@Seeker2 commented on GitHub (Sep 10, 2019): You misunderstood the point there -- the poster used that example to demonstrate that Deluge was recognizing the proxy and connecting to it...but Deluge wasn't using the proxy for peer/seed connections!

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Sep 10, 2019):

@emanruse
Seems you have the same symptom as #7734 and there are some discussion going on there currently.

@Chocobo1 commented on GitHub (Sep 10, 2019): @emanruse Seems you have the same symptom as #7734 and there are some discussion going on there currently.

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@emanruse commented on GitHub (Sep 11, 2019):

Seems you have the same symptom as #7734 and there are some discussion going on there currently.

Only in the part relating to the "Extra info" (2nd paragraph) in the OP. I don't have the [general] symptom of "No connections when using a Socks5 proxy server" listed in that other issue. As I explained: there are connections to tracker (proxified) and to peers (not proxified) as long as "Disable connections not supported by proxies" is off.

In short: it looks related but not "the same" as the that other issue.

@emanruse commented on GitHub (Sep 11, 2019): > Seems you have the same symptom as #7734 and there are some discussion going on there currently. Only in the part relating to the "Extra info" (2nd paragraph) in the OP. I don't have the [general] symptom of "No connections when using a Socks5 proxy server" listed in that other issue. As I explained: there *are* connections to tracker (proxified) and to peers (not proxified) as long as "Disable connections not supported by proxies" is off. In short: it looks related but not "the same" as the that other issue.

deekerman commented

2026-02-21 19:59:33 -05:00

Author

Owner

@ghost commented on GitHub (May 4, 2022):

AFAIK this IP leak was fixed in RC1_2 of libtorrent. Feel free to comment to re-open it if you're still facing with latest version.

@ghost commented on GitHub (May 4, 2022): AFAIK this IP leak was fixed in RC1_2 of libtorrent. Feel free to comment to re-open it if you're still facing with latest version.