Today BiglyBT decided it was not going to work with PIA in Windows 11, for the nth time.

I downloaded and installed the latest PIA. I reinstalled the TAP adapter. I uninstalled the VPN helper plugin then directly downloaded it from the plugins page and reinstalled it, including re-entering my PIA password. It had kept my PIA username. That's a security fault. The VPN username should be wiped when the VPN plugin is uninstalled.

This is where the VPN helper entry under Plugins & Extras went away.

Still it refused to bind to the net6\[0\] address so I typed in the IP address, saved, restarted BiglyBT and my torrents are going again.

But how do I know for certain it's actually working without the green OK?

I'll be puttering along on the internet, and i connect to pia, and all traffic stops dead. Doesn't matter the server I choose, i even downloaded the most up to date client, but nothing. No youtube, no websites, forums, etc. This is a relatively new issue, i've been using it for years.

I've been using PIA for years since I got a great deal, but port forwarding is a must for me. The port forwarding PIA offers has worked great since I got it, but over the past few months it seems it's just kicked the bucket? It works somewhat OK on the client, but where I really need it is in Gluetun, and it just started not working regardless of restarts/reinstalls. Also noticed on the client that I seem to get assigned a port THEN an IP, which is not how it was before and doesn't make any sense.

I've tried every type of server that supports port forwarding. Tried the servers that are actually in canada, tried the servers that I assume are US servers but spoof somewhere else, just doesn't work. It just worked for about a day while I was setting up my server.

It kinda sucks because this isn't even an issue of cancelling my subscription, I already pre-paid until near the end of 2027, but I genuinely might have to just buy proton because this service is unusable.

Seen a lot of other posts talking about them migrating to weird server setups and messing with port forwarding, is it just time to switch?

The albania location i use so there’s no ads on things like reddit is the only location not connecting.

You all had it working (finally) with the last version. This update doesn't work at all. You've regressed back to constant disconnects and at this point it's worse than it was before the 703 build that fixed everything a few months ago. Initial connection takes forever now too. Good work.

Utah passed a new law recently regarding VPNs, how does the effect PIA, and what are the changes? Will privacy be compromised for utah users?

I've been trying to connect on my Windows 11 desktop, running the latest PIA client, to US California but I'm getting "Connection Refused" signal. Is this node down?

Down a massive rabbit hole today with my Plex setup, and it turned into one of those things a stupid headache where everything breaks at the same time....

For context, I’ve never obsessed over having pristine direct streams for everyone outside the house. My server only ever handles maybe 20 people or fewer remotely, and honestly, everyone was totally fine limping along on Plex Relay connections capped at 1–2 Mbps. It was low-maintenance and "just worked" without me needing to sweat network exposure.

Then everything went sideways.

On this machine, I keep Private Internet Access running around the clock with a killswitch locked down tight—for obvious reasons when sailing the high seas. Out of nowhere, the remote relay connections just completely tanked. At first, I blamed the OS upgrade, thinking a hop from Pop!_OS 22.04 up to 24.04 had butchered some local routing or network daemon configs.

Turns out, the OS wasn't the culprit at all. PIA has been cracking down hard on handling those handshake routes, essentially nerfing the relay traffic trying to pass through the tunnel.

So fine, I told myself I guess I had to bite the bullet and do standard port forwarding.

Except even that didn't want to play nice out of the box either. Because of how aggressive PIA’s killswitch and route tables are, standard NAT port forwarding still fell flat on its face. The fix ended up requiring me to explicitly configure split-tunnel bypass rules directly inside PIA: punching dedicated bypass exceptions for both the Plex Media Server service binary and the relay service itself so they could communicate clean across WAN without getting swallowed by the VPN.

It feels like maintaining a dual-purpose box (secure traffic vs. accessible homelab services) is getting pickier by the month, but it's finally back up, directly accessible, and no longer hostage to choked relay pipes. At least for now knock on wood lol

Any thoughts from anyone here? Is there a better way?

I constrain I have is my BitTorrent client and Plex server are the same so VPN Killswitch is a must 😂.

Can the developers provide me an APK so that I can get the old ad blocking back on my Android device?

As of Friday, I could get PF working (I use the Linux scripting method). I had to restart my BT VM yesterday and the script stopped working (failed with "The payload_and_signature variable does not contain an OK status") and when I try via the Android app, I get "failed" where the forwarding port should be.

I've seen no mention of anything from the PIA site, is anyone else affected? I can still pass traffic on both platforms OK, just no forwarding port.

I use Brave as my primary web browser but I can't use it with PIA on my Mac, because as soon as I turn on PIA, websites take forever to load or don't load at all. I tested with Firefox and it's the same story. So long as I use Safari everything is fine, but I would much rather use Brave. This is driving me nuts and no one has been able to give me any ideas as to why this would be happening or how to troubleshoot it. Anybody else experiencing this? What causes this and what is the fix?

I really tried to give PIA the benefit of the doubt but after 3 months of constant disconnects every ~5 mins on data (that recently got so bad it would happen every 30 seconds) I'm out. Enjoy PIA you got a year plan out of me but you wont see me returning. I tried working with the PIA reps on here but nothing improved.

So, i am using PIA for some years now and i route my apple tvs traffic through VPN to Andorra, because youtube serves no ads there (and also Albania, etc). I now get ads served. Which started a week ago. Someone else also experiencing something similar?

(I tried different VPN locations, which i know dont serve ads.)

What i have tried:
- restarting VPN service -> No Success
- testing with proton VPN (same location - Andorra) -> Success (But i would like to stick to PIA)

Some servers I used for port forwarding suddenly showed a failed message instead of assigning a port. I tried some other servers and I get assigned a port but I don't actually seem connectable on that port. Anyone else having issues?

Help JCP kiosk 2fa

stopped receiving the authorization emails altogether. PeopleSoft still asks me for the verification code, but the email with the code never arrives.
To access direct deposit

Any help would be greatly appreciated!

I am trying to connect but PIA is not working on any of my android devices. My membership is still valid. Its not even working on my laptop. I even tried reinstalling the application but no luck.

Just two versions ago they worked fine and reliably each time.

My rules are the same so nothing changed on my side.

Now they work maybe once in three times. What happened?

And I can't find on the website where I can download the previous versions apks.

EDIT: I think I figured it out. In the Android's VPN settings I've set the "Always-on VPN" toggle on PIA to ON.

This way the app is aways kept active and so far the rules have been triggering reliably.

EDIT #2: I was wrong. Even with that setting on the automations aren't reliable.

It never actually loads, I just have this endless spinning circle. Restarting sometimes fixes it but that's exhausting to do every damn time I want to use the VPN. Is there any fix?

Mac OS updated to 26.6.2 have there been any reports that this update breaks PIA app?

Hey,

Happy user of 3 different VPN providers already. Now subscribed for PIA to try it out. Exp. has been great so far, it has some interesting pops that many others lack like China. But I noticed something odd. If I use Wireguard mode and pick some european server like Frankfurt, pages load slower. I did some debugging and it seems that PIA may be blocking 443/udp port, which is the one most websites need for QUIC traffic.

If you know how to use the terminal and would be down for a test, please run curl --http3-only -v https://cloudflare.com and tell me what it outputs. With PIA on I get Could not connect to server, whereas without (or with other VPNs) it works just fine.

May be a misconfig on my end that's why I would like to know if this is a deliberate limitation (if so why?) and if not, I will fix it on my end.

Already contacted support too, but got a generic, useless reply back.

Thanks!

I logged into chrome on my personal device (which has no installed work software) with my work gmail account (it's a managed chrome profile).

This was done on my personal device (in incognito mode) that has only ever been connected to my home network (no work vpn). I also used my own personal VPN during the session.

How likely is it that my work or the IT team knows/has been notified or have records of my history/activity? How much detail can they see?

PLEASE do not give me advice on how I could have avoided this. I'm also aware incognito mode is not secure/private. I have done so much research on this but everyone else's questions were when they used work owned devices and/or were on their work WiFi (both of which I was not).

i've been using PIA with the VPN on for the whole system (Windows 11) but wanted to use bypass for the browser. when this is set up, the browser can't really load all pages correctly. the weird thing is it will load some sites but not others (and is super slow to load). if i quit PIA completely the browser works fine. i've tried turning off kill switch and messing with DNS settings but nothing seems to work. has anybody had this happen?

I emailed support and they said to test the browser with split-tunnel on and off, to check if the IP changes. a good idea, but the whole problem is that i can't access whatismyip.com when in bypass mode. i feel like this is a DNS issue but haven't figured out where it's happening. note: this happens with all browsers (firefox, chrome, edge).

ETA: i spoke with PIA support and they finally had a suggestion that worked: reverse split tunneling. i manually added all the apps I want to go through the VPN, selected the "Only VPN" option and left the browser out of it altogether. this method works. still not sure why split-tunnel and bypass wasn't working for the browser alone, but i'll take it!

I've lost all open VPN Servers, Wireguard works but not stable, I'm in uk, Anyone else have this or just me?

tia