cross-posted from: https://lemmy.dbzer0.com/post/19035305
[Promoting] Gluetun: The Little VPN Client That Could
My journey with docker started with a bunch of ill fated attempts to get an OpenVPN/qBittorrent container running. The thing ended up being broken and never worked right, and it put me off of VPN integration for another year or so.
Then recently I found Gluetun…and holy fucking cow. This thing is the answer to every VPN need I could possibly think of. I have set it up with 3 different providers now, and it has been more simple and reliable than the clients made by the VPN providers themselves every time.
If you combine the power of Gluetun with the power of Portainer, then you can even easily edit settings for your existing containers and hook them up to a VPN connection in seconds (or disconnect them). Just delete the forwarded ports in the original container, select the Gluetun container as the network connection, and then forward the same ports in Gluetun. Presto, you now have a perfectly functioning container connected to a VPN with a killswitch.
So if any of y’all on the high seas have considered getting more serious about your privacy, don’t do what I did and waste a bunch of time on a broken container. Use Gluetun. Love Gluetun. Gluetun is the answer.
100% agree. gluetun solved my vpn bleeding/failure problems.
Just wondering, but I’m seeing a lot of simple networking questions around here lately, and the majority about people not understanding how VPNs or networks work in general. Have we just reached the point where everything needs to be abstracted away because people don’t understand interfaces, networks, and routing between them now?
Not talking smack, just trying to understand why these questions are so prominent now, so my guess is the above.
A lot of reasonably competent geeks just never get deep into networking, and VPNs can be overwhelming. It doesn’t really help that for a long time it was all IPSec which basically you need to learn voodoo to manage. Thankfully we have much better tools now, but it’s still just a tech layer that many people don’t touch frequently.
I think the questions are more prominent because a wider audience of people are becoming more privacy conscious.
In my case, I haven’t had the advantage of going to school for any of this, so I have to pick up knowledge where I can. If there is a reliable tool available to accomplish my task, I’m more likely to use it than to pursue a more manual solution because even simple computing questions can be rabbit holes that result in hours of reading and learning.
The reason that I made this post is because your options are always limited by your awareness of available solutions, and I presumed there might be someone else out there who has struggled getting a VPN reliably bound to a service.
You don’t need portainer for it to be easy! The wiki is quite great at providing setup examples for docker compose, regular docker, and others!
Indeed! There are many simple and quality ways to set it up, and users can pick anything they prefer. FOSS is dope like that.
I just did it! Thank you so much! I failed so many times in the past but this took a few hours and now I have that perfect setup that I always wanted.
I’m so glad this post helped somebody!
Based. I use gluetun with qbt and ProtonVPN (with port forwarding). Despite this being a tricky config, it was still pretty easy to setup. Can share bash scripts if anyone is interested.
How do you handle the forwarded port change on every reconnect and updating it in qbt?
gluetun bundles a control server on port 8000 which you can query for the port number (don’t worry about
openvpn
being in the url path, it still works with Wireguard). In my bash script (running on the host system), I usecurl
to retrieve the forwarded port number and then do a POST with that data to the API of my qbt client which is running in another container on port 8080.