Daniel Mildner 0 Posted ... Hi, I have a strange problem. I have Qbittorrent behind AirVPN with port forwarding setup. Everything is working great on the most trackers. All trackers show me the correct IP address of the airvpn server I'm connected to with the correct port which is forwarded. Also the torrent client itself shows the expected airvpn adress. Only one tracker shows besides the correct ip also another ip a totally other IP Adress with the correct port. So, on this tracker all information is right but the additinal, wrong IP Adress. So, it's impossible to be connectable. The tracker shows 185.39.65.10 as my IP adress, which isn't right. So, two questions: 1. Is this an IP( 185.39.65.10) from any airvpn server ? How can I prevent the false unreachable IP from being created additionally after a couple of minutes. 2. If yes, how could it happen that this adress is shown in the tracker? The adress does not belong to the connected airvpn server on my opinion, nor to my server itself. My connected airvpn server is in switzerland. I read that there might be a rerouting problem. I have already set the "anti-geolocation system" (under "Settings") to "Not active / neutral". However, the problem with the additional, incorrect IP address still exists. Share this post Link to post
Tech Jedi Alex 1489 Posted ... 6 hours ago, Daniel Mildner said: 1. Is this an IP( 185.39.65.10) from any airvpn server ? How can I prevent the false unreachable IP from being created additionally after a couple of minutes. Definitely not AirVPN-related. It belogs to Telepark Passau. Is this your ISP by any chance? 6 hours ago, Daniel Mildner said: 2. If yes, how could it happen that this adress is shown in the tracker? Does something similar happen with IPleak's torrent addess detection? Hide Tech Jedi Alex's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
Daniel Mildner 0 Posted ... (edited) Yes, Telepark Passau is my ISP. But i had the same Problem with my last ISP Telekom. Imo, everything should be fine with IPleak's torrent addess detection I'm connected to a switzerland Airvpn-Server, except for one strange DNS Address Server 94.247.43.254, ( ISP: Lennart Seitz, Germany), which i don't know. The wrong IP (185.39.65.10) doesn't appear. Edited ... by Daniel Mildner Share this post Link to post
Tech Jedi Alex 1489 Posted ... On 7/20/2025 at 9:35 AM, Daniel Mildner said: Yes, Telepark Passau is my ISP. But i had the same Problem with my last ISP Telekom. Hints at your BitTorrent client actually leaking the IP. Is the client bound to the VPN interface? On 7/20/2025 at 9:35 AM, Daniel Mildner said: except for one strange DNS Address Server 94.247.43.254, ( ISP: Lennart Seitz, Germany), which i don't know. Hints at DNS leaks on your machine. What's the contents of /etc/resolv.conf on Linux or the output of ipconfig /all on Windows? Hide Tech Jedi Alex's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
Daniel Mildner 0 Posted ... Thank you. Qbittorrent was leaking the IP. The missing client-VPN Interface bound was the problem. Share this post Link to post