Gluetun, WireGuard, and ProtonVPN: The Hard Guide to Port Forwarding Without Blowing Up Your Docker Stack
The current best practice demands coupling `qbittorrent` with `gluetun` using a specific container setup. This requires enforcing startup readiness via `depends_on: condition: service_healthy` and adding mandatory healthchecks to `gluetun` itself.
Debate raged over VPN stability. Some pointed to AirVPN keeping static ports, while others fixated on ProtonVPN, despite initial setup friction. Key contributors drove the technical specifications: `hyphen612` pushed for WireGuard over OpenVPN and a specific port-forwarding success dependency loop. Meanwhile, `Scrath` validated the service healthcheck mechanism as the fix for startup failures. `Flatworm7591` claimed a flawless configuration using WireGuard, Docker Mods (GSP), and Proton, while `muusemuuse` dismissed BiglyBT outright, calling it an inherently slow, Java-based I2P mess.
The consensus technical path is clear: use `gluetun` with `service:gluetun`. The persistent conflict lies in the VPN choice—the community is split between testing proven protocols and accepting the difficulty of advanced providers like ProtonVPN to achieve port forwarding.
Key Points
Container orchestration must use `gluetun` with `service:gluetun` network mode.
This is cited as the core best practice for the entire setup.
Startup reliability hinges on strict dependency management.
`Scrath` and others confirmed that implementing `depends_on: condition: service_healthy` resolved critical container startup failures.
WireGuard is favored over OpenVPN for the connection layer.
`hyphen612` explicitly recommended WireGuard within the Gluetun context.
ProtonVPN is the current focal point despite configuration complexity.
`Flatworm7591` provided an alleged 'flawless' method with Proton, while initial setups were noted as difficult.
BiglyBT should be avoided due to technical limitations.
`muusemuuse` stated it is an 'I2P and Java-based solution' whose performance drawbacks are fundamental.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.