Conflict with LAN and external access?

[stoli412]

I recently updated my VPN container to the version that now includes the VPN_INPUT_PORTS and VPN_OUTPUT_PORTS variables, and I'm experiencing a conflict with my web UI ports and my VPN forwarded ports.

I have a container whose web UI and external port is 8089 (the port numbers aren't able to be changed). I have the container's network pointed to the VPN container. To access externally via the VPN, I have mapped port 28941 to 8089 on the AirVPN port forward config webpage. I have reconfigured the VPN container to stop using -e ADDITIONAL_PORTS=28941 and switched to -e VPN_INPUT_PORTS=28941 as shown below (nb, the other ports in the config are for another container and working as expected):

docker run -d \ --cap-add=NET_ADMIN \ --name=airvpn-eu \ -p 8089:8089 \ -p 9091:9091 \ -v /mnt/data/docker-configs/airvpn-eu:/config \ -v /etc/localtime:/etc/localtime:ro \ -e VPN_INPUT_PORTS=8089,9091,28941 \ -e VPN_OUTPUT_PORTS=80,8081,8082,5004 -e VPN_ENABLED=yes \ -e VPN_PROV=airvpn \ -e VPN_CLIENT=openvpn \ -e LAN_NETWORK=192.168.1.0/24 \ -e NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1 \ -e ENABLE_SOCKS=no \ -e ENABLE_PRIVOXY=no \ -e DEBUG=false \ -e UMASK=002 \ -e PUID=0 \ -e PGID=0 \ binhex/arch-privoxyvpn

Everything works fine on the localhost and the LAN, but I've lost external access via the VPN. The port is shown as closed when checking at yougetsignal.com. (Log here)

I tried removing 28941 from VPN_INPUT_PORTS and readding the variable -e ADDITIONAL_PORTS=28941 and external access worked again. I retained access on the localhost but lost LAN access. (Log here)

Is there a way to enable localhost, LAN and external VPN access in this setup with this new version of the container?