Your Arch Linux implementation is an unusable morass of broken Python… any plans to fix?
This should be helpful. It includes the codes for Fedora/CentOS/RHEL ; Ubuntu/Linux Mint/Debian and derivatives ; Arch Linux/Manjaro.
There’s also a knowledge base article on how to install the Proton VPN Linux App on your system.
What is this? It’s been available as 1.0 for a while…
Am I suppose to see these additional options cause everything literally looks the same? Nothing changed at all
Edit there is conflicting information on the official site. It says you can just upgrade to the beta version but in another section it says proton must be completely removed first. It is now working. Just make sure to completely remove the stable version
Looks like protonvpn-cli is gone. Is there a way to do things with the command line? Is it on the map?
What is the situation on Raspbian (Raspberry Pi OS)? The Debian set-up guides states it does not work for Raspberry Pi, I tried anyway, and it definitely does not! Is there going to be a Raspberry Pi specific package any time soon?
Will port forwarding be added to the cli version too ? Or is it already available ?
Hi, I have “Proton VPN Linux Client 4.0.0b2” installed on fedora 37.
i’m a bit lost, is there multiple realeases on linux ?
there’s a protonvpn gui 1.12.0 aviable on flathub, but not updated since a year.
Quite great, but you should include more features as Wireguard and Stealth protocol, as the mobile app.
You should include both in the command line interface.
+1 for wireguard support!
We’re definitely aiming at bringing WG to our Linux client, but we need to first mature it. But the “platform” is already there, so it should allow us to easily implement it.
And also the Stealth Protocol…
on arch here wondering the same thing. debtap wont work for me so i guess ill just wait for the inevitable aur package, hopefully a solution comes for opensuse as well
Well, once we release the client we hope the community can build around it for each of the needs. For now our focus is stability and reliability, and we plan to add new features, but in terms of building a distro agnostic client that is not totally in our plans (at the least for now).
If you look at our package structure you can see that the NM backend can be easily switched for non NM, and thus our idea, once we mature this client enough, is to implement native protocols that do not depend on NM. Thus allowing users to run native connections. But in terms of packaging we’ll probably stay the same, as this allow for an effortless way of distributing packages. But again, it’s a double edged-sword, the more we try to support. the more it will be harder for us to ensure that things work robustly on all systems. That’s why once we release the once, we expect for the community to make any changes necessary to adapt for their own needs.
Hey u/Someday_somewere, if that is what you have installed then it is not the latest version.
Same thing happened for me but on Ubuntu. Simply upgrading did not solve this. I completely deleted and purged proton stable version and then did the full install for beta. It is now working correctly
You’re still in time to switch! 
Yeah our goal with this client was mainly to improve the issues from the previous one, which the three main ones were: no settings window (and little feature), slow responsiveness and memory leaks.
Hi! If you run$ python3 -m proton.sso list , are you still seeing your credentials? If yes, can you try to log out, delete $ python3 -m proton.sso logout <your username>and log back in?
We currently only support Debian, Ubuntu and Fedora. But from what I’ve understood there is someone who compiled the either fedora or debian packages and made them installable on arch based systems.