docker-surfshark VS openvpn-client

Looking in the issues this one doesn't have a kill switch. https://github.com/ilteoood/docker-surfshark/issues/48

I don't believe they allow port forwarding but no issues with docker

I am trying to put in place my vpn using this image and I have an error as below :

This is the VPN I use (dockerfied) pay close attention to the examples, configuring your torrent client wrong will result in a IP leak. https://github.com/ilteoood/docker-surfshark

SurfShark VPN

Ok everything is running and seems to be ok if I check the container logs but if I switch to the website and the corresponding port I just see ERR_CONNECTION_TIMED_OUT any idea? Did it with https://github.com/ilteoood/docker-surfshark and QBitTorrent now. The surfshark openVPN container looks fine as the connection was established.

I use dperson/openvpn-client, which seems to do the trick for the most part. Ive got several packages that route through it using network_mode: "service:openvpn".

Gluetun has an integrated killswitch: https://github.com/qdm12/gluetun

I used to use https://github.com/dperson/openvpn-client which has a killswitch as well.

By kill-switch I mean iptables rules that don't let anything out if there's no VPN interface up. So you don't run the risk of leaking torrent stuff through your plain-text connection.

One of my Pi servers running a series of Docker services was taken out a few months back because an apt upgrade changed the compilation target of time_t causing me to have to spend a week untangling a web of dependencies to revert to an older version of musl.

I just tested the https://github.com/dperson/openvpn-client to use my NordVPN account and could get it working, the container connects succesfully! Can I somehow share this connection to other LAN devices (eg my TV) where I cant't install a VPN client?

I have gone down a rabbit hole today trying to route all Docker container traffic through OpenVPN. Previously I have used dperson/openvpn-client, but I would prefer to run OpenVPN directly on the host. With the VPN up on the host, the Docker containers make use of the VPN connection but if it drops they continue without it. Ideally there would be a kill switch to prevent this from happening.

I am looking to use my protonvpn subscription to use with an OpenVPN container (this one), but the documentation on both Protonvpn and the repo is pretty light on how to use it.

Hey there, I successfully managed to run this OpenVPN docker Container on my DS218+. I then connected another container to use this OpenVPN container as a network. Everything works like a charm.

OpenVPN client to route my illicit content through Pakistan (CyberGhost paid VPN)

As someone who's currently using dperson/openvpn-client with a Cyberghost VPN, what are the advantages of this container?

I'd like to integrate an application on a container that's connected to an OpenVPN server. I've found a convenient client base image to build on top of, but I can't seem to find the right way to do this.