QBittorent is Not listening on the selected port when using a socks5 proxy set up to work with Mullvad

[WIlllKilll]

Please provide the following information

qBittorrent version and Operating System

v4.04 - Window 10 pro x64 version 1709

If on linux, libtorrent and Qt version

(type here)

What is the problem

QBittorent is not listening on the selected port when using a socks5 proxy as set up to work with Mullvad VPN. When socks5 is disabled seeds connect and connections occur.

https://mullvad.net/en/guides/socks5-proxy/

Qbittorrent

1.  Click on Tools followed by Options (Alt-O).
2.  Click on Connection.
3.  Cl ick on BitTorrent
4.  Enable (Check) Enable anonymous mode
5.  Disable (Uncheck) Enable DHT
6.  Disable (Uncheck) Enable PeX
7.  Disable (Uncheck) Enable Local peer discovery
8.  Click on Connection
9.  For Enabled protocol: Use the drop-down bar and select TCP
10. Under Proxy Server change Type to SOCKS5.
11. Change Host: to 10.8.0.1.
12. Change Port to 1080.
13. Checkmark the box next to use proxy for peer connections.
14. Checkmark the box next to Disable connections not supported by proxies.
15. Disable (Uncheck) Use PNP / NAT - PMP
16. Click on Connection

What is the expected behavior

Socks5 should allow Torrents to connect to trackers and receive peer and seed info and allow connection to peers.
I have also allowed DHT for trackerless magnets with no diffference when togging this setting.

Steps to reproduce

Please see setup instruction above.

Extra info(if any)

This has been an issue on the past on other builds is it the build or configuration?

[Supralateral]

SOCKS is a proxy, which means your data is being seeded from y.y.y.y:yyyyy (the VPN's network) instead of x.x.x.x:xxxxx (your local public network). Your announces are coming from y.y.y.y:yyyyy, and other leeches in the swarm are trying to connect to y.y.y.y:yyyyy. So, qBittorrent's listening port (xxxxx) is useless.

There's no way qBittorrent can manage this on its own, SOCKS5 basically ensures closed ports, which highly restricts your capacity to seed. Port forwarding with SOCKS is complicated and I don't think it's something Mullvad provides: https://debian-administration.org/article/449/SSH_dynamic_port_forwarding_with_SOCKS

You should still be able to download with SOCKS, and some uploading can still occur, but don't expect to upload any significant amount of data with the SOCKS proxy enabled. If you need to seed through a proxy, consider using a systemwide proxy. Mullvad offers port forwarding in their client, which proxies your entire system network through their services.

[xavier2k6]

Thanks for the report, unfortunately it's too old a version now.
If you can reproduce this in latest 4.3.3, please create a "new issue"