URL to the Wiki page
https://github.com/qdm12/gluetun-wiki/blob/main/setup/providers/private-internet-access.md
What's missing?
I recently just worked through setting up my gluetun instance to use wireguard with PIA and while the documentation and everything is adequate, the script that was linked was 3 years old and not maintained. So I forked it and updated it with some QoL features. I did put in a PR that Kyle may merge at some point and if he does, then ignore this.
But generally my updated fork (https://github.com/Ephemeral-Dust/pia-wg-config) allows the following :
Two new flags:
--server, -s which will add the server's common name to the config file--port-fowarding, -p which will force the script to only use servers that support port forwarding.
These two flags make setting up PIA wireguard with port forwarding much simpler, in addition I updated the script to use PIA's V6 json server list as the old script was still on V4.
A QoL thing that would be neat to add, but would likely require something on gluetuns side, is if you bind the wg0.conf to gluetuns wg0.conf, it would be able to read the username, password, and server names from it, so the only environment flags you would need to set beyond the custom provider ones are VPN_PORT_FORWARDING=on and VPN_PORT_FORWARDING_PROVIDER=private internet access.
URL to the Wiki page
https://github.com/qdm12/gluetun-wiki/blob/main/setup/providers/private-internet-access.md
What's missing?
I recently just worked through setting up my gluetun instance to use wireguard with PIA and while the documentation and everything is adequate, the script that was linked was 3 years old and not maintained. So I forked it and updated it with some QoL features. I did put in a PR that Kyle may merge at some point and if he does, then ignore this.
But generally my updated fork (https://github.com/Ephemeral-Dust/pia-wg-config) allows the following :
Two new flags:
--server, -swhich will add the server's common name to the config file--port-fowarding, -pwhich will force the script to only use servers that support port forwarding.These two flags make setting up PIA wireguard with port forwarding much simpler, in addition I updated the script to use PIA's V6 json server list as the old script was still on V4.
A QoL thing that would be neat to add, but would likely require something on gluetuns side, is if you bind the wg0.conf to gluetuns wg0.conf, it would be able to read the username, password, and server names from it, so the only environment flags you would need to set beyond the custom provider ones are VPN_PORT_FORWARDING=on and VPN_PORT_FORWARDING_PROVIDER=private internet access.