AirVPN "Your forwarded ports" - connection timed out

[bdika 1]

I have the following set up:

ISP Modem --> Protectli(OPNsense-AirVPN Wireguard) --> Netgear R7000 Access Point(Fresh Tomato) --> My Lan (of which there is one hardwired computer running an apache webserver)

I have a nextcloud instance running on the apache webserver. I want to be able to access the nextcloud instance remotely.

OPNsense has an option available for various Dynamic DNS (DDNS) services. I had the DDNS service for duckdns working and I could access my nextcloud server remotely before I changed to AirVPN as my VPN (I was using Mulvad).

Now I want to accomplish the same thing with AirVPN without using duckdns but by using AirVPN's DDNS.

The problem is that I cannot even get started. When I go to the AirVPN ports page, click on "Request a new port" and then click on "Test open". The connection times out (110) for TCP but seems to work for UDP (at least I don't see any error for UDP). This happens regardless of whether I leave the local port empty, fill in the local port with the same port number as the assigned port or use port 80 for the local port. Also it doesn't matter if I fill in the xxxx.airdns,org or not. "CanYouSeeMe" reports the ports as closed for for all my attempts. I have tried this on my local internet as well as on my cell phone data plan without any difference.

I feel like I am missing something fundamental but have no idea what it is.

Any help would be much appreciated.

Thanks.

bdika

[OpenSourcerer 1441]

In OPNsense you must create another port forward, the random port from OPNsense to 80/443 or so on the Netgear router, otherwise you're trying to reach a thing running on OPNsense on that random port.

[bdika 1]

Hi OpenSourcerer:

Thanks for responding.

It turns out that this is a bug in OPNsense with wireguard. See here.

I tried to follow the suggestion in that post but still cannot get port 80 open without reference to AirVPN.

I will look for help in the OPNsense forum.

Thanks again.

bdika