gluetun: VPN client in a thin Docker container for multiple VPN providers

github.com GitHub - qdm12/gluetun: VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.

VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in. - GitHub - qdm12/gluetun: VPN clien...

Cool GitHub Projects @programming.dev

VPN client in a thin Docker container for multiple VPN providers!

github.com /qdm12/gluetun

1 0

Selfhosted @lemmy.world

gluetun: VPN client in a thin Docker container for multiple VPN providers

github.com /qdm12/gluetun

150 34

You're viewing a single thread.

19 comments

What's the use case?
- The container connects to the VPN and only the VPN, now you can route whatever docker containers you want through that container as a network. Now that one VPN connection can serve any container you want.
  
  That's pretty cool. I might have to set it up this weekend.
  
  I am a very big fan. Just be careful which provider you try to use with it as not all are created equal. I have had good luck with AirVPN.
  
  I can also +1 that, getting the OpenVPN key and cert was a bit complicated but other than that there weren't any issues with AirVPN whatsoever.
- I use gluetun to route traffic from some of my containers that need a VPN. qBittorrent, Jackett etc. Some containers dont have the option to configure a proxy so you'd have to setup a VPN client within a container which isn't ideal. With gluetun its easy to attach a container to it and it just works
  
  Neat. I never need a VPN for more than a few days at a time, but if I ever sub to one long term I'll keep this in mind.
  
  Good point about Jackett! I had only set up qbittorrent to use vpn.
  
  Why isn't it ideal? I'm currently using this setup with containers routed through a gluetun container connected to a vpn via wireguard, and it seems to be working fine. I've verified using curl inside the relevant containers to query an IP checker and I've also used a torrent IP checker to confirm my torrent client isn't leaking my IP.
  
  I think he's saying that manually configuring all the containers (without this tool) isn't ideal.
  
  Oh sure yeah it did suck 😁
  
  Also the biggest benefit; You only need 1 VPN connection and 1 key pair for gluetun to connect everything. Most VPN providers limit the amount of active simultaneous connections. If you have lots of containers that need it then it's not possible

19 comments