Open notDavid opened 3 years ago
I noticed another error in the journal/log while running the login command:
$ journalctl -f
Aug 22 12:36:33 pi5 dbus-daemon[3935]: [session uid=1000 pid=3935] Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.2' (uid=1000 pid=3937 comm="/usr/bin/gnome-keyring-daemon --start --foreground" label="unconfined")
Aug 22 12:36:33 pi5 org.gnome.keyring.SystemPrompter[8301]: Unable to init server: Could not connect: Connection refused
Aug 22 12:36:33 pi5 gcr-prompter[8301]: cannot open display:
Aug 22 12:36:33 pi5 dbus-daemon[3935]: [session uid=1000 pid=3935] Activated service 'org.gnome.keyring.SystemPrompter' failed: Process org.gnome.keyring.SystemPrompter exited with status 1
Aug 22 12:36:33 pi5 gnome-keyring-daemon[3937]: couldn't initialize prompt: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.keyring.SystemPrompter exited with status 1
Aug 22 12:36:33 pi5 gnome-keyring-d[3937]: couldn't initialize prompt: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.keyring.SystemPrompter exited with status 1
Is this happening because i'm running a headless server / not having a Desktop installed?
Apparently. A bit weird for a cli tool not to work on a headless server...
Please note that, at the present time, the new ProtonVPN CLI doesn’t support Split Tunneling and doesn’t run on headless servers.
Unbelievable, a headless version is a MUST.
I have run into this as well, but on my laptop, that ist neither headless, nor a server.
Please reopen, this isn't a cli tool until it works headless.
Issue appears to be around how the keyring is storing data: https://keyring.readthedocs.io/en/latest/#using-keyring-on-headless-linux-systems
On headless, I see these options
keyring --list-backends
keyring.backends.fail.Keyring (priority: 0)
keyring.backends.chainer.ChainerBackend (priority: 0)
On a linux with gui (even just SSH'd in), I get these
-> % keyring --list-backends
keyrings.cryptfile.file.EncryptedKeyring (priority: 0.6)
keyrings.cryptfile.cryptfile.CryptFileKeyring (priority: 2.5)
keyring.backends.fail.Keyring (priority: 0)
keyrings.cryptfile.file.PlaintextKeyring (priority: 0.5)
keyring.backends.chainer.ChainerBackend (priority: 10)
keyring.backends.SecretService.Keyring (priority: 5)
I got further along by installing gnome-keyring
which forces a UI prompt via X11. I still can not connect due to unknown error during server connect.
this program is terrible.
fyi, there seems to be a new beta version here (i haven't tested it yet): https://protonvpn.com/support/early-access-linux-vpn/
via https://reddit.com/r/ProtonVPN/comments/q8my4j/grab_an_exclusive_seat_in_protonvpns_linux_beta/
@notDavid I've just tried this too but it doesn't fix the issue.
If this is totally reliant on X11 libs, I think it's going to be a ground up remake to fix. I have to say, I'm pretty surprised that a headless use case wasn't considered with a CLI app; it seems to be to be the number 1 use case for this. Pretty disappointed considering we pay for it.
Lol, seriously eh?
And I was just thinking, well if i try the tina approach it's gotta be easier then all the networkmanager rabbit holing 😂
In case anyone misses it, the workaround is to install gnome-keyring
(i think).
UPDATE: ahh i guess to be fair it is mentioned here in step 4: https://protonvpn.com/support/official-linux-client-arch/
i cant believe this is still broken. totally useless garbage on a non GUI install
This makes no sense at all. It's a CLI, which is not a CLI, because it needs a GUI?! More specific: uses the keyring of Gnome. What went wrong there on design/architecture level?!? They should write at least first in repo: "This is not a real CLI, you need Gnome". Currently, this is deliberate misdirection and I ask to explain this deliberate deception.
Have anyone a quickfix/work around?
@REficul-dRAw I use this one, and have basically given up on them actually doing anything to fix this. https://github.com/Rafficer/linux-cli-community
it's 2023 and I can confirm it's still broken, I am using swayWM/hyprland on arch and it's causing issues I even went ahead and installed gnome-keyring can't believe this is an official package... What's the point of cli version if it requires GUI??
Hi there,
I have this issue: #7 on Ubuntu 64-bit running on a Raspberry Pi4. Please advise thank you;
~/.cache/protonvpn/logs/protonvpn.log :
``` 2021-08-22 11:15:07,653 — settings_backend.py — INFO — get_backend:13 — Settings backend:protonvpn-cli.log :
``` 2021-08-22 09:15:07,644 — cli.py — INFO — __init__:17 — ------------------------------------------------- ----------- Initialized protonvpn-cli ----------- ------------------------------------------------- 2021-08-22 09:15:07,644 — cli.py — INFO — __init__:29 — ProtonVPN CLI v3.8.0 (protonvpn-nm-lib v3.3.2; proton-client v0.5.1) 2021-08-22 09:15:07,658 — cli.py — INFO — __init__:64 — CLI command: Namespace(command='login', get_logs=False, help=False, version=False) 2021-08-22 09:15:10,462 — cli_wrapper.py — INFO — login:68 — Credentials provided, attempting to login 2021-08-22 09:15:18,743 — cli.py — INFO — __init__:17 — ------------------------------------------------- ----------- Initialized protonvpn-cli ----------- ------------------------------------------------- 2021-08-22 09:15:18,773 — cli.py — INFO — __init__:29 — ProtonVPN CLI v3.8.0 (protonvpn-nm-lib v3.3.2; proton-client v0.5.1) 2021-08-22 09:15:18,787 — cli.py — INFO — __init__:64 — CLI command: Namespace(command='c', get_logs=False, help=False, version=False) 2021-08-22 09:15:18,789 — cli.py — INFO — connect:128 — Options: Namespace(cc=None, fastest=False, help=False, p2p=False, protocol=None, random=False, sc=False, servername=None, tor=False) ```System specs:
``` $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ uname -a Linux pi5 5.4.0-1041-raspi #45-Ubuntu SMP PREEMPT Thu Jul 15 01:17:56 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux ```Not sure if this warning i got while installing is related: #46