OS version: W10 Pro
I did not see a fix for this problem in the changelog for upcoming versions
When bound to a specific network interface (VPN), some trackers are still announced over the default network interface causing another IP to bleed to the tracker. Not all trackers continue to work but a lot keep working (did not find a difference for http/https)
Bind qBittorrent to a disconnected interface (VPN, but disconnected) and restart qBittorrent for changes to take effect. This should mean no network traffic to trackers and therefore announces must fail.
Add a list of torrents with various trackers as it's only a fraction of trackers that announce outside of the bound interface.
Check which trackers report a working announcement and check with those trackers to see what IP is reported.
When a firewall rule is made to block qBittorrent and that rule applied only to the not-bound interface while the bound interface (VPN) is disconnected, then all trackers fail. If the bound interface is connected then all trackers succeed. The firewall log still shows a lot of connections through the not-bound interface.