Zeee
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Zeee
-
-
19 hours ago, binhex said:18 hours ago, Katherine said:
I was using the "PPTP/L2TP/SOCKS" username and password which starts with an x--------.
With the next-gen network, PIA wants everyone to use their login username and password which start with p--------. Once I switched credentials, I was able to authenticate right away.
Well, damn. I feel like a right idiot. Thank you both! Got it working.
I'll go and hang my head in shame over there -----> somewhere...
- 1
-
On 11/3/2020 at 12:26 PM, Katherine said:
I received the message in the log to switch to PIA's next-gen network:
VPN configuration file '/config/openvpn/openvpn.ovpn' 'remote' line is referencing PIA legacy network which is now shutdown, see Q19. from the following link on how to switch to PIA 'next-gen':- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md exiting script...
I downloaded the next-gen ovpn config file from the link in the FAQ. I used the same credentials.conf as my previous settings but replaced everything else. This my ovpn file:
client dev tun proto udp remote de-berlin.privacy.network 1198 resolv-retry infinite nobind persist-key cipher aes-128-cbc auth sha1 tls-client remote-cert-tls server auth-user-pass credentials.conf compress verb 1 crl-verify crl.rsa.2048.pem ca ca.rsa.2048.crt disable-occ
For some reasons, I am unable to connect and I keep getting AUTH_FAILED error in a loop which freezes the Unraid webui.
DEBG 'start-script' stdout output: AUTH: Received control message: AUTH_FAILED DEBG 'start-script' stdout output: SIGTERM[soft,auth-failure] received, process exiting
Has anyone encountered this problem?
I've been having this problem for what feels like weeks now. No matter what I do I cannot get it to auth. But when I went back to the old-gen network, everything worked fine. Here's what I've tried:
- downloaded many versions of the NextGen.zip with all the ovpn files in it
- tried many different .ovpn files in the .zip
- generating a new password from the PIA site and updating the docker parameters
- modding the .ovpn to remove the built in CA and CRL and use the files
- modding the .ovpn file to specifically include "credentials.conf" nest to "auth-user-pass"
- deleted the perms.txt file and restarted
- completely cleared out the containers' volume on the drive and started again
I could really use some advice on what I'm doing wrong. Why is the nextgen network rejecting my credentials?
Here's the .ovpn file:
client dev tun proto udp remote ca-toronto.privacy.network 1198 resolv-retry infinite nobind persist-key persist-tun cipher aes-128-cbc auth sha1 tls-client remote-cert-tls server auth-user-pass credentials.conf compress verb 1 reneg-sec 0 crl-verify crl.rsa.2048.pem ca ca.rsa.2048.crt disable-occ
Here's my docker-compose:
torrent: cap_add: - NET_ADMIN image: "binhex/arch-rtorrentvpn:latest" container_name: "torrent" hostname: "torrent" restart: "always" network_mode: "bridge" ports: - <ports> volumes: - <volumes> environment: - VPN_ENABLED=yes - VPN_USER=<user> - VPN_PASS=<password> - VPN_PROV=pia - STRICT_PORT_FORWARD=yes - ENABLE_PRIVOXY=yes - ENABLE_AUTODL_IRSSI=yes - ENABLE_RPC2=yes - ENABLE_RPC2_AUTH=yes - ENABLE_WEBUI_AUTH=no - RPC2_USER=<password> - RPC2_PASS=<password> - LAN_NETWORK=192.168.1.0/24 - NAME_SERVERS=1.1.1.1,1.0.0.1 - PHP_TZ=<timezone> - TZ=<timezone>
Any help would be really appreciated.
[Support] binhex - rTorrentVPN
in Docker Containers
Posted
No, it's not just you. I've had the same problem crop up in just the past few days with the container previously working fine for months.
I've tried starting the container fresh with just my VPN details and I still get this problem. So, I think something more sinister is going on.