You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting random vpn disconnects, most often using qbittorrent. The fault is not, however, limited to qbittorrent.
It's difficult to describe how to 'provoke' a random event. That said, start a torrent download using qbittorrent or just surf. After some random period, (minutes to many days), it will go offline. Restart the VPN, and connection is restored.
Expected behavior
The connection should not drop.
Error Messages/Program Output/Log Messages (~/.pvpn-cli/pvpn-cli.log)
Last 100 lines of /root/.pvpn-cli/pvpn-cli.log attached. There's nearly 11,000 lines/2.6Meg.
Desktop (please complete the following information):
The particular IPs vary, but with the fault occurring (It isn't now), the diagnostics are as described here:
[https://www.linuxquestions.org/questions/slackware-14/protonvpn-nuttiness-4175743576/ pvpn-cli.log
](url) pvpn-cli.log
The text was updated successfully, but these errors were encountered:
I'm getting random vpn disconnects, most often using qbittorrent. The fault is not, however, limited to qbittorrent.
It's difficult to describe how to 'provoke' a random event. That said, start a torrent download using qbittorrent or just surf. After some random period, (minutes to many days), it will go offline. Restart the VPN, and connection is restored.
Expected behavior
The connection should not drop.
Error Messages/Program Output/Log Messages (~/.pvpn-cli/pvpn-cli.log)
Last 100 lines of /root/.pvpn-cli/pvpn-cli.log attached. There's nearly 11,000 lines/2.6Meg.
Desktop (please complete the following information):
python3 --version
)] Python3-3.11.101protonvpn --version
)] 2.2.12Additional context
Add any other context about the problem
Here's some output
`here.
dec@ebony:~$ cat /etc/resolv.conf
Generated by resolvconf
ProtonVPN DNS Servers. Managed by ProtonVPN-CLI.
nameserver 10.20.0.1
dec@ebony:
$ route$ ping 10.20.0.1Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.20.0.1 128.0.0.0 UG 0 0 0 proton0
default chateau.dec 0.0.0.0 UG 1002 0 0 eth0
10.20.0.0 0.0.0.0 255.255.0.0 U 0 0 0 proton0
128.0.0.0 10.20.0.1 128.0.0.0 UG 0 0 0 proton0
146.70.48.2 chateau.dec 255.255.255.255 UGH 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 1002 0 0 eth0
dec@ebony:
PING 10.20.0.1 (10.20.0.1) 56(84) bytes of data.
64 bytes from 10.20.0.1: icmp_seq=1 ttl=64 time=39.0 ms
64 bytes from 10.20.0.1: icmp_seq=2 ttl=64 time=22.7 ms
--- 10.20.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 22.658/30.828/38.999/8.170 ms
dec@ebony:~$ ping 146.70.48.2
PING 146.70.48.2 (146.70.48.2) 56(84) bytes of data.
64 bytes from 146.70.48.2: icmp_seq=1 ttl=54 time=28.8 ms
64 bytes from 146.70.48.2: icmp_seq=2 ttl=54 time=30.4 ms
--- 146.70.48.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 28.768/29.600/30.432/0.832 ms`
The particular IPs vary, but with the fault occurring (It isn't now), the diagnostics are as described here:
[https://www.linuxquestions.org/questions/slackware-14/protonvpn-nuttiness-4175743576/
pvpn-cli.log
](url)
pvpn-cli.log
The text was updated successfully, but these errors were encountered: