cannot generate PIA token anymore

binhex / arch-qbittorrentvpn

Docker build script for Arch Linux base with qBittorrent, Privoxy and OpenVPN

GNU General Public License v3.0

473 stars 48 forks source link

cannot generate PIA token anymore #86

Closed ljmerza closed 3 years ago

ljmerza commented 3 years ago

started yesterday, dont see anything about outages.

2021-04-16 09:39:19,363 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://212.102.35.130/authv3/generateToken'
[info] Retrying in 10 secs...

tezgno commented 3 years ago

Same issue. Started day before yesterday for me.

tezgno commented 3 years ago

Reverting back to 4.3.3-1-05 seems to resolve the issue for me. Something related to 4.3.3-1-06 and PIA is causing issues.

ljmerza commented 3 years ago

I tried that and it didn't work for me. The only difference between 05 and 06 is adding binding qbittorrent to the network interface so I don't think the version change itself fixed it and you got lucky.

tezgno commented 3 years ago

Try downloading and replacing the latest PIA openvpn files.

We are connecting using Wireguard

ljmerza commented 3 years ago

just tried that and it didnt work. here's my docker compose

qbittorrentvpn:
    image: binhex/arch-qbittorrentvpn:4.3.3-1-06
    env_file: env/qbittorrentvpn.env
    restart: always
    ports:
      - 6881:6881
      - 6881:6881/udp
      - 8118:8118
      - 8087:8087
    volumes:
      - /home/user/docker:/config
    devices:
      - /dev/net/tun
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    privileged: true

TZ=America/New_York

PUID=1000
PGID=1000

VPN_ENABLED=yes
VPN_CLIENT=wireguard
VPN_USER=xxx
VPN_PASS=xxx
VPN_PROV=pia

STRICT_PORT_FORWARD=yes
ENABLE_PRIVOXY=yes
DEBUG=true
WEBUI_PORT=8087
LAN_NETWORK=192.168.1.0/24,192.168.2.0/24
NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

tezgno commented 3 years ago

I tried that and it didn't work for me. The only difference between 05 and 06 is adding binding qbittorrent to the network interface so I don't think the version change itself fixed it and you got lucky.

So, I switched back to 06 and it failed immediately. I then went back to 05 and it failed. Completely stopped my container and started it back and it connected just fine. Went back to 06 and it failed again. Back to 05 and is working. Stopped and started several times and is still working. Back to 06 and failed. No matter what I want to do, 06 doesn't work at all. Version 05 is hit/miss.

ljmerza commented 3 years ago

@tezgno which server are you using? ive tried all the CA servers

tezgno commented 3 years ago

@ljmerza Ok... further digging, this is a PIA issue. Switch to Poland (poland.privacy.network) and see if that connects for you.

ljmerza commented 3 years ago

doesnt seem to work from that server either

[warn] Unable to successfully download PIA json to generate token from URL 'https://143.244.43.129/authv3/generateToken'

tezgno commented 3 years ago

That's weird. It's working fine for me on 06. If I switch back to what I had before, which was Toronto, it fails. But Poland appears to be working. How I was able to find this is because another tool is having the exact same problem and people are reporting getting the same errors with different tools. All starting 1-2 days ago.

ljmerza commented 3 years ago

i was able to get any vpn server working by switching to VPN_CLIENT=openvpn but that removes wireguard. i'll leave this open since the original issue isnt solved.

TopCheddar27 commented 3 years ago

Just also chiming in to say I am seeing the exact same issues. I am going to try the above (reverting versions or switching endpoints) to see if that helps with the token.

I would like to note this has seemed to start right after I pulled the latest image for what it's worth.

northernpowerhouse commented 3 years ago

Binhex has fixed this in the deluge client, and it'll be commited to the qbittorrent version shortly

binhex commented 3 years ago

ok try pulling down latest guys

WTFox commented 3 years ago

Working now, thanks!

tezgno commented 3 years ago

Working for me as well