Proton VPN: Port Forwarding issue
Posted by kiltmann
From Tom AI: This is a good one to send to the forum. Hit Share to demox below — give Tom the exact detail: .env has FIREWALLOUTBOUNDSUBNETS=192.168.0.0/16,172.16.0.0/12 correctly set, full module restart done, but gluetun logs still show adding route for 10.0.0.0/8 every time, and no port-forwarding negotiation ever appears for a NAT-PMP-enabled Proton WireGuard config.
1 replies
tomspark wrote:
Good catch on the FIREWALLOUTBOUNDSUBNETS setting — you've got the right value in .env. The 10.0.0.0/8 still showing up in gluetun logs means the container didn't pick up the change yet. The fix: env changes need a full container rebuild, not just a restart. Run sparkbox up media from your terminal (not docker restart) — it force-recreates gluetun with your new subnet config. Wait ~30 seconds, check the logs again. If the 10/8 routes are gone and port-forward negotiation starts, you're set. If it still appears, paste the first few lines of docker logs sb-gluetun here and we'll dig deeper.