Comment # 1 on bug 1230023 from Alexandre Vicenzi

Firstly, there are two Proton VPN packages.

Secondly, Proton VPN does not support openSUSE officially, and any request to
their support will lead to the same reply.

Thirdly, this is a known bug that Proton is aware but it has little priority to
fix because it does not happen in Ubuntu (their official supported distro of
choice).

The packages available on Leap/SLE are deprecated (protonvpn-gui and
protonvpn-cli), because they are based on the old Linux app which reached EOL
in 2023 [1]. There's no guarantee that they will work in the future, and to be
honest, they should be removed from future releases of openSUSE.

The package available on Tumbleweed (proton-vpn) is currently maintained, but
this does not work on Leap due to missing dependencies.

From my understanding, the issue is related to this bug [2], and in theory,
this happens on both versions of Proton VPN either on GNOME, KDE, or else.

The solution is rather easy, unlock your keyring before using Proton VPN, as
Proton fails to connect due to missing credentials locked in the keyring and
asking for it while trying to connect.

Another solution is, once you get a request for a password only type your
user/root password, this will unlock the keyring. Cancel the current connection
because it is already broken and click connect again. It should work now
because the keyring has been unlocked.

If the internet stops working, it is very likely that Kill Switch is enabled in
the settings, if a connection fails it kills it entirely if this is enabled.
Either disable this setting or cancel the current failed connection (if
possible).

[1]: https://github.com/ProtonVPN/linux-app
[2] https://github.com/ProtonVPN/proton-vpn-gtk-app/issues/43