2020-03-29 16:42:06 -04:00
# Gluetun VPN client
2020-02-06 20:42:46 -05:00
2020-05-29 07:24:27 -04:00
*Lightweight swiss-knife-like VPN client to tunnel to Private Internet Access, Mullvad, Windscribe and Surfshark VPN servers, using Go, OpenVPN, iptables, DNS over TLS, ShadowSocks and Tinyproxy*
2020-02-06 20:42:46 -05:00
2020-05-17 17:54:37 -04:00
**ANNOUNCEMENT**: * New wiki available [here](https://github.com/qdm12/private-internet-access-docker/wiki) *
2020-02-06 20:42:46 -05:00
2020-04-12 13:42:41 +00:00
<img height="250" src="https://raw.githubusercontent.com/qdm12/private-internet-access-docker/master/title.svg?sanitize=true">
2020-02-06 20:42:46 -05:00
2020-03-25 18:23:09 -04:00
[](https://github.com/qdm12/private-internet-access-docker/actions?query=workflow%3A%22Buildx+latest%22)
2020-02-06 20:42:46 -05:00
[](https://hub.docker.com/r/qmcgaw/private-internet-access)
[](https://hub.docker.com/r/qmcgaw/private-internet-access)
[](https://github.com/qdm12/private-internet-access-docker/issues)
[](https://github.com/qdm12/private-internet-access-docker/issues)
[](https://github.com/qdm12/private-internet-access-docker/issues)
[](https://microbadger.com/images/qmcgaw/private-internet-access)
[](https://microbadger.com/images/qmcgaw/private-internet-access)
[](https://join.slack.com/t/qdm12/shared_invite/enQtOTE0NjcxNTM1ODc5LTYyZmVlOTM3MGI4ZWU0YmJkMjUxNmQ4ODQ2OTAwYzMxMTlhY2Q1MWQyOWUyNjc2ODliNjFjMDUxNWNmNzk5MDk)
<details><summary>Click to show base components</summary><p>
- [Alpine 3.11 ](https://alpinelinux.org ) for a tiny image (37MB of packages, 6.7MB of Go binary and 5.6MB for Alpine)
2020-06-03 02:11:35 +00:00
- [OpenVPN 2.4.8 ](https://pkgs.alpinelinux.org/package/v3.11/main/x86_64/openvpn ) to tunnel to your VPN provider servers
2020-02-06 20:42:46 -05:00
- [IPtables 1.8.3 ](https://pkgs.alpinelinux.org/package/v3.11/main/x86_64/iptables ) enforces the container to communicate only through the VPN or with other containers in its virtual network (acts as a killswitch)
- [Unbound 1.9.6 ](https://pkgs.alpinelinux.org/package/v3.11/main/x86_64/unbound ) configured with Cloudflare's [1.1.1.1 ](https://1.1.1.1 ) DNS over TLS (configurable with 5 different providers)
- [Files and blocking lists built periodically ](https://github.com/qdm12/updated/tree/master/files ) used with Unbound (see `BLOCK_MALICIOUS` , `BLOCK_SURVEILLANCE` and `BLOCK_ADS` environment variables)
- [TinyProxy 1.10.0 ](https://pkgs.alpinelinux.org/package/v3.11/main/x86_64/tinyproxy )
- [Shadowsocks 3.3.4 ](https://pkgs.alpinelinux.org/package/edge/testing/x86/shadowsocks-libev )
</p></details>
## Features
2020-02-22 17:06:35 +00:00
- Based on Alpine 3.11 for a small Docker image below 50MB
2020-05-29 07:24:27 -04:00
- Supports **Private Internet Access ** , **Mullvad ** , **Windscribe ** and **Surfshark ** servers
2020-02-22 17:06:35 +00:00
- DNS over TLS baked in with service provider(s) of your choice
2020-05-02 17:08:15 +00:00
- DNS fine blocking of malicious/ads/surveillance hostnames and IP addresses, with live update every 24 hours
2020-02-22 17:06:35 +00:00
- Choose the vpn network protocol, `udp` or `tcp`
2020-06-03 02:11:35 +00:00
- Built in firewall kill switch to allow traffic only with needed the VPN servers and LAN devices
2020-02-22 17:06:35 +00:00
- Built in SOCKS5 proxy (Shadowsocks, tunnels TCP+UDP)
- Built in HTTP proxy (Tinyproxy, tunnels TCP)
- [Connect other containers to it ](https://github.com/qdm12/private-internet-access-docker#connect-to-it )
- [Connect LAN devices to it ](https://github.com/qdm12/private-internet-access-docker#connect-to-it )
2020-03-29 16:42:06 -04:00
- Compatible with amd64, i686 (32 bit), **ARM ** 64 bit, ARM 32 bit v6 and v7 🎆
2020-02-22 17:06:35 +00:00
### Private Internet Access
- Pick the [region ](https://www.privateinternetaccess.com/pages/network/ )
- Pick the level of encryption
- Enable port forwarding
### Mullvad
- Pick the [country, city and ISP ](https://mullvad.net/en/servers/#openvpn )
- Pick the port to use (i.e. `53` (udp) or `80` (tcp))
2020-03-29 16:42:06 -04:00
### Windscribe
- Pick the [region ](https://windscribe.com/status )
2020-06-02 23:07:29 +00:00
- Pick the port to use
2020-03-29 16:42:06 -04:00
2020-05-29 07:24:27 -04:00
### Surfshark
2020-06-02 23:07:29 +00:00
- Pick the [region ](https://github.com/qdm12/private-internet-access-docker/wiki/Surfshark ) or a multi hop region name
2020-05-29 07:24:27 -04:00
2020-02-22 17:06:35 +00:00
### Extra niche features
2020-02-22 17:07:06 +00:00
- Possibility of split horizon DNS by selecting multiple DNS over TLS providers
2020-02-22 17:06:35 +00:00
- Subprograms all drop root privileges once launched
- Subprograms output streams are all merged together
2020-02-22 17:07:06 +00:00
- Can work as a Kubernetes sidecar container, thanks @rorph
2020-02-06 20:42:46 -05:00
## Setup
2020-02-22 17:05:52 +00:00
1. Requirements
2020-04-13 00:21:41 +00:00
- A VPN account with one of the service providers:
2020-06-02 23:07:29 +00:00
- Private Internet Access: **username ** and **password ** ([sign up ](https://www.privateinternetaccess.com/pages/buy-vpn/ ))
2020-04-13 00:21:41 +00:00
- Mullvad: user ID ([sign up ](https://mullvad.net/en/account/ ))
- Windscribe: **username ** and **password ** | Signup up using my affiliate link below
2020-04-13 00:32:57 +00:00
[](https://windscribe.com/?affid=mh7nyafu)
2020-04-13 00:21:41 +00:00
2020-06-02 23:07:29 +00:00
- Surfshark: **username ** and **password ** ([sign up ](https://order.surfshark.com/ ))
2020-04-12 13:42:41 +00:00
- If you have a host or router firewall, please refer [to the firewall documentation ](https://github.com/qdm12/private-internet-access-docker/blob/master/doc/firewall.md )
2020-02-06 20:42:46 -05:00
2020-05-03 16:28:59 +00:00
1. On some devices such as Synology or Qnap machines, it's required to setup your tunnel device `/dev/net/tun` on your host:
```sh
insmod /lib/modules/tun.ko
# or
modprobe tun
```
You can verify it's here with `ls /dev/net`
2020-02-06 20:42:46 -05:00
1. Launch the container with:
```bash
2020-06-03 02:11:35 +00:00
docker run -d --name gluetun --cap-add=NET_ADMIN \
2020-02-06 20:42:46 -05:00
-e REGION="CA Montreal" -e USER=js89ds7 -e PASSWORD=8fd9s239G \
qmcgaw/private-internet-access
```
or use [docker-compose.yml ](https://github.com/qdm12/private-internet-access-docker/blob/master/docker-compose.yml ) with:
```bash
docker-compose up -d
```
Note that you can:
2020-02-22 17:07:06 +00:00
2020-02-06 20:42:46 -05:00
- Change the many [environment variables ](#environment-variables ) available
2020-04-12 13:42:41 +00:00
- Use `-p 8888:8888/tcp` to access the HTTP web proxy (and put your LAN in `EXTRA_SUBNETS` environment variable, in example `192.168.1.0/24` )
- Use `-p 8388:8388/tcp -p 8388:8388/udp` to access the SOCKS5 proxy (and put your LAN in `EXTRA_SUBNETS` environment variable, in example `192.168.1.0/24` )
2020-04-30 23:41:57 +00:00
- Use `-p 8000:8000/tcp` to access the [HTTP control server ](#HTTP-control-server ) built-in
2020-02-06 20:42:46 -05:00
- Pass additional arguments to * openvpn * using Docker's command function (commands after the image name)
2020-02-22 17:07:06 +00:00
2020-05-02 14:59:22 +00:00
**If you encounter an issue with the tun device not being available, see [the FAQ](https://github.com/qdm12/private-internet-access-docker/blob/master/doc/faq.md#how-to-fix-openvpn-failing-to-start) **
2020-05-17 17:54:37 -04:00
1. You can update the image with `docker pull qmcgaw/private-internet-access:latest` . See the [wiki ](https://github.com/qdm12/private-internet-access-docker/wiki/Common-issues#use-a-release-tag ) for more information on other tags available.
2020-02-06 20:42:46 -05:00
## Testing
2020-06-03 02:11:35 +00:00
Check the VPN IP address matches your expectations
2020-02-06 20:42:46 -05:00
```sh
2020-06-03 02:11:35 +00:00
docker run --rm --network=container:gluetun alpine:3.11 wget -qO- https://ipinfo.io
2020-02-06 20:42:46 -05:00
```
2020-05-17 17:54:37 -04:00
Want more testing? ▶ [see the Wiki ](https://github.com/qdm12/private-internet-access-docker/wiki/Testing )
2020-02-06 20:42:46 -05:00
## Environment variables
2020-05-17 18:34:57 -04:00
**TLDR**; only set the 🏁 marked environment variables to get started.
### VPN
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
2020-05-29 07:24:27 -04:00
| 🏁 `VPNSP` | `private internet access` | `private internet access` , `mullvad` , `windscribe` , `surfshark` | VPN Service Provider |
2020-05-17 18:34:57 -04:00
| `IP_STATUS_FILE` | `/ip` | Any filepath | Filepath to store the public IP address assigned |
| `PROTOCOL` | `udp` | `udp` or `tcp` | Network protocol to use |
| `OPENVPN_VERBOSITY` | `1` | `0` to `6` | Openvpn verbosity level |
| `OPENVPN_ROOT` | `no` | `yes` or `no` | Run OpenVPN as root |
| `OPENVPN_TARGET_IP` | | Valid IP address | Specify a target VPN server IP address to use |
| `OPENVPN_CIPHER` | | i.e. `aes-256-gcm` | Specify a custom cipher to use. It will also set `ncp-disable` if using AES GCM for PIA |
| `OPENVPN_AUTH` | | i.e. `sha256` | Specify a custom auth algorithm to use |
- Private Internet Access
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| 🏁 `USER` | | | Your username |
| 🏁 `PASSWORD` | | | Your password |
| `REGION` | `Austria` | One of the [PIA regions ](https://www.privateinternetaccess.com/pages/network/ ) | VPN server region |
| `PIA_ENCRYPTION` | `strong` | `normal` , `strong` | Encryption preset |
| `PORT_FORWARDING` | `off` | `on` , `off` | Enable port forwarding on the VPN server |
| `PORT_FORWARDING_STATUS_FILE` | `/forwarded_port` | Any filepath | Filepath to store the forwarded port number |
- Mullvad
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| 🏁 `USER` | | | Your user ID |
| `COUNTRY` | `Sweden` | One of the [Mullvad countries ](https://mullvad.net/en/servers/#openvpn ) | VPN server country |
| `CITY` | | One of the [Mullvad cities ](https://mullvad.net/en/servers/#openvpn ) | VPN server city |
| `ISP` | | One of the [Mullvad ISP ](https://mullvad.net/en/servers/#openvpn ) | VPN server ISP |
| `PORT` | | `80` or `443` for TCP; or `53` for UDP. Leave blank for default Mullvad server port | Custom VPN port to use |
- Windscribe
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| 🏁 `USER` | | | Your username |
| 🏁 `PASSWORD` | | | Your password |
| `REGION` | `Austria` | One of the [Windscribe regions ](https://windscribe.com/status ) | VPN server region |
| `PORT` | | One from the [this list of ports ](https://windscribe.com/getconfig/openvpn ) | Custom VPN port to use |
2020-05-29 07:24:27 -04:00
- Surfshark
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| 🏁 `USER` | | | Your username |
| 🏁 `PASSWORD` | | | Your password |
| `REGION` | `Austria` | One of the [Surfshark regions (subdomains) ](https://github.com/qdm12/private-internet-access-docker/wiki/surfshark ) | VPN server region |
2020-05-17 18:34:57 -04:00
### DNS over TLS
None of the following values are required.
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| `DOT` | `on` | `on` , `off` | Activate DNS over TLS with Unbound |
| `DOT_PROVIDERS` | `cloudflare` | `cloudflare` , `google` , `quad9` , `quadrant` , `cleanbrowsing` , `securedns` , `libredns` | Comma delimited list of DNS over TLS providers |
| `DOT_CACHING` | `on` | `on` , `off` | Unbound caching |
| `DOT_IPV6` | `off` | `on` , `off` | DNS IPv6 resolution |
| `DOT_PRIVATE_ADDRESS` | All private CIDRs ranges | | Comma separated list of CIDRs or single IP addresses Unbound won't resolve to. Note that the default setting prevents DNS rebinding |
| `DOT_VERBOSITY` | `1` | `0` to `5` | Unbound verbosity level |
| `DOT_VERBOSITY_DETAILS` | `0` | `0` to `4` | Unbound details verbosity level |
| `DOT_VALIDATION_LOGLEVEL` | `0` | `0` to `2` | Unbound validation log level |
| `DNS_UPDATE_PERIOD` | `24h` | i.e. `0` , `30s` , `5m` , `24h` | Period to update block lists and cryptographic files and restart Unbound. Set to `0` to deactivate updates |
| `BLOCK_MALICIOUS` | `on` | `on` , `off` | Block malicious hostnames and IPs with Unbound |
| `BLOCK_SURVEILLANCE` | `off` | `on` , `off` | Block surveillance hostnames and IPs with Unbound |
| `BLOCK_ADS` | `off` | `on` , `off` | Block ads hostnames and IPs with Unbound |
| `UNBLOCK` | |i.e. `domain1.com,x.domain2.co.uk` | Comma separated list of domain names to leave unblocked with Unbound |
### Firewall
That one is important if you want to connect to the container from your LAN for example, using Shadowsocks or Tinyproxy.
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| `EXTRA_SUBNETS` | | i.e. `192.168.1.0/24,192.168.10.121,10.0.0.5/28` | Comma separated subnets allowed in the container firewall |
### Shadowsocks
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| `SHADOWSOCKS` | `on` | `on` , `off` | Enable the internal SOCKS5 proxy Shadowsocks |
| `SHADOWSOCKS_LOG` | `off` | `on` , `off` | Enable logging |
| `SHADOWSOCKS_PORT` | `8388` | `1024` to `65535` | Internal port number for Shadowsocks to listen on |
| `SHADOWSOCKS_PASSWORD` | `8388` | `1024` to `65535` | Password to use to connect to Shadowsocks |
| `SHADOWSOCKS_METHOD` | `chacha20-ietf-poly1305` | One of [these ciphers ](https://shadowsocks.org/en/config/quick-guide.html ) | Method to use for Shadowsocks |
### Tinyproxy
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| `TINYPROXY` | `on` | `on` , `off` | Enable the internal HTTP proxy tinyproxy |
| `TINYPROXY_LOG` | `Info` | `Info` , `Connect` , `Notice` , `Warning` , `Error` , `Critical` | Tinyproxy log level |
| `TINYPROXY_PORT` | `8888` | `1024` to `65535` | Internal port number for Tinyproxy to listen on |
| `TINYPROXY_USER` | `8388` | `1024` to `65535` | Username to use to connect to Tinyproxy |
| `TINYPROXY_PASSWORD` | `8388` | `1024` to `65535` | Password to use to connect to Tinyproxy |
### System
| Variable | Default | Choices | Description |
| --- | --- | --- | --- |
| `TZ` | | i.e. `Europe/London` | Specify a timezone to use to have correct log times |
| `UID` | `1000` | | User ID to run as non root and for ownership of files written |
| `GID` | `1000` | | Group ID to run as non root and for ownership of files written |
2020-02-06 20:42:46 -05:00
## Connect to it
There are various ways to achieve this, depending on your use case.
2020-06-03 02:11:35 +00:00
- <details><summary>Connect containers in the same docker-compose.yml as Gluetun</summary><p>
2020-02-06 20:42:46 -05:00
2020-06-03 02:11:35 +00:00
Add `network_mode: "service:gluetun"` to your * docker-compose.yml * (no need for `depends_on` )
2020-02-06 20:42:46 -05:00
</p></details>
2020-06-03 02:11:35 +00:00
- <details><summary>Connect other containers to Gluetun</summary><p>
2020-02-06 20:42:46 -05:00
2020-06-03 02:11:35 +00:00
Add `--network=container:gluetun` when launching the container, provided Gluetun is already running
2020-02-06 20:42:46 -05:00
</p></details>
- <details><summary>Connect containers from another docker-compose.yml</summary><p>
2020-06-03 02:11:35 +00:00
Add `network_mode: "container:gluetun"` to your * docker-compose.yml * , provided Gluetun is already running
2020-02-06 20:42:46 -05:00
</p></details>
- <details><summary>Connect LAN devices through the built-in HTTP proxy * Tinyproxy * (i.e. with Chrome, Kodi, etc.)</summary><p>
You might want to use Shadowsocks instead which tunnels UDP as well as TCP, whereas Tinyproxy only tunnels TCP.
1. Setup a HTTP proxy client, such as [SwitchyOmega for Chrome ](https://chrome.google.com/webstore/detail/proxy-switchyomega/padekgcemlokbadohgkifijomclgjgif?hl=en )
2020-06-03 02:11:35 +00:00
1. Ensure the Gluetun container is launched with:
2020-02-06 20:42:46 -05:00
- port `8888` published `-p 8888:8888/tcp`
- your LAN subnet, i.e. `192.168.1.0/24` , set as `-e EXTRA_SUBNETS=192.168.1.0/24`
1. With your HTTP proxy client, connect to the Docker host (i.e. `192.168.1.10` ) on port `8888` . You need to enter your credentials if you set them with `TINYPROXY_USER` and `TINYPROXY_PASSWORD` .
1. If you set `TINYPROXY_LOG` to `Info` , more information will be logged in the Docker logs
</p></details>
- <details><summary>Connect LAN devices through the built-in SOCKS5 proxy * Shadowsocks * (per app, system wide, etc.)</summary><p>
1. Setup a SOCKS5 proxy client, there is a list of [ShadowSocks clients for **all platforms** ](https://shadowsocks.org/en/download/clients.html )
2020-06-03 02:11:35 +00:00
- **note** some clients do not tunnel UDP so your DNS queries will be done locally and not through Gluetun and its built in DNS over TLS
2020-02-06 20:42:46 -05:00
- Clients that support such UDP tunneling are, as far as I know:
- iOS: Potatso Lite
- OSX: ShadowsocksX
- Android: Shadowsocks by Max Lv
2020-06-03 02:11:35 +00:00
1. Ensure the Gluetun container is launched with:
2020-02-06 20:42:46 -05:00
- port `8388` published `-p 8388:8388/tcp -p 8388:8388/udp`
- your LAN subnet, i.e. `192.168.1.0/24` , set as `-e EXTRA_SUBNETS=192.168.1.0/24`
1. With your SOCKS5 proxy client
- Enter the Docker host (i.e. `192.168.1.10` ) as the server IP
- Enter port TCP (and UDP, if available) `8388` as the server port
- Use the password you have set with `SHADOWSOCKS_PASSWORD`
2020-03-29 20:06:27 -04:00
- Choose the encryption method/algorithm to the method you specified in `SHADOWSOCKS_METHOD`
2020-02-22 17:43:17 +00:00
1. If you set `SHADOWSOCKS_LOG` to `on` , (a lot) more information will be logged in the Docker logs
2020-02-06 20:42:46 -05:00
</p></details>
2020-06-03 02:11:35 +00:00
- <details><summary>Access ports of containers connected to Gluetun</summary><p>
2020-02-06 20:42:46 -05:00
2020-06-03 02:11:35 +00:00
In example, to access port `8000` of container `xyz` and `9000` of container `abc` connected to Gluetun,
publish ports `8000` and `9000` for the Gluetun container and access them as you would with any other container
2020-02-06 20:42:46 -05:00
</p></details>
2020-06-03 02:11:35 +00:00
- <details><summary>Access ports of containers connected to Gluetun, all in the same docker-compose.yml</summary><p>
2020-02-06 20:42:46 -05:00
2020-06-03 02:11:35 +00:00
In example, to access port `8000` of container `xyz` and `9000` of container `abc` connected to Gluetun, publish port `8000` and `9000` for the Gluetun container.
2020-02-06 20:42:46 -05:00
The docker-compose.yml file would look like:
```yml
version: '3.7'
services:
2020-06-03 02:11:35 +00:00
gluetun:
2020-02-06 20:42:46 -05:00
image: qmcgaw/private-internet-access
2020-06-03 02:11:35 +00:00
container_name: gluetun
2020-02-06 20:42:46 -05:00
cap_add:
- NET_ADMIN
environment:
- USER=js89ds7
- PASSWORD=8fd9s239G
ports:
- 8000:8000/tcp
- 9000:9000/tcp
abc:
image: abc
container_name: abc
2020-06-03 02:11:35 +00:00
network_mode: "service:gluetun"
2020-02-06 20:42:46 -05:00
xyz:
image: xyz
container_name: xyz
2020-06-03 02:11:35 +00:00
network_mode: "service:gluetun"
2020-02-06 20:42:46 -05:00
```
</p></details>
2020-02-22 17:15:42 +00:00
## Private Internet Access port forwarding
2020-02-06 20:42:46 -05:00
2020-02-22 17:15:42 +00:00
Note that [not all regions support port forwarding ](https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn ).
2020-02-06 20:42:46 -05:00
2020-06-03 02:11:35 +00:00
When `PORT_FORWARDING=on` , a port will be forwarded on the VPN server side and written to the file specified by `PORT_FORWARDING_STATUS_FILE=/forwarded_port` .
2020-02-06 20:42:46 -05:00
2020-02-22 17:15:42 +00:00
It can be useful to mount this file as a volume to read it from other containers, for example to configure a torrenting client.
2020-02-06 20:42:46 -05:00
2020-04-30 23:41:57 +00:00
## HTTP control server
A built-in HTTP server listens on port `8000` to modify the state of the container. You have the following routes available:
- `http://<your-docker-host-ip>:8000/openvpn/actions/restart` restarts the openvpn process
2020-05-02 17:08:15 +00:00
- `http://<your-docker-host-ip>:8000/unbound/actions/restart` re-downloads the DNS files (crypto and block lists) and restarts the unbound process
2020-04-30 23:41:57 +00:00
2020-04-12 13:42:41 +00:00
## Development and contributing
2020-03-25 18:19:57 -04:00
2020-05-17 17:54:37 -04:00
- Contribute with code: see [the Wiki ](https://github.com/qdm12/private-internet-access-docker/wiki/Contributing ).
2020-04-12 13:42:41 +00:00
- [The list of existing contributors 👍 ](https://github.com/qdm12/private-internet-access-docker/blob/master/.github/CONTRIBUTING.md#Contributors )
- [Github workflows ](https://github.com/qdm12/private-internet-access-docker/actions ) to know what's building
- [List of issues and feature requests ](https://github.com/qdm12/private-internet-access-docker/issues )
2020-02-22 17:35:50 +00:00
2020-02-06 20:42:46 -05:00
## License
This repository is under an [MIT license ](https://github.com/qdm12/private-internet-access-docker/master/license )
2020-04-13 00:32:57 +00:00
## Support
Sponsor me on [Github ](https://github.com/sponsors/qdm12 ), donate to [paypal.me/qmcgaw ](https://www.paypal.me/qmcgaw ) or subscribe to a VPN provider through one of my affiliate links:
[](https://github.com/sponsors/qdm12)
[](https://www.paypal.me/qmcgaw)
[](https://windscribe.com/?affid=mh7nyafu)
Feel also free to have a look at [the Kanban board ](https://github.com/qdm12/private-internet-access-docker/projects/1 ) and [contribute ](#Development-and-contributing ) to the code or the issues discussion.
2020-04-15 12:33:50 +00:00
2020-04-28 08:43:13 -04:00
Many thanks to @Frepke and @Ralph521 for supporting me financially 🥇👍