Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't port forward after setting up WireGuard #193

Open
jboctor opened this issue Oct 5, 2024 · 1 comment
Open

Can't port forward after setting up WireGuard #193

jboctor opened this issue Oct 5, 2024 · 1 comment

Comments

@jboctor
Copy link

jboctor commented Oct 5, 2024

I am able to run VPN_PROTOCOL=wireguard DISABLE_IPV6=yes DIP_TOKEN=no AUTOCONNECT=true PIA_PF=false PIA_DNS=true PIA_USER=pxxxxxxx PIA_PASS=xxxxxx ./run_setup.sh and connect to the VPN. After that though I need to port forward for my torrent client and when I run PIA_TOKEN=xxxxxx PF_GATEWAY=84.239.17.161 PF_HOSTNAME=michigan404 ./port_forwarding.sh I get the output Getting new signature... The payload_and_signature variable does not contain an OK status.

It's failing on this bit of code I believe.

 payload_and_signature="$(curl -s -m 5 \
    --connect-to "$PF_HOSTNAME::$PF_GATEWAY:" \
    --cacert "ca.rsa.4096.crt" \
    -G --data-urlencode "token=${PIA_TOKEN}" \
    "https://${PF_HOSTNAME}:19999/getSignature")"
@CTalvio
Copy link

CTalvio commented Jan 9, 2025

For me the issue was the script trying to enable the PF through my real interface, but it has to be done via the VPN interface. Adding --interface pia to the curl commands that the PF script runs fixes this, as it will then use the VPN tunnel to talk to the PIA server.

Make sure to do this for both places in the script where curl is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants