starred/qBittorrent

Fork 0

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

qBittorrent leaking IP address even when connected to NordVPN (and Network Interface and Optional IP address binding set to VPN) #17022

New issue

Open

opened 2026-02-22 03:36:43 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-22 03:36:43 -05:00

Owner

Originally created by @neurozero on GitHub (Jul 15, 2025).

qBittorrent & operating system versions

qBittorrent: v5.1.0
OS: Windows 10
VPN: NordVPN
Router: Linksys Smart Wi-fi (wired connection)

What is the problem?

Settings:
CONNECTION
Peer connection protocol: TCP and uTP
Use UPnP / NAT-PMP port forwarding from my router: enabled (disabled gives the same issue)
Proxy Server Type: None

BITTORRENT
Enable DHT (decentralized network) to find more peers: disabled
Enable Peer Exchange (PeX) to find more peers: disabled
Enable Local Peer Discovery to find more peers: disabled
Encryption mode: Allow encryption
Enable anonymous mode: disabled (enabled doesn't change anything)

ADVANCED
Network interface: NordLynx
Optional IP address to bind to: 10.5.0.2 (NordLynx Tunnel Adapter IP)

At ipleak.net my IP address is shown as whatever NordVPN is assigning to me, however
When I use the Torrent Address detection on ipleak.net my real IP address is shown for the test torrent.

Occasionally it will show a different IP address when I change some settings, but more often than not it is just showing my real IP address.

I tried Transmission just to test the ipleak test torrent and it only sees my NordVPN IP address.

I've been trying to use NordVPN Proxy Server but it won't always connect (SOCKS5 proxy error, Message: "End of file").

I don't know what else to try at this point.

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

In the log:
7/15/2025 10:26 AM - Detected external IP. IP: "185.153.179.$$$" [Not my IP, NordVPN IP]
7/15/2025 10:19 AM - Successfully listening on IP. IP: "10.5.0.2". Port: "UDP/21249"
7/15/2025 10:19 AM - Successfully listening on IP. IP: "10.5.0.2". Port: "TCP/21249"
7/15/2025 10:19 AM - Successfully listening on IP. IP: "fe80::723e:7ca:789d:$$$$$$". Port: "UDP/21249"
7/15/2025 10:19 AM - Successfully listening on IP. IP: "fe80::723e:7ca:789d:$$$$$$". Port: "TCP/21249"

Originally created by @neurozero on GitHub (Jul 15, 2025). ### qBittorrent & operating system versions qBittorrent: v5.1.0 OS: Windows 10 VPN: NordVPN Router: Linksys Smart Wi-fi (wired connection) ### What is the problem? Settings: **CONNECTION** Peer connection protocol: **TCP and uTP** Use UPnP / NAT-PMP port forwarding from my router: **enabled** (**disabled** gives the same issue) Proxy Server Type: **None** **BITTORRENT** Enable DHT (decentralized network) to find more peers: **disabled** Enable Peer Exchange (PeX) to find more peers: **disabled** Enable Local Peer Discovery to find more peers: **disabled** Encryption mode: **Allow encryption** Enable anonymous mode: **disabled** (**enabled** doesn't change anything) **ADVANCED** Network interface: **NordLynx** Optional IP address to bind to: **10.5.0.2** (NordLynx Tunnel Adapter IP) At ipleak.net my IP address is shown as whatever NordVPN is assigning to me, **however** _When I use the Torrent Address detection on ipleak.net my **real IP address** is shown for the test torrent._ Occasionally it will show a different IP address when I change some settings, but more often than not it is just showing my real IP address. I tried Transmission just to test the ipleak test torrent and it only sees my NordVPN IP address. I've been trying to use NordVPN Proxy Server but it won't always connect (SOCKS5 proxy error, Message: "End of file"). I don't know what else to try at this point. ### Steps to reproduce _No response_ ### Additional context _No response_ ### Log(s) & preferences file(s) In the log: 7/15/2025 10:26 AM - Detected external IP. IP: "185.153.179.$$$" [Not my IP, NordVPN IP] 7/15/2025 10:19 AM - Successfully listening on IP. IP: "10.5.0.2". Port: "UDP/21249" 7/15/2025 10:19 AM - Successfully listening on IP. IP: "10.5.0.2". Port: "TCP/21249" 7/15/2025 10:19 AM - Successfully listening on IP. IP: "fe80::723e:7ca:789d:$$$$$$". Port: "UDP/21249" 7/15/2025 10:19 AM - Successfully listening on IP. IP: "fe80::723e:7ca:789d:$$$$$$". Port: "TCP/21249"

deekerman added the

Proxy/VPN

label

2026-02-22 03:36:43 -05:00

deekerman commented

2026-02-22 03:36:48 -05:00

Author

Owner

@neurozero commented on GitHub (Jul 16, 2025):

I updated the title. This seems to be specific to NordVPN. No issues with ProtonVPN or Private Internet Access.

@neurozero commented on GitHub (Jul 16, 2025): I updated the title. This seems to be specific to NordVPN. No issues with ProtonVPN or Private Internet Access.

deekerman commented

2026-02-22 03:36:48 -05:00

Author

Owner

@noelbautista91 commented on GitHub (Aug 9, 2025):

Confirming with NordVPN. I've also tried Anonymous mode on qbittorrent, it made no difference.

Interestingly both my real IP and NordVPN IP are exposed.

@noelbautista91 commented on GitHub (Aug 9, 2025): Confirming with NordVPN. I've also tried Anonymous mode on qbittorrent, it made no difference. Interestingly both my real IP and NordVPN IP are exposed.

deekerman commented

2026-02-22 03:36:48 -05:00

Author

Owner

@Autori commented on GitHub (Aug 10, 2025):

Perhaps related #22834

I made a workaround for my issue using firewall, blocking outbound from qbittorrent app from LAN IP range. Some features aren't working because they don't use the binding ( see #22844 ).

@Autori commented on GitHub (Aug 10, 2025): Perhaps related #22834 I made a workaround for my issue using firewall, blocking outbound from qbittorrent app from LAN IP range. Some features aren't working because they don't use the binding ( see #22844 ).

deekerman commented

2026-02-22 03:36:48 -05:00

Author

Owner

@yeahmyusernameis32characterslong commented on GitHub (Aug 26, 2025):

This is going to be Nord or OS specific, so if your VPN is leaking your real IP, run your torrent app in Docker and route it through a separate VPN container. Spin up a VPN container like Gluetun using WireGuard, then make your torrent container use the VPN container network. That forces all traffic from the app through the tunnel and if the VPN drops the app loses internet, so no leaks and if the data wants to use another method to get out like you are experiencing, it can't. DNS goes through the VPN and you can enable port forwarding if your provider supports it. Keeps the rest of your system off the VPN (you can add other docker containers for other apps to go through the VPN container). If needed, I can show a simple compose setup to link them.

@yeahmyusernameis32characterslong commented on GitHub (Aug 26, 2025): This is going to be Nord or OS specific, so if your VPN is leaking your real IP, run your torrent app in Docker and route it through a separate VPN container. Spin up a VPN container like Gluetun using WireGuard, then make your torrent container use the VPN container network. That forces all traffic from the app through the tunnel and if the VPN drops the app loses internet, so no leaks and if the data wants to use another method to get out like you are experiencing, it can't. DNS goes through the VPN and you can enable port forwarding if your provider supports it. Keeps the rest of your system off the VPN (you can add other docker containers for other apps to go through the VPN container). If needed, I can show a simple compose setup to link them.