ANSWERED I've tried everything and I don't know, Open port, pfSense

[drneba 0]

I followed this guide https://nguvu.org/pfsense/pfsense-port-forward/
My configuration: pfSense + Unraid with qBittorrent container
Everything works for me, AirVPN connects to the server, Unraid server gets the VPN IP address, but when I check if the port is open I get an error.


Firewall / Rules / WAN


Firewall / Rules / AIR_SRB


TorrentHost - IP address of Unraid server
TorrentInboundPort - port I got from the AirVPN site

Port Forward






Any help would be great, I'm really tired


 

[go558a83nk 371]

Everything looks correct.  The two things I wonder are:  1) are the external and internal ports matching for the port forward you created with AirVPN?  By default they do match but just making sure.  2) Have you reconnected the VPN connection since making the port forward rule?  Often that's required.

[drneba 0]

  On 8/18/2024 at 1:04 PM, go558a83nk said:

1) are the external and internal ports matching for the port forward you created with AirVPN?  By default they do match but just making sure.

What exactly do you mean, I created an alias with the port assigned to me on AirVPN.

  On 8/18/2024 at 1:04 PM, go558a83nk said:

2) Have you reconnected the VPN connection since making the port forward rule?  Often that's required.

Did you mean to do a reconnect here?


 

[invok3r 3]

I dont know if its just openVPN things or not but i'd suggest (if you can) to try using wireguard. Im sure the ports will work and be open. 

[drneba 0]

  On 8/21/2024 at 12:18 AM, invok3r said:

I dont know if its just openVPN things or not but i'd suggest (if you can) to try using wireguard. Im sure the ports will work and be open. 

Thanks, that's what I was thinking of trying. I have to make some time for that

[drneba 0]

  On 8/21/2024 at 12:18 AM, invok3r said:

I dont know if its just openVPN things or not but i'd suggest (if you can) to try using wireguard. Im sure the ports will work and be open. 

Unfortunately it doesn't work with Wire Guard either. Obviously I don't know. I'm so tired of everything.

[drneba 0]

I found this thread, but it's locked, Could someone please explain this to me
"The problem was an any/any rule in the Wireguard unasigned tunnel firewall rule list. Even though the AirVPN WG interface was assigned, group rules are evaluated first..."

 

[go558a83nk 371]

  On 8/24/2024 at 7:03 PM, drneba said:

I found this thread, but it's locked, Could someone please explain this to me
"The problem was an any/any rule in the Wireguard unasigned tunnel firewall rule list. Even though the AirVPN WG interface was assigned, group rules are evaluated first..."

 

so they're saying they had an any/any rule in their firewall/rules/openvpn or /firewall/rules/wireguard group which overrode the automatically created rule (when you create the port forward) in firewall/rules/individual_interface

[drneba 0]

So both of those rules should be empty.
It's the same with me and it still doesn't work

[go558a83nk 371]

  On 8/24/2024 at 7:28 PM, drneba said:

So both of those rules should be empty.
It's the same with me and it still doesn't work

yeah, for me the group rules section is empty.  but the individual interface gets auto created by using the associated filter rule option in the port forward.

your problem may be due to a firewall on the unraid box and/or the qbit container?

[drneba 0]

when a port is opened on pfsense, does say yougetsignal.com have to show that the port is open, regardless of what is after pfsense

[go558a83nk 371]

  On 8/24/2024 at 7:49 PM, drneba said:

when a port is opened on pfsense, does say yougetsignal.com have to show that the port is open, regardless of what is after pfsense

Neither AirVPN's port open test nor yougetsignal's port open test will show "green" unless your whole chain is working and your server (qbit) is listening and responds to the query.  This is important.  Your server must be up and responding.  So if things seem correct on pfsense then then problem is somewhere else, that's my thought.

[drneba 0]

That's right, you're 100% right.
The entire chain must be active and set to an open port. Everything works for me on a Windows machine and finally it tells me that the port is open. It is important to me that I have done the pfSense settings correctly. Now I will solve Unraid. A thousand times thanks.