search

walterl / proton-privoxy

Privoxy over ProtonVPN in Docker
MIT License
110 stars 27 forks source link

Constant disconnects, auth failures #58

Closed mooleshacat closed 2 hours ago

mooleshacat commented 3 hours ago

I get the following in my logs:

root@vps-151c25b9:/usr/local/invidious-stack/run/proton-privoxy-4# docker logs proton-privoxy-1
Connecting to CA#367 via UDP...
Connected!
2024-10-19 16:02:20.307 7f62a5f83b48 Info: Privoxy version 3.0.33
2024-10-19 16:02:20.307 7f62a5f83b48 Info: Program name: privoxy
2024-10-19 16:02:20.307 7f62a5f83b48 Info: Listening on port 8080 on IP address 0.0.0.0
Connecting to CA#355 via UDP...
Connected!
ln: failed to create symbolic link '/app/proton-privoxy/templates': File exists
2024-10-19 16:03:12.022 7fef9b4e6b48 Info: Privoxy version 3.0.33
2024-10-19 16:03:12.022 7fef9b4e6b48 Info: Program name: privoxy
2024-10-19 16:03:12.022 7fef9b4e6b48 Info: Listening on port 8080 on IP address 0.0.0.0
Connecting to CA#362 via UDP...
Connected!
ln: failed to create symbolic link '/app/proton-privoxy/templates': File exists
2024-10-19 16:04:12.294 7fbf36c13b48 Info: Privoxy version 3.0.33
2024-10-19 16:04:12.294 7fbf36c13b48 Info: Program name: privoxy
2024-10-19 16:04:12.295 7fbf36c13b48 Info: Listening on port 8080 on IP address 0.0.0.0
Connecting to CA#381 via UDP...
Connected!
ln: failed to create symbolic link '/app/proton-privoxy/templates': File exists
2024-10-19 16:05:11.840 7f5e0a14eb48 Info: Privoxy version 3.0.33
2024-10-19 16:05:11.840 7f5e0a14eb48 Info: Program name: privoxy
2024-10-19 16:05:11.840 7f5e0a14eb48 Info: Listening on port 8080 on IP address 0.0.0.0
Connecting to CA#361 via UDP...
Connected!
ln: failed to create symbolic link '/app/proton-privoxy/templates': File exists
2024-10-19 16:06:11.787 7f1d1b682b48 Info: Privoxy version 3.0.33
2024-10-19 16:06:11.787 7f1d1b682b48 Info: Program name: privoxy
2024-10-19 16:06:11.787 7f1d1b682b48 Info: Listening on port 8080 on IP address 0.0.0.0
Connecting to CA#361 via UDP...
[!] Authentication failed.
[!] Please make sure that your Username and Password is correct.
Device "proton0" does not exist.
Failed to bring up VPN :(
There is already a VPN connection running.
Terminating previous connection...
Connecting to CA#361 via UDP...
[!] Authentication failed.
[!] Please make sure that your Username and Password is correct.
Device "proton0" does not exist.
Failed to bring up VPN :(
Connecting to CA#355 via UDP...
[!] Authentication failed.
[!] Please make sure that your Username and Password is correct.
Device "proton0" does not exist.
Failed to bring up VPN :(
There is already a VPN connection running.
Terminating previous connection...
Connecting to CA#355 via UDP...
[!] Authentication failed.
[!] Please make sure that your Username and Password is correct.
Failed to bring up VPN :(
Device "proton0" does not exist.

Every time this happens I reset my username/password and reconfigure proton-privoxy, it will work for about 1 minute maximum, then crap out again. When I check docker logs I get the above, saying my authentication failed.

The username and password is correct.

I am contacting proton vpn because it could possibly be related to the issue I have where if I connect more than 4-6 devices it kicks off my desktop claiming I have "too many connections" but the plan I have allows for 10 connections.

Is there a reason why the connection works, then fails 60 seconds later?

mooleshacat commented 3 hours ago

Proton support asked me if I was reconnecting frequently or using scripts to change servers.

I replied with "no, I just am trying to get a basic connection. I have no scripts (yet) I can't seem to get 6 connections nevermind the 10 I am supposedly allowed"

Looking at the logs, it appears as though proton gets connected, but then tries to reconnect for some reason even though it already has a connection.

Testing with only 1 container to see if it disconnects or if it is because I have multiple containers. It is possible the connection is being dropped and privoxy tries to reconnect, making the server think I have 1 extra connection for a minute or two. I suspect the disconnect is frequent enough when combined with 4 containers causes more than 10 connections, which would be why proton denies authentication and it says wrong password.

mooleshacat commented 2 hours ago

Update: same issue with only 1 container.

It connects, then few minutes later gets disconnected, and claims "authentication failure" when reconnecting.

I am out of solutions.

mooleshacat commented 2 hours ago

It appears I have found the problem.

I added to the crontab to restart services, including proton-privoxy, every minute.

What I suspect was happening was the restarts would cause stale logins to increase, taking me to my limit of 10 connections.

By removing the crontab entry to restart the containers, it appears to be working properly.

I am tracking this issue here https://github.com/catspeed-cc/invidious/issues/36 but I will close this ticket and reopen if I have further issues.

Thanks :)