• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bwobba's Achievements


Newbie (1/14)



  1. I put this in the wrong thread no wonder it wasnt appearing >.<. Enjoy the dono
  2. Hi All, Just a note, Anyone with the AUTH_FAILED issue associated recently with PIA looks to have been resolved ive been able to connect now using both OpenVPN and Wireguard and got PF working. Thanks all that helped. @binhex Thanks for the assistance to rule out the container ... wouldnt happen to have a donations link anywhere would you?
  3. Yes correct two issues as im testing both wireguard and openvpn both are not working. OpenVPN as you mention look to be PIA with new accounts (me yaya!). Wireguard gives me the numeric literal at line 4 (supervisord-wireguard log attached earlier). Then fails to generate the token required for auth. Which then loops continuously. Lucky for me i can use my current VPN w/o PF but sucks as it seems to be PIA. I've never had an issue with your great containers! Thanks for all the hard work.
  4. Cheers!, I have the correct setting in my live container using qbit instead... Overlooked it, removes the warning but the same final errors occur. i.e. Failed Auth / numeric literal at line 4
  5. Hi, I have done it for both scenarios, OpenVPN and wireguard. Please see attachments. Let me know if i can provide anything else. supervisord-wireguard.log supervisord-OpenVPN.log
  6. There looks to be a suggestion to try the latest version of OpenVPN 2.4.x. I am no docker pro but am happy to test if someone can tell me what command to include to pull OpenVPN 2.4 instead of OpenVPN 2.5 to rule in or out of the issue.
  7. Hi @binhex, I believe the reddit post reflects a number of the users already in this thread. As we can all see PIA isnt answering the thread with little more then check your password which is weak. When using the wireguard method, I have not been able to get it to generate the wireguard config thus no endpoint that im aware of is actually set as yet, i.e. should default to Netherlands; 2020-12-07 09:20:05,192 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token from URL '' [info] Retrying in 10 secs... 2020-12-07 09:20:15,218 DEBG 'start-script' stderr output: parse error: Invalid numeric literal at line 4, column 0 When using the OpenVPN method; Each of the following default PIA .opvn files have been tried in conjunction with ca.rsa.2048.crt & crl.rsa.2048.pem. 1. netherlands.opvn ( 2. au_sydney.opvn ( 3. ca_montreal.opvn ( All presented with the AUTH_FAILED issue. With the standard associated cipher warning as i have used stock standard PIA opvn files; 2020-12-07 09:33:32 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning. I have noticed something new an Invalid prefix issue not sure where its cropping up from heres the extract of the log; 2020-12-07 09:33:32,086 DEBG 'start-script' stdout output: [info] Docker network defined as 2020-12-07 09:33:32,088 DEBG 'start-script' stdout output: [info] Adding as route via docker eth0 2020-12-07 09:33:32,089 DEBG 'start-script' stderr output: Error: Invalid prefix for given prefix length. 2020-12-07 09:33:32,089 DEBG 'start-script' stdout output: [info] ip route defined as follows... Any help would be amazing. KR, BW
  8. @chris.warren.melb Given most new PIA users who are using this configuration are having issues. Seems more then coincidence. For example my old VPN provider is still working albeit without PF'ing which is why the move to PIA was done. I believe @binhex has confirmed above he and others in the post are able to log into their existing PIA accounts with PF both on OpenVPN and Wireguard with no issue. I have used it in both binhex-delugevpn and binhex-qbittorrentvpn (not to discuss that here) and the behaviour described above is identical. If someone can come up with another suggestion i am all ears to try it.
  9. @Liam_Galt, @Seraph91P I joined for a similar reason to move from not being connectable to being connectable due to PF. Honestly ill give PIA a week to fix it if they dont ill ask for a refund. Hopefully they'll fix whatever is stopping the auth from occurring. Had the same idea lets use wireguard but have the same line 4 error. I have tried all the checklists throughout the thread with no love. Is there a log i could provide around the wireguard line 4 error? I suspect its to go with auth too but no way to be sure at the moment. I suspect. Its only a 2 element json reply not the expected 4+?