Hello, I am a ProtonVPN user, I really like the unlimited plan, with aliases, drive, etc. The problem is that my use of the VPN is 90% in Linux. I have given it many opportunities and I have been very patient. But I can not anymore.
Both applications (CLI, GUI) are a disaster. Memory leaks, hundreds of incomprehensible python scripts, absurd dependencies on widgetsets, keyrings, wallets, gnom(öö)s.
But there is still something but and alarming: Even though ProtonMail is the owner of ip.me, it does not self-check the connection, so even if you get a message “everything is correct, you are correctly connected to x server”, you must do manual checks , because many times you are actually browsing with your original IP.
I have 5 Linux machines, only one Arch machine and another Debian after a hell of a hit-and-miss, they work apparently fine. The surprising thing is that the other 3 Debian machines, with exactly the same fresh configuration as the operational Debian machine, although they “connect successfully”, browse with the original IP leaked.
The most amazing case I have experienced was a Debian machine that apparently connected correctly, then I realized that the http/https requests sent through chromium were correctly masked, but the requests made from Lynx/Dillo used the original leaked IP.
Note: I always use non-desktop-environment but usually i3wm. Maybe this is the reason of my hell ?
For this reason I ask the community what the current status of Mullvad in Linux is like. Thank you.