act28/pia-openvpn-proxy repository overview

⁠Privoxy via Private Internet Access OpenVPN/WireGuard

An Alpine Linux container running Privoxy and OpenVPN/WireGuard via Private Internet Access

⁠Starting the VPN Proxy

⁠Using docker run

⁠OpenVPN Example

docker run -d \
--cap-add=MKNOD \
--cap-add=NET_ADMIN \
--cap-add=NET_RAW \
--device=/dev/net/tun \
--name=vpn_proxy \
--dns=209.222.18.218 --dns=209.222.18.222 \
--restart=always \
-e "VPN_PROTOCOL=openvpn" \
-e "REGION=switzerland" \
-e "USERNAME=${USERNAME}" \
-e "PASSWORD=${PASSWORD}" \
-e "LOCAL_NETWORK=192.168.1.0/24" \
-e "UID=1000" \
-e "GID=1000" \
-v /etc/localtime:/etc/localtime:ro \
-v </host/path/to/config>:/config \
-p 8118:8118 \
-p 1080:1080 \
docker.io/act28/pia-openvpn-proxy

⁠WireGuard Example

docker run -d \
--cap-add=NET_ADMIN \
--cap-add=NET_RAW \
--sysctl="net.ipv4.conf.all.src_valid_mark=1" \
--privileged=true \
--name=vpn_proxy \
--dns=209.222.18.218 --dns=209.222.18.222 \
--restart=always \
-e "VPN_PROTOCOL=wireguard" \
-e "REGION=swiss" \
-e "USERNAME=${USERNAME}" \
-e "PASSWORD=${PASSWORD}" \
-e "LOCAL_NETWORK=192.168.1.0/24" \
-e "UID=1000" \
-e "GID=1000" \
-v /etc/localtime:/etc/localtime:ro \
-v </host/path/to/config>:/config \
-p 8118:8118 \
-p 1080:1080 \
docker.io/act28/pia-openvpn-proxy

NOTE Substitute the environment variables for VPN_PROTOCOL, REGION, USERNAME, PASSWORD, LOCAL_NETWORK, UID, GID as indicated.

⁠Using docker-compose

An example docker-compose-dist.yml file has been provided. Copy/rename this file to docker-compose.yml and substitute the environment variables as indicated.

Then start the VPN Proxy via:

docker-compose up -d

⁠Environment Variables

⁠Wireguard

PIA's wireguard uses a JSON API request over HTTPS to configure and setup the tunnel connection. You will have to search through the returned JSON data to find the id key of your preferred region.

You can find the current region list here⁠.

The open-source PIA manual-connection⁠ script uses a latency check to determine the "best" region, which may not be ideal, in certain circumstances. I have chosen not to include a latency check at this time, but may consider it in another iteration.

⁠Connecting to the VPN Proxy

To connect to the VPN Proxy, set your browser proxy to 127.0.0.1:8118 (or 0.0.0.0:8118 if that does not work). If you override the docker port -p, make sure to use that port number instead.

Alternatively, you can use the ZeroOmega extension/addon as a convenience.

Proxy SwitchyOmega 3 (ZeroOmega) for Chrome⁠

ZeroOmega--Proxy SwitchyOmega V3 for FireFox⁠

⁠SOCKS5 Proxy

A SOCKS5 proxy has been provided to support tcp/udp routing through the VPN tunnel. Use 127.0.0.1:1080 (or 0.0.0.0:1080)

⁠Like this project? Help support it.

Donate⁠

Onion⁠