ANSWERED Can I expose container ports when using AirVPN Wireguard as default gateway on QNAP

[DarkKman 2]

Hi folks,

So I have a new QNAP NAS with the QVPN Client setup using AirVPN Wireguard set as default gateway. Everything works fine and dandy (once I realised I needed to create a new device in client area... doh!). I have setup a set of containers using Portainer to have an automated set of tools (e.g. SABnzbd, *arrs) to use with my Plex Media Server [PMS] (which is on the QNAP host - not docker). I have the port forwarding all setup for PMS which works fine and dandy too.

My questions are;
1. Can I somehow expose ports in Portainer so I can use port forwarding within docker? The only reason (at the moment) is to get SANnzbd an internet facing port so I can use the "Integration" settings in NZBPlanet so I can manually send movies/tv shows directly to SABnzbd via the internet when not on my local network (I have NoIP DDNS services but guess I could use the AirVPN DDNS instead?) ready to go but when setting up Port Forwarding in AirVPN the ports are closed (as expected I'm sure). If this is possible how would I achieve this in Portainer?
2. If the above *is* possible, and I'm using port redirection in a container e.g. 0.0.0.0:12345->1234/tcp, which port would I use in AirVPN Port Forward page?
3. If this is not possible, is it feasible to try and create a Gluetun/Wireguard connection *within* Portainer? So I assume this would be a Gluetun AirVPN tunnel going through my QNAP host AirVPN connection - is this a thing?
4. If 3. above is possible... umm... is there a guide how I would do this in Portainer? I've seen a few posts here on AirVPN about Gluetun/Wireguard/docker but these are all for stacks which I've not yet really delved into (I'm very new to docker/containers and only did this to get a movie search tool (Radarr) as ,you have to pay for Apache to get it working as a .qpkg in QNAP!

I hope this makes some sense to somebody - I know its a lot to ask but keen to learn and keen to get a setup that feels secure and free from probing eyes as best I can!

Thanks in advance!

***EDIT*** Curiously on my old NAS which I was using to test, I can see that the port forwarding I set up for the container IS being forwarded (tested by using the DDNS:AirVPNport). The difference here being I set up this test container using Container Station (the only GUI setting I see is "Default web URL port:1234" [based on example in point 2 above) and clicked "Publish All Exposed Ports" but no idea if this is related; and I can't achieve this in the new NAS as I don't store my containers storage /config in the default volume... So I can see its possible but just confused how its achieved so help still required please

[DarkKman 2]

UPDATE - 19/05/2025
So it seems that the ports were already configured in Portainer correctly and the only issue being the Port Forwarding in the Client area. Once a port forward was created and  local ports added (along with Device, Protocol and IP Layer) I simply had to "Disable" the port then "Enable" again and all worked... Can't believe it took so long for me to try that but none-the-less all is working as expected!

[Staff 10167]

29 minutes ago, DarkKman said:

I simply had to "Disable" the port then "Enable" again and all worked

Hello!

Thanks for the report. This (the switch Enable/Disable/Enable) should not be necessary, so the problem was unexpected and deserves an investigation, thank you again.

Kind regards