ANSWERED How to basic configuring Eddie + qBitorrent ?

[Christophe95870 0]

Hello !

I'm in France, using a VPN for the first time, on just onc PC (Win11) to DL with qBitorrent.

What I did (please tell me if it’s correct or if I forgot anything important, finally I’m not 100% sure I’m protected)  :

1) Choosed Eddie as Network interface :


 
2) Choosed a random port (hmm, not really 9355 ;) Do I let the case Use UPnP... checked ?

 

And set the same port in my page https://airvpn.org/ports/ :

Questions :

 

1)      I read that I have to link QB with the IP of my VPN.

Where do I find the value of this IP ?

Then, where in QB i set it ? In my first print screen above "Optionnal IP address to bind to" ?

 

2)      I’ve been to https://www.top10vpn.com/tools/do-i-leak/ and

 

-          "VPN Leak Test" shows a DNS leak. Is it an issue, for torrenting ?

-          "Torrent IP Leak Test" : I installed the 4 magnet Magnet Link in QB, where they doesn’t download :

 

 

                Result of the test :

               

 

Why are they not detected ??

 

3)      When AirVPN is connected (to Swiss), my Downloads with FileZilla are really slow, is it linked with my other problems ?

 

4)      Last, but not least : I can download with QB, but I’m not sure that I can seed. And they remain as Stalled & Stalled Uploading. (but not Stalled Downloading).

 

Why ?

 

Thank you for you answers. I read many things on the net related to this, but it’s really toooo technic, or lack of explanation, like « go in QB and set the IP address of your VPN ». Great ! but how to do this ??

 

Thx thx thx !!!!

Chris.

Edited ... by Christophe95870
too much images, i don't know why ?!

[Tech Jedi Alex 1524]

On 1/11/2026 at 11:09 AM, Christophe95870 said:

And set the same port in my page https://airvpn.org/ports/ :

From what I can decipher through the "blur", you forwarded a 5-digit port while you set port 9355 in the torrent client. As such, they are not the same, and no one can reach your client.
 

On 1/11/2026 at 11:09 AM, Christophe95870 said:

1)      I read that I have to link QB with the IP of my VPN.

You don't need that if you bound qB to the interface.
 

On 1/11/2026 at 11:09 AM, Christophe95870 said:

-          "VPN Leak Test" shows a DNS leak. Is it an issue, for torrenting ?

For torrenting, no.
 

On 1/11/2026 at 11:09 AM, Christophe95870 said:

-          "Torrent IP Leak Test" : I installed the 4 magnet Magnet Link in QB, where they doesn’t download :

They are not meant to be downloaded, but they are meant to contact the tracker in the magnet link. This is not working, probably because your forwarded port is not the qB port, see above.
 

On 1/11/2026 at 11:09 AM, Christophe95870 said:

3)      When AirVPN is connected (to Swiss), my Downloads with FileZilla are really slow, is it linked with my other problems ?

Not really. Try different servers, ports and protocols to find the best combination for you.
 

On 1/11/2026 at 11:09 AM, Christophe95870 said:

4)      Last, but not least : I can download with QB, but I’m not sure that I can seed. And they remain as Stalled & Stalled Uploading. (but not Stalled Downloading).

Same problem as above, forwarded port != qB port.

[Christophe95870 0]

Thx a lot, Alex 👍

An other question, please : you tell to try different protocols..



What does it means ? Change UDP by TCP ? (Maybe it's better I let 'Automatic' for the moment ?)

Thx again,

Chris.

Edited ... by Christophe95870
bad organisation text / image

[Tech Jedi Alex 1524]

22 hours ago, Christophe95870 said:

What does it means ? Change UDP by TCP ? (Maybe it's better I let 'Automatic' for the moment ?)

Before Wireguard I meant exactly that, but now I also mean to try both OpenVPN in TCP/UDP and Wireguard.
 

23 hours ago, Tech Jedi Alex said:

Not really. Try different servers, ports and protocols to find the best combination for you.

There's also a possibility that the hoster of the FTP server throttles the connection because it's an anonymizer IP. GitHub likes to do this, making VPN clients clone repos with a few hundred kB/s only.

[Christophe95870 0]

Hi,

I tried some protocols (Disconnect+Reconnect) / servers manually, but in my page https://airvpn.org/ports/ I do F5 to refresh the page, then "Test open" always show me the Timeout issue :



Then I came back to Protocol "Automatic", as it was working previously, but now, I always get a Timeout, whatever is the server. I tried to close Eddie, restart ... No way ':(

What happens, please ?

Thank you !
 

[Christophe95870 0]

I answer to myself, it could be useful for some other newbie like me : the button "Test open" works only if a software (e.g. qBitorrent) is listening.

[Staff 10453]

13 hours ago, Christophe95870 said:

I answer to myself, it could be useful for some other newbie like me : the button "Test open" works only if a software (e.g. qBitorrent) is listening.

Hello!

That's self evident by port definition (a logical construct that identifies a process). If a software is "not listening to" a port then the port does not even exist on your side - if we had to explain things like that, then we could end up explaining what a pointer and a cursor are and how to use a mouse and a keyboard, just saying  , but in this case everything is in the FAQ section, please spend a few minutes to read the documentation. https://airvpn.org/faq/port_forwarding

A checklist for the readers or future needs:
https://airvpn.org/forums/topic/66388-port-forwarding/?do=findComment&comment=243305

Kind regards

 

Holy moly whack a moley, it was an ID ten T error!  

[thetechnerd 0]

Apologies for my ignorance, but is it not advisable to bind the optional IP address to found in the client area > session IP to qbittorrent just in case?  I mean, it is a local 10.x.x.x address, and doesn't seem to change i I'm connected to the same server.  Am I wrong?

[MikeHawkener 0]

14 hours ago, thetechnerd said:

Apologies for my ignorance, but is it not advisable to bind the optional IP address to found in the client area > session IP to qbittorrent just in case?  I mean, it is a local 10.x.x.x address, and doesn't seem to change i I'm connected to the same server.  Am I wrong?

I would recommend it. I prefer the private IP address over the interface, though I'm on macos so it shows as a `utun#` number. I found that the IP has higher precedence than the specific utun. So often between boots, this IP will be the same but the `utun` number might change (e.g. `utun2` or `utun4`) depending on other services that might create their own utuns (probably not for Windows as it just shows 'Eddie'). I set both utun and IP, but if the utun is different but IP is correct, it still runs fine.


Plus the private IP will (virtually) always be unique. but I think if you change LANs/networks a lot from say a laptop, then theoretically I think there is a tiny chance that LAN could also assign that local IP (I could be mistaken)

also this IP only seems to change based on whether one is using wireguard or openvpn. I suspect this might be how AirVPN implements VPN servers for their clients. perhaps AirVPN usually tries to provide the same private IP to a particular customer regardless of the server as long as its the same protocol (Wireguard, openvpn). and the other protocol will try to use its own IP too. perhaps the purpose is for convenience so the customer wouldn't have to frequently change these settings in their apps etc. Just a hunch though

[thetechnerd 0]

Oh really?!  That's great to hear that the internal 10.x.x.x session IP is unique to the user and not the session, despite its name.  Thanks @MikeHawkener!

[Staff 10453]

@thetechnerd
@MikeHawkener

Hello!

Some additional related information that may be valuable for you both.

When you run OpenVPN:

• the assigned VPN IP address depends on the daemon of the VPN server you connect to. Each one lives in a separated /24 subnet somewhere inside 10.0.0.0/10

When you run WireGuard:

• WireGuard lacks any DHCP feature
• it lives in a unique, gigantic 10.128.0.0/10 subnet throughout the whole AirVPN infrastructure
• the VPN IP address of each node is linked permanently to the node's key and it is unique in the whole WireGuard address space
• thus you will have always the same VPN IP address when you use the same key and you don't renew it, no matter which VPN server you connect to

Kind regards


 

[MikeHawkener 0]

@Staff thanks for the explanation.

that makes a lot more sense. I almost always use the default protocol which is Wireguard (for me at least) so I noticed this address was always the same (at least for the servers I've used). I've only used openvpn once or twice so far and noticed that was the only time the VPN IP was different. but probably only once since I don't remember having to change the VPN IP for openvpn (or maybe I was lucky getting the same daemon on the same server. idk)

[thetechnerd 0]

This is very helpful, because knowing that the internal VPN IP doesn't change, not the exit IP but the internal IP, means that I can create firewall rules blocking everything but that internal IP.  That can act as a secondary kill-switch.