manual-connections VS gluetun

Nope, those are here but they're clunky as heck

I don't know what to do with these PIA github files. https://github.com/pia-foss/manual-connections

WireGuard is much faster for me. See here for PIA and 3rd party scripts which can be used to create WireGuard config files.

There's a separate API you need to use after the link is up

If you're running a Linux server and want to automate it, PIA's automated connection scripts are here, and this script automatically runs those scripts, grabs the forwarded port and updates the config of your favorite client, then starts it.

I'm a bit partial to doing vpn with foss protocol and clients, without gui applications at all on mac and linux. PIA provides some nice resources to that end on their foss github page.

I set up PIA on my Ubuntu Server (which does not run 24/7) using the official Manual Connections repository, however with WireGuard, the authentication token runs out for me after a few days (since it expires when my server is turned off, then it can't get a new token when it turns back on), is there any way I can prevent this? It was working perfectly before the access token expired :p

https://github.com/pia-foss/manual-connections lists several, including mine

It's a bit of a pain in the butt, but I used the PIA manual connection script to generate a wireguard config file, and then I plugged that into gluetun and now it works great. Was easier than trying to config OpenVPN

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki