thrnz

I think 6881 is the default port used by Bittorrent, so if you're sticking with the defaults and using it on a normal connection, then port 6881 would need forwarding...

https://github.com/thrnz/docker-wireguard-pia/blob/d55b299fe4e6acadf20a76e36aa9e4f82d36a62f/pf_success.sh#L24-L25 Is the custom script executable? That's the only thing that comes to mind. The custom script is only run if set `-n`, exists and has permission to execute `-x`....

`PORT_SCRIPT` should point to where the script has been mounted inside the container - its run from within the container after the port is successfully forwarded. If I'm reading the...

``` c376d7f98240:/scripts# [ -x $PORT_SCRIPT ] && echo "true" c376d7f98240:/scripts# [ -n $PORT_SCRIPT ] && echo "true" true c376d7f98240:/scripts# ``` That reminds be a bit of another issue - #28...

Is #74 enough to work around it? I can stick it on Docker hub and tag it as testing if it's more convenient than manually building it.

> I actually just learned that with docker-compose you can just replace the `image: thrnz/docker-wireguard-pia` with `build: https://github.com/thrnz/docker-wireguard-pia.git#pf-custom-cmd` to build a branch. TIL! That's actually looks really handy. > It...

The container handles generating Wireguard configs itself. From that log it looks like getting the initial auth token and serverlist is failing which suggests some network wonkiness. Running the container...

`curl: (7) Failed to connect to serverlist.piaservers.net port 443 after 6302 ms: Host is unreachable` Those logs look normal enough up until there. It might worth checking that `https://serverlist.piaservers.net/vpninfo/servers/v6` is...

Is qBittorrent bound to the wireguard interface `wg0`? That's one thing that comes to mind that I vaguely recall being an issue in the past. IIRC it uses all network...

I think the only time those log messages happen is when the container itself is stopped or restarted. It's triggered when the `run` script receives a `SIGTERM` from Docker itself...