Our great sponsors
-
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.
-
docker-qbittorrentvpn
Discontinued Docker container which runs a qBittorent-nox client with an optional WireGuard or OpenVPN connection
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I run this one: https://github.com/DyonR/docker-qbittorrentvpn in my kubernetes cluster. It supports IVPN just fine (at least Wireguard, since I don't use OpenVPN). Once the WG tunnel is active, you should have an interface named "wg0" in the interface list: Tools->Options->Advanced->Network Interface. Select that and QBit will use that interface only (which means it won't communicate if the WG tunnel is down; which is what I want.
Related posts
- port forwarding is highly effective
- wg client public IP changes, and the connection drops completely
- How to host a docker based proxy for selected containers
- Mullvad blocking forwarded ports on machine with local network sharing activated
- Hi, anyone can explain for me how to port forwarding with PIA VPN on Linux Headless?