PIA: looses connection every 24 hours

[gurabli]

I had fully working system for a long time. Now, for few weeks, the connection to PIA brakes in a time of 24 hours or less. I can access qbit UI, but nothing is downloading. Need to restart container and zhan everything runs just fine. Any idea why? Don't have the logs now, but it looks that can't resolve DNS after a while.

Anybody else having this issue with PIA?

[gaiacanon]

Mine stopped downloading anything at all starting last night. Several restarts of the containers and still nothing.

My torrent shows 7 seeds, but I'm not connected to any

[mtalexan]

I had a similar problem when using ProtonVPN as the openvpn provider. In my specific case it turned out that ProtonVPN had a specific set of VPN servers they designated for Torrent traffic, and all the other servers had network bandwidth shaping rules that would cause Torrent-like traffic to be heavily de-prioritized until it was effectively non-existent. Once I figured out what that correct server list was and updated my ovpn file accordingly, everything started working just fine again.

tl;dr My experience with ProtonVPN suggests it's a VPN provider-side problem. Maybe you're pointing to the wrong PIA servers?

[KENNNNNT]

@mtalexan I am also using ProtonVPN, I have the p2p .opvn files (switz, sweeden etc) in my appdata\openvpn, however cannot get the container to run. When I was using PIA it was working fine, after adding the AES-256-CBC string to the .opvn files, however the proton files have this value included yet the container logs still errors on it, and fails to run. Any advice?

[mtalexan]

I forked this and the arch-qbittorrentvpn repos about a yrar ago to implement support for multiple remote lines in the ovpn files, something binhex decided to implement differently about 2 months ago rather than using my pull requests, so I've been on that for a while. As of my fork, the AES-256-CBC line in the Proton VPN ovpn was working just fine. That suggests it could be some other change binhex made, or it could be a result of a newer openvpn client version.

I'd suggest you start by getting a pristine copy of the ovpn file, copy it into the location the container uses, and after starting the container, diff the two files. The ovpn file is semi- silently modified in binhex's version to strip unsupported lines and modify others into a preferred form that won't need extensive processing during subsequent runs. It would be worth checking to see what the differences are from the original since that caused me a lot of problems in the past.