search

walterl / proton-privoxy

Privoxy over ProtonVPN in Docker
MIT License
113 stars 29 forks source link

Authentication failed #52

Open Tom-S183 opened 6 months ago

Tom-S183 commented 6 months ago

Console keeps spamming this message: 2024-05-13 12:13:48 [!] Authentication failed. 2024-05-13 12:13:48 [!] Please make sure that your Username and Password is correct. 2024-05-13 12:13:48 Failed to bring up VPN :( 2024-05-13 12:13:48 Device "proton0" does not exist. 2024-05-13 12:13:53 There is already a VPN connection running. 2024-05-13 12:13:53 Terminating previous connection... 2024-05-13 12:13:53 Connecting to NL#256 via UDP... 2024-05-13 12:13:53 [!] Authentication failed. 2024-05-13 12:13:53 [!] Please make sure that your Username and Password is correct. 2024-05-13 12:13:53 Device "proton0" does not exist.

I am sure the credentials are correct. I used my normal ProtonVPN login and the OpenVPN / IKEv2 credentials. Both didn't work.

Here is the command I used: 

docker run -d --device=/dev/net/tun --cap-add=NET_ADMIN -v /etc/localtime:/etc/localtime:ro -p 8888:8080 -e PVPN_USERNAME=user -e PVPN_PASSWORD=pass --name proton-privoxy walt3rl/proton-privoxy
Cyber-Broccoli commented 5 months ago

Same issue on my side. Tried to run protonvpn init but it did not fix the issue.

taconi commented 5 months ago

+1

kilbouri commented 5 months ago

Make sure you've read this: https://github.com/walterl/proton-privoxy/issues/44

I just had this exact issue, because I misunderstood the docs. You can find the credentials you're supposed to give under the "Account" tab in your ProtonVPN dashboard.

Cyber-Broccoli commented 5 months ago

On my side, it was a DNS issue from inside my docker. Solved.

LakshayZoof commented 3 weeks ago

If you are on the free tier make sure to specify that in the docker compose file - PVPN_TIER=0

mooleshacat commented 2 weeks ago

One other thing to note specific to proton, I have noticed with using 4 containers (plus my desktop/mobile) making 6 connections, I only have 4 connections left.

I had an issue where I was restarting containers too fast, and that temporarily adds 1 connection to your account. In my case I was adding 4 each time I restarted all my containers, easily putting me over limit. I am not sure how long until the stale connection falls off.

So if you have 4 containers, I would not restart them or change servers too often, as you can hit your limit of 10 and then they fail to authenticate and/or kick off your desktop/mobile clients.

Personally I keep 4 connections spare in case I need a new server or reboot container.