2 Likes
This started happening to me on September 28. I couldn’t get the connection to operate at all. I saw that the client was stuck on a certain server. I tried reconnecting. I attempted to connect to another nation. Nope, the same server each time.
I tried deleting and reinstalling, but it didn’t work. (At least I’m back on the current version. It would be wonderful to have a signal when an update is available, but I digress.)
On September 30, I discovered that Proton was back up.
When I visited Proton’s status page, there was no indication of a problem with the VPN.
BTW, Proton, you really should concentrate on documentation. It’s difficult to find download and installation instructions for the Linux CLI.
3 Likes
And the GTK app isn’t functioning for me either
2 Likes
You must utilize Wireguard or OpenVPN configuration files, which are currently the only available options.
You are not the only one furious about it; the CLI was quite nice.
Furthermore, the GTK app performs poorly on Linux and is only supported by two distributions. Works on Mint, although sluggish.
2 Likes
Alternatively, you can continue using the deprecated but newly updated CLI. Hopefully, it will last till the replacement arrives.
2 Likes
As Nelizea and others have pointed out, we presently do not have an official CLI. For quite some time, the community CLI hasn’t been utilized or updated. As you can see here: GitHub - Rafficer/linux-cli-community: Linux command-line client for ProtonVPN. Written in Python., I merged an update 8 months ago to ensure that our backend does not break the CLI, but it may do so in the future if we need to make changes to our API, and we cannot continue to support tools that are no longer being maintained while restricting ourselves with deprecated software.
2 Likes
I would strongly encourage Proton to prioritize a Linux CLI over a DE-specific (Gnome) GUI client. As others and myself have found, the existing Linux GUI client isn’t quite suitable for those of us not using Gnome, which is a lot of users.
1 Like