port forwarding no longer working

[tcurdt]

This here fails:

  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")"

with a connection refused

* Connecting to hostname: 10.12.112.24
*   Trying 10.12.112.24...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x1360960)
* connect to 10.12.112.24 port 19999 failed: Connection refused
* Failed to connect to 10.12.112.24 port 19999: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 10.12.112.24 port 19999: Connection refused

As a paying customer I am utterly annoyed there is no proper support for manually using wireguard.
And now even the openvpn stopped working properly.

What's going on?

[aarsenca]

I believe I have the same problem. Until this morning, the port forwarding script had been running non-stop for close to two months on my Raspberry Pi. It stopped by itself this morning. I just tried reconnecting (wireguard, autoconnect) and getting a new port. The script failed with this error: The payload_and_signature variable does not contain an OK status. I tried with openvpn and other specific servers and got the same error. I also tried with piactl: I was able to connect (wireguard and openvpn, region auto, requestportforward true), but get portforward returned "unknown". I spent about 45 minutes chatting with PIA Support. The issue was escalated. I just received an email saying basically that they were able to replicate the problem but magically, they tried several times with the same run-setup.sh command I was using and they ended up getting a port. So their suggestion is to keep trying the same thing over and over again and it should work... Needless to say, it has not worked for me yet!

[aarsenca]

For what it's worth, I just got a port with openvpn and preferred server ca-montreal.

[et304383]

I am having this issue as well. Can't establish a conenction to the server. It's like they shut down port 19999 ?

[et304383]

Seems that something has changed with how you must port forward. Before I could bind to my public IP. Now I have to bind to the 10.x route/gateway. So if you had custom scripts like I do, change that part. Seems to have fixed the issue for me.

port_forwarding_gateway=$(route | grep -P '^0\.0\.0\.0' | awk '{print $2}')

ETA: it also seems to matter what hostname you choose for your particular endpoint. I'm using Swiss and zurich406 works while zurich411 returns an empty response.

[aarsenca]

I still have this issue once in a while. It is usually due to something failing on PIA's side. When it happens, I switch from wireguard to openvpn and it usually gives me a port. If it doesn't, I wait a few minutes and try again. When it starts working again, I switch back to wireguard and I usually get a port. I can also try with "auto" instead of a specific server, but usually it does not fix the problem. Sometimes, it can take a few hours before it starts working properly. It's not a real solution, but it's my solution until I find a better one.

[GoPapaSmurf]

I had this error message. As it turns out, the local IP address of my tunnel changed, not knowing... So the IP address of PF_GATEWAY was wrong. I corrected it, and this solved the problem.