Forwarded port is closed

[bob1324 1]

Hi,
I have a forwarded port, say 22222.
If I test it with:
http://www.yougetsignal.com/tools/open-ports/
I get the message : port 22222 is closed.
I thought it should be open.
I have no connection problems.
Can somebody explain me (a noob) if this is right or wrong.
Thanks

[OpenSourcerer 1450]

Think of a port forwarding rule as a directive for the AirVPN server firewall where connections to an AirVPN exit IP should be routed to. If you don't start an application on the other end (= your computer) listening on that port, the port will remain closed. The port check connects to that port, the firewall forwards that request to your computer on that port and your computer answers if it's open or closed.

[bob1324 1]

If I use Qbittorrent with port 22222 for incoming connections
the port should be opened.
I still get the message that the port is closed.
Qbittorrent works but slow.

[OpenSourcerer 1450]

In its settings > Advanced, change the Bind to interface option to "TAP-Windows Adapter", or the wintun device if you use that.

[bob1324 1]

1 hour ago, OpenSourcerer said:

In its settings > Advanced, change the Bind to interface option to "TAP-Windows Adapter", or the wintun device if you use that.

I always have it "binded", but port stays closed

[NoiselessOwl 26]

did you set the port forwarding on your AirVPN account? If you didn't, then you need to do that. Go to https://airvpn.org/ports/ and set it there. Then the port should be open. If you encounter an error on the port number you want to take, then it is taken and you have to use a different port number.

[bob1324 1]

I have port forwarding  on my airvpn account.
At least 6 years the same port.

[dam448 0]

6 hours ago, bob1324 said:

I have port forwarding  on my airvpn account.
At least 6 years the same port.

Just to test :
- did you try to change the port number in your AirVPN account and qBitorrent settings ?
- to restart/shutdown qBitorrent and restart again ? Edited ... by dam

[bob1324 1]

Tried different port number.
This new port is still closed.
 

[NoiselessOwl 26]

3 hours ago, bob1324 said:

Tried different port number.
This new port is still closed.
 

Have you tried to use a different torrent client to see if qBT is not the issue?

[bob1324 1]

I think I found it.
The public part firewall blocked qBittorrent.
Ticked the right block.
Can somebody tell me if  this is not right?
 

[OpenSourcerer 1450]

6 hours ago, bob1324 said:

The public part firewall blocked qBittorrent.
Ticked the right block.
Can somebody tell me if  this is not right?

Define "public part firewall". What firewall?

[bob1324 1]

Found an English example on internet.

[OpenSourcerer 1450]

Windows Defender Firewall is its name.
So, is it solved?

[bob1324 1]

Yes, I hope so.
I ticked the public part of qBittorent in Windows Defender Firewall .
Not sure if it is the right thing to do.
Maybe yo have an opinion.
Thanks.

[Flx 77]

3 minutes ago, bob1324 said:

Not sure if it is the right thing to do.

Nope.

5 minutes ago, bob1324 said:

Maybe yo have an opinion.

Why the flying ducks are you using Windows Firewall anyway?

[bob1324 1]

9 hours ago, Flx said:

9 hours ago, bob1324 said:

Not sure if it is the right thing to do.

Nope. 

Restored Windows Defender Firewall .
QBittorrent now is only private.
 

9 hours ago, Flx said:

9 hours ago, bob1324 said:

Maybe yo have an opinion.

Why the flying ducks are you using Windows Firewall anyway?

I have a problem and want to solve it.
There must be other user with Airvpn and qBittorrent.
Do they have the same problem?

[OpenSourcerer 1450]

I think it actually was the right thing to do. TAP or wintun adapters are public networks AFAIK. You can check if it's working through AirVPN with the public thing ticked if you go to ipleak.net, click on the Torrent Detection button and open the magnet link with qB. Don't close the tab, though, because after importing it ipleak.net shows you which IP qB is using to contact the tracker on ipleak.net. If it's the same as at the top of the website, i.e., AirVPN exit IP, you're good to go, problem solved.

[bob1324 1]

On 11/10/2020 at 4:21 PM, NoiselessOwl said:

On 11/10/2020 at 12:50 PM, bob1324 said:

Tried different port number.
This new port is still closed.
 

Have you tried to use a different torrent client to see if qBT is not the issue? 

Ihave tried it with BiglyBT and Tixati.
The port is still closed.

[bob1324 1]

21 hours ago, OpenSourcerer said:

I think it actually was the right thing to do. TAP or wintun adapters are public networks AFAIK. You can check if it's working through AirVPN with the public thing ticked if you go to ipleak.net, click on the Torrent Detection button and open the magnet link with qB. Don't close the tab, though, because after importing it ipleak.net shows you which IP qB is using to contact the tracker on ipleak.net. If it's the same as at the top of the website, i.e., AirVPN exit IP, you're good to go, problem solved.

When installing BiglyBT and Tixati I got both times the advice to only open the private part of Windows Defender Firewall and not the public.

[OpenSourcerer 1450]

26 minutes ago, bob1324 said:

When installing BiglyBT and Tixati I got both times the advice to only open the private part of Windows Defender Firewall and not the public.

Advice from whom, Windows? Other clients must be allowed to connect to your client from the internet, that's how BitTorrent works. And the connections don't come from your private LAN. You should tick that box again and then check yourself if qB is talking via the VPN connection by using the torrent address detection feature of ipleak.net. There is simply no use in troubleshooting any further if you configured the firewall to block incoming connections for qBittorrent.

[bob1324 1]

Still having only my private lan ticked on (no public).
Removed air vpn, not using any other vpn.
Started qBittorrent, the incoming port in qBittorent is open in;
http://www.yougetsignal.com/tools/open-ports/
The same for Tixati, the incoming port is open.
QBtorrent and Tixati open the public lan for the incoming port.
No need for manually open the public lan.
Airvpn keeps it closed.

[OpenSourcerer 1450]

1 minute ago, bob1324 said:

Started qBittorrent, the incoming port in qBittorent is open in;

Well, then it's clear you didn't bind qB to TAP, otherwise qB wouldn't be able to connect at all. Check that setting again.