You can also use the HTTP control server to get the port forwarded. You will keep the same forwarded port for 60 days as long as you bind mount the /gluetun directory.
It can be useful to mount this file as a volume to read it from other containers, for example to configure a torrenting client. Disconnecting the PIA VPN then connecting the GVC always worked in the past. Long story short, I can circumvent the connection problem by disconnecting the PIA VPN and reinstalling the PIA split tunnel filter each time before using the GVC.
#Pia vpn client not connecting update#
When PRIVATE_INTERNET_ACCESS_VPN_PORT_FORWARDING=on, a port will be forwarded on the VPN server side and written to the file specified by PRIVATE_INTERNET_ACCESS_VPN_PORT_FORWARDING_STATUS_FILE=/tmp/gluetun/forwarded_port. Apparently an update to the Private Internet Access VPN client is causing this issue. It seems to only work for port forwarding for torrenting applications, not sure why, maybe they run deep packet inspection on the forwarded port. This is not a gluetun issue, but a PIA one. ⚠️ port forwarding with PIA is not really working for some reason. It defaults to /tmp/gluetun/forwarded_port.
VPN_SERVICE_PROVIDER=private internet access.SERVER_REGIONS=Netherlands Required environment variables VPN_SERVICE_PROVIDER=private internet access
0 kommentar(er)
