I'm experiencing the exact same issue. I am using private internet access on my Kali Linux box, built on Debian Wheezy. I don't have a tooltip at all so I don't know how to view what port I'm connected to. Also I saved the settings to connect automatically but I want to change the region. I can't find a way to do this. Since I don't have a tooltip I can't hover over the icon and opt to change the settings. Clicking the PIA icon connects it, but since it's set to connect automatically I am not shown the box to customize my options.
To those experiencing the same issue, I realized the only logical work around is to download PIA's openvpn config files at http://www.privateinternetaccess.com/openvpn/openvpn.zip and extract the contents of the folder into the /etc/openvpn directory. Then run PIA manually from the /etc/openvpn directory using: sudo openvpn <region>. To portforward run the new port forwarding API script to get a port assignment. Then navigate to http://canyouseeme.org and enter the port you just recieved. If everything worked correctly it should say success!
I've been having the same problem for about 2 weeks. Port forwarding previously worked fine. Like p6021691 workarounds using Linux are a bit over my head. Has anyone been able to resolve this without Linux scripts? I have an open support ticket but no help so far. An official answer would be great.
I'm running Win 10 64bit. Here are some things I've tried with no resolution:
-Tried all port forwarding enabled servers with same result -Disabled/uninstalled TinyWall and Avast Antivirus -Uninstalled and reinstalled PIA v77 -Uninstalled PIA v77 and installed v75
Here's a relevant-seeming c/p from my pia_manager.log file:
18-03-13T15:42:51.586Z] <info> #7944/39722364 |PiaManager| Assigning port forward
Permission denied means that the app has tried to connect to the port forwarding API, but has explicitly been denied so by the operating system. On Windows, that's firewall or antivirus most of the time.
You can probably verify this by simply opening the link in your browser within 2 minutes of connecting. You will probably also get an error from your browser that it can't connect because of a firewall. If it goes through and gives you a port, well you can use that port but should also make sure to check your antivirus whitelist to make sure it's allowing PIA's rubyw.exe to connect to the Internet.
On my MacOS 10.11.6 setup I can request a port from a new region and it works just fine. But once I lose connection to that region, I can't request a port anymore. So I have needed to change region every few days. Within another week or so, I will be out of regions!
I have tried going back to earlier connections which worked before, but they still don't offer ports anymore.
Seems like we are having some issues with port forwarding, our network team is working on it. In the meantime, just keep trying: you will eventually get one. You don't have to change region completely for it to work, it just helps workaround the problem.
I'm still getting one everytime personally but we've heard from the network team that it's a load issue on the port forward API.
Same issue, mine isn't working at all. I even installed the v78 on a clean vm with no iptable rules and it still doesn't work. No matter how many times I switch, no luck.
Ok I found the answer. There are TWO problems. The ubuntu tooltip isn't updating. AND Some of the servers are returning CONNECTION RESET BY PEER. If you turn on debugging logs and switch servers you'll find your port eventually by grepping the debug log:
grep -a "Forwarded port:" ~/.pia_manager/log/pia_manager.log
should be the last one if you got one.
It works for now! Hope this helps you fix the next build PIA
This tooltip on unbuntu always seems to have troubles. I would suggest throwing it on the SETTINGS LOCKED screen as well as a backup since these tooltips have gotten broken twice now.
I noticed today the tooltip wasn't showing a Forwarded Port in v77 for The Netherlands. I upgraded to v78 and checked the pia_nw.log and it was showing "forwarded_port":{"single":null}. I tried reconnected a bunch of times to NL to no avail. It does still work for France as mentioned above.
@p6435869, we had to deactivate port forwarding on the Netherlands region due to ongoing network issues. We're planning to get port forwarding working on NL again in the future, but we're not quite there yet.
@p6435869, we had to deactivate port forwarding on the Netherlands region due to ongoing network issues. We're planning to get port forwarding working on NL again in the future, but we're not quite there yet.
Would still love a persistent popup when the forwarded port is changed or unavailable!
Using Mac v.79, not getting port forwards at all. No port mentioned in the tooltip, and no "forwarded" strings in pia_nw.log or openvpn.log. Tried Czech Republic, Montreal, Vancouver.
Using Mac v.79, not getting port forwards at all. No port mentioned in the tooltip, and no "forwarded" strings in pia_nw.log or openvpn.log. Tried Czech Republic, Montreal, Vancouver.
Can you send us a debug log and let me know the debug ID so I can look at it?
Using Mac v.79, not getting port forwards at all. No port mentioned in the tooltip, and no "forwarded" strings in pia_nw.log or openvpn.log. Tried Czech Republic, Montreal, Vancouver.
Can you send us a debug log and let me know the debug ID so I can look at it?
Using Mac v.79, not getting port forwards at all. No port mentioned in the tooltip, and no "forwarded" strings in pia_nw.log or openvpn.log. Tried Czech Republic, Montreal, Vancouver.
Can you send us a debug log and let me know the debug ID so I can look at it?
Sure. Thanks for looking. 4 A 8 5 A
Testing, got the following results by running selected lines from port_forwarding.sh.
$ client_id=`head -n 100 /dev/urandom | shasum -a 256 | tr -d " -"` $ echo $client_id 00970665b7d405b2--obfuscated--b0906ec61d3ee0b60ee4b64e1 $ curl http://209.222.18.222:2000/\?client_id\=$client_id curl: (52) Empty reply from server
@Disposable001 Seems that for some reason the API isn't accepting the app's traffic trying to get your public IP. It does seem that the port forward request is going through as expected:
[2018-04-18T14:49:29.972Z] <info> #16762/70152730305820 |PiaManager| Forwarded port response: {"port"=>42209}
@Disposable001 Seems that for some reason the API isn't accepting the app's traffic trying to get your public IP. It does seem that the port forward request is going through as expected:
[2018-04-18T14:49:29.972Z] <info> #16762/70152730305820 |PiaManager| Forwarded port response: {"port"=>42209}
Are you using the x-username and password with the app by chance instead of your p-username? After discussion with the team, it sounds like what is happening is that the app tries to contact the API to get additional information and set things up, but it is being denied because it expects a p-username and that stalls the whole part that eventually shows the tooltip.
@Max-P Yes, I’m using the x-name as the login name. Is that not desirable? Was working with the old v.69 client. If it’s not fully supported by the API, perhaps you should configure the client only to accept the p-name, or maybe synthesize the p-name from the x-name “under the hood” and use it instead. I’ll retest with the p-name and report back.
Hello. Is there a solution for this yet? I'm using my P name and it is no longer showing a port. I believe this started when I upgraded today. I tried all of Canada, Germany, and Switzerland. Uninstalling now and reinstalling now.
EDIT: Nevermind. Uninstalling and reinstalling (I assume) worked.
Comments
I am using private internet access on my Kali Linux box, built on Debian Wheezy. I don't have a tooltip at all so I don't know how to view what port I'm connected to.
Also I saved the settings to connect automatically but I want to change the region. I can't find a way to do this. Since I don't have a tooltip I can't hover over the icon and opt to change the settings. Clicking the PIA icon connects it, but since it's set to connect automatically I am not shown the box to customize my options.
I'm running Win 10 64bit. Here are some things I've tried with no resolution:
-Tried all port forwarding enabled servers with same result
-Disabled/uninstalled TinyWall and Avast Antivirus
-Uninstalled and reinstalled PIA v77
-Uninstalled PIA v77 and installed v75
Here's a relevant-seeming c/p from my pia_manager.log file:
Seems your issue is that your firewall is blocking the port forwarding API for some reason:
Permission denied means that the app has tried to connect to the port forwarding API, but has explicitly been denied so by the operating system. On Windows, that's firewall or antivirus most of the time.
You can probably verify this by simply opening the link in your browser within 2 minutes of connecting. You will probably also get an error from your browser that it can't connect because of a firewall. If it goes through and gives you a port, well you can use that port but should also make sure to check your antivirus whitelist to make sure it's allowing PIA's rubyw.exe to connect to the Internet.
I didnt think something as your provider showing you what port your connected on needed you to be some sort of script genius.
I have tried going back to earlier connections which worked before, but they still don't offer ports anymore.
I'm still getting one everytime personally but we've heard from the network team that it's a load issue on the port forward API.
should be the last one if you got one.
It works for now! Hope this helps you fix the next build PIA
This tooltip on unbuntu always seems to have troubles. I would suggest throwing it on the SETTINGS LOCKED screen as well as a backup since these tooltips have gotten broken twice now.
Not ideal but at least it works
I've reported this to the appropriate person and will update once I hear back!
In the meantime, I see you're on a Mac. You can get the port manually by running this command in a Terminal:
Are you using the x-username and password with the app by chance instead of your p-username? After discussion with the team, it sounds like what is happening is that the app tries to contact the API to get additional information and set things up, but it is being denied because it expects a p-username and that stalls the whole part that eventually shows the tooltip.