cubesmi 0 Posted ... (edited) Hi! I'm struggling with gluetun port forwarding to another container. In order to debug my setup I came up with following docker compose which sets up a simple nginx webserver and VPN port forwarding. 'wget localhost:80' from inside the gluetun container works 'wget <host-ip>:29099' from LAN works as well, if I expose 29099:80 in the gluetun container Can anyone spot the flaw in following setup? Thanks in advance 🙂 version: "3" services: gluetun-v1: image: qmcgaw/gluetun:v3.33 container_name: gluetun-v1 cap_add: - NET_ADMIN environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY=xxx - WIREGUARD_PRESHARED_KEY=xxx - WIREGUARD_ADDRESSES=10.147.182.65/32 - SERVER_REGIONS=Europe - FIREWALL_VPN_INPUT_PORTS=29099 nginx: image: nginx container_name: nginx-v1 network_mode: service:gluetun-v1 Cheers, cubesmi Edited ... by cubesmi Quote Share this post Link to post
OpenSourcerer 1441 Posted ... Split from: Please describe your own issue, what you've tried and where you're stuck. Your setup is different and might have a different core issue than the one you refer to. Quote Hide OpenSourcerer's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
plaidy 0 Posted ... (edited) I just set up airvpn with gluetun today. I was using Mullvad previously and have always had the ports defined in the container. You probably need to add this to the gluetun container's compose: ports: - 29099:80 - 29099:80/udp Edited ... by plaidy Quote Share this post Link to post
Unleash9823 0 Posted ... You change the port on the VPN server side from 29099 to 80, which is then forwarded to your server with docker running on. I would assume the correct environment variable setting would be FIREWALL_VPN_INPUT_PORTS=80 as the traffic arrives at port 80 at your machine. Quote Share this post Link to post
cubesmi 0 Posted ... This exposes the web server port through the gluetun container on the host machine, unfortunately this doesn't solve the issue; the web server is still not accessible via the public airvpn ip address 😞 Quote Share this post Link to post
barnabus 0 Posted ... Hey - has anybody figured this out yet? I'd like to get this set up as well. Quote Share this post Link to post
48oift]h[ow94]8q2w3l 0 Posted ... Did anyone solve this yet? I have the exact same setup issue with Nginx and Gluetun. Works fine locally but can't get it to work remotely Quote Share this post Link to post
Staff 10014 Posted ... 11 hours ago, 48oift]h[ow94]8q2w3l said: Did anyone solve this yet? I have the exact same setup issue with Nginx and Gluetun. Works fine locally but can't get it to work remotely Hello! Yes, various users found the problem in their configuration, you may check whether their solutions are applicable for your case too:https://airvpn.org/forums/topic/56370-portforwarding-not-working-gluetun-and-desktop-app/?tab=comments#comment-223375https://airvpn.org/forums/topic/56288-proper-way-to-set-up-airvpn-wireguard-with-portforwarding-in-a-docker-with-gluetun-on-nas/?tab=comments#comment-222853 Also consider to contact Gluetun community as Gluetun supports AirVPN. Kind regards Quote Share this post Link to post