14:21:18,885 - linuxkeyring.py - INFO - _delitem_:52 - Delete key SessionData Raise PasswordDeleteError('Password not found') Self._keyring_lete_password(self._keyring_service, key)įile '/usr/lib/python3.10/site-packages/keyring/backends/kwallet.py', line 151, in delete_password 14:21:18,885 - linuxkeyring.py - ERROR - _delitem_:67 - KeyringDataNotFound: Password not foundįile '/usr/lib/python3.10/site-packages/protonvpn_nm_lib/core/keyring/linuxkeyring.py', line 58, in _delitem_ 14:21:18,883 - linuxkeyring.py - INFO - _delitem_:52 - Delete key UserData I won't have access to my Arch device for another month or so, so I don't have the error message I was seeing off hand - something about no key storage found or something, maybe - but I will try to follow up with another comment containing the exact error message, if all answers containing systemd service examples remain unfruitful on my end.ĮTA: Fixed by blowing away cache and config directories, uninstalling and reinstalling, then logging in from shell with protonvpn-cli login Īnybody else having trouble signing in? I'm getting this in the log: 14:21:18,693 - utilities.py - INFO - ensure_internet_connection_is_available:20 - Checking for internet connectivity Has anyone successfully gotten a systemd service written to get ProtonVPN connected on startup on an Arch system? I've seen examples that Ubuntu users have posted, elsewhere, but I can't seem to get it to work. I may be missing some understanding, but how can I know that my network traffic is actually going through that proton0 tunnel when I run a protonvpn-cli connect. command, I can see the tunnel (named proton0) appear via an ifconfig command, but the /etc/iptables/les file remains untouched. In that case, it named itself tun0.Īfter running a protonvpn-cli connect. When I installed their CLI tooling, it automatically went into my /etc/iptables/les file and added some things to route traffic via their tunnel, which can itself be seen by running an ifconfig command in a terminal.

Protonvpn linux