Pia-tun

Feature-rich PIA (Private Internet Access) WireGuard VPN container that automatically selects the lowest-latency server, applies a strict killswitch with…

  • Network Services
  • Security
Feature-rich PIA (Private Internet Access) WireGuard VPN container that automatically selects the lowest-latency server, applies a strict killswitch with zero-leak protection, syncs the forwarded port to qBittorrent, Deluge, or Transmission, and exposes optional SOCKS5/HTTP proxies and DNS-over-TLS for other containers.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

68/100 Good

Maintained
84last commit 3 days ago
Popular
42132 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
132
Open issues
3
Last commit
2026-11-17
Latest release
v1.1.3
License
MIT
Activity
rising

Checked 3 days ago - source: GitHub (x0lie/pia-tun)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 3 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in PIA install placeholders Replace <clientid> and <partnername> with your real PIA client ID and company name before running the install. If you leave them as placeholders, the agent will not connect to your tenant and first setup will fail. source
  • Add the Pia Winget feed first Winget (Windows' package installer) needs Pia's feed added first, using your tenant name and a valid, non-expired security token. If the source or token is missing, the installer cannot find the package and the install will stop. source
  • Download the agent first Make sure the installer downloads the Pia Agent file before it launches the install command. If that download is blocked or incomplete, setup fails or leaves a broken agent. source
  • Configure environment variables Set PIA_USER and PIA_PASS to your Private Internet Access credentials. Set LOCAL_NETWORKS to your LAN CIDR (e.g. 192.168.1.0/24) to allow downstream WebUI access. Set PIA_LOCATIONS (e.g. ca_toronto) or leave 'all' for automatic server selection, and set PS_CLIENT to qbittorrent, deluge, or transmission to enable automatic port forwarding sync. Additional variables PS_USER, PS_PASS, and PS_URL may source
  • Route traffic through the VPN On each downstream container that should use the VPN (e.g. qBittorrent), change its network type to 'Container' and select 'pia-tun' from the Container Network dropdown so all its traffic is tunneled through the PIA connection. source

Fetched 3 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to add a PIA auth token to my compose file?

No. The container acquires the auth token automatically and keeps it fresh. You provide PIA_USER and PIA_PASS as your credentials.

How can other containers connect through the PIA tunnel?

Enable the optional SOCKS5 and HTTP proxy services so other machines or containers can use the VPN. Optional proxy authentication is supported.

How do I sync the forwarded port to a torrent client?

Set PS_CLIENT to qbittorrent, deluge, or transmission to enable automatic port sync. You may also set PS_USER, PS_PASS, and PS_URL for that client.

How do I allow access to downstream torrent WebUIs from my LAN?

Set LOCAL_NETWORKS to your LAN CIDR, such as 192.168.1.0/24, to allow downstream WebUI access.

Does it work on minimal hosts?

Yes. It supports WireGuard userspace with wireguard-go and includes an iptables-legacy auto-fallback.

Answers sourced from github.com

Community

No community discussions collected yet.