docker-wireguard VS openvpn-client

It’s probably better to just use the wireguard docker container setup instructions now: https://github.com/linuxserver/docker-wireguard?tab=readme-o...

You can add one to the docker compose file and then route other containers (especially qbittorrent) through it by setting network-mode. Read about it here: https://github.com/linuxserver/docker-wireguard

FWIW there is https://github.com/linuxserver/docker-wireguard/tree/alpine, which does just that really. It's a little more complicated because it still supports all the peer config envs, etc. but it's much smaller than the normal image because it doesn't have support for compiling and enabling the kernel module.

- I am using the linuxserver wireguard docker container: https://github.com/linuxserver/docker-wireguard

To expose Nexcloud to the Intenet you would also need to deploy a reverse proxy in a container (for example Nginx Proxy Manager). If you don't need Nextcloud to be publicly available, you can deploy a VPN server (Wireguard) to securely access your local network from anywhere.

wireguard for the actual VPN

Some nice services are * Invidious (youtube frontend) * Nitter (twitter frontend) * Bibliogram (not updated, but still works, instagram frontend) * Libremdb (imdb frontend) * Nextcloud (google drive alternative) * Hauk (location sharing) * LibreTanslate (translation engine) * SimplyTranslate (translation frontend, can link to LibreTranslate) * SearXNG (google search alternative) * Gotify / ntfy (notifications) * Apprise (notification gateway) * Jitsi (video chat) * Homebox (home organizer) * Home-Assistant (home automation) * Pi-hole (DNS server with adblock lists, to avoid ads on all devices) * TT-RSS (advanced and simple RSS aggregator and reader) * Alltube (youtube-dl frontend, to download videos from most websites) * Rimgo (imgur frontend) * Quetre (quora frontend) * Wikiless (wikipedia frontend, note that the repo is deleted, maybe will never be updated) * VPN server, with Wireguard (https://github.com/linuxserver/docker-wireguard, or with a nice frontend https://github.com/WeeJeWel/wg-easy)

VPN - OpenVPN or Wireguard - https://github.com/linuxserver/docker-wireguard

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?

services: vpn: container_name: vpn image: dperson/openvpn-client # cap_add, security_opt, and volume required for the image to function cap_add: - net_admin environment: TZ=Europe/London read_only: true tmpfs: - /run - /tmp restart: unless-stopped security_opt: - label:disable stdin_open: true tty: true volumes: - /dev/net:/dev/net:z - ./vpn:/vpn # You will need to change this, read https://github.com/dperson/openvpn-client # -r is your CIDR network (I specify two to allow my other docker containers in) # -f should be set to your VPN port, all other ports get firewalled # -p is for port forwarding, so your torrent port forwards work. command: '-r 192.168.1.0/24 -r 172.19.0.0/16 -f 1302 -p 23009' # Since all the containers using the VPN share the same network interface # Ports forwarded here reach the deluge container ports: - 58846:58846 - 8112:8112 sysctls: - net.ipv6.conf.all.disable_ipv6=0 # Remove this if you don't want IPv6