Looking at Mullvad, from ProtonVPN hell in Linux

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.

Wow. I migrated to Mullvad after experiencing a lot of connection drops and leaks on Proton, and it’s sad to hear that after 3 years, they still have not adressed that.

About Mullvad, it works great. Never experienced leaks, super stable software and no drops. I’ve used it in Linux Mint, Pop OS and Fedora, and they all worked fine with Mullvad, plug’n’play.

I don’t have Proton VPN problems in Debian 12, and the CLI works fine in Ubuntu 23.04.

But I have downgraded unlimited, since Google search doesn’t like Proton VPN, all the domestic servers will pop up “not a robot” captchas.

I have Mullvad running on multiple Linux machines (errm a dozen ?) mostly Arch and Mint.

Zero problems. It just works.

Have very good experiences with Mullvad on Linux. On top of the killswitch they also have the optional lock-down mode that will not allow any traffic unless the VPN is started (don’t know if Proton has that). Additional advantage over Proton: I almost never encounter captchas.
You should give it a try for a month. You can get your 5 Euros back if you are not happy.

debian, mullvad cli only

no issues, and, i always double check the connection & dns

i have a script i run each time i connect for verification of connection/dns, never an issue

Works great, they have repositories for Debian / Ubuntu and Fedora too.

I haven’t tried connecting to my ProtonVPN recently, I had issues in the past with connectivity and switched to Mullvad. Haven’t had any issues with Mullvad since then. Trying to figure out what plan I need to renew my Proton account with this year…I don’t use their VPN on my phone or computer (use Mullvad for both), don’t need their password manager, don’t need their drive, all I use is mail, starting to question that as well.

Run both ProtonVPN and Mullvad on Fedora, Arch, and Ubuntu derivatives, currently using PopOS with KDE.

Using mullvad on arch with kde and on my phone rn, and I am quite happy with it.
Am rarely getting asked for captchas. Ping is good enough for competitive gaming. And how private you can be with your account is just a dream.
Am currently on my first month, but I’m definitely gonna add some more credit to my account for many more months

I just cancelled my test month of Proton because the port forwarding benefit was not as large as I expected and it’s a pain in the arse to switch servers even with the desktop app on Windows. There are sooo many sites blocking VPNs that I switch once or twice per session and I don’t have the time nor patience to trial-by-error on Proton.

Running via gluetun Docker container is the same for either Mullvad or Proton but I just pick a good server in my geography and let it run. Port forwarding with Proton and gluetun is stupid despite the guides they provide.

Right now, Proton is only worth it if port forwarding is mandatory for your use.

I use Fedora on almost all my machines, and Ubuntu on one laptop.
I did use Proton previously and moved to Mullvad. It works fine.
I have installed the Mullvad app + browser and it works finely.

Moving to Mullvad is the best option. I do not regret it.

Mullvad doesn’t have port forwarding if that’s important to you. Be aware

They have a webpage that lets you generate either an OpenVPN or Wireguard config for your account.

Assuming your OS supports one or the other, you should be fine.

Does anyone here run Mullvad on the router?

Not defending Proton because they don’t need to - they are well-known provider with a lot of happy users, but reading your post tells me you need to work on your Linux skills - or switch to some other OS.

If you don’t agree, then I’d suggest you stop the drama, buy a month €5 and take it for a test drive.

Proton VPN also has an auto-connection problem for some apps after the computer wakes from sleep; e.g., WhatApp often loses connection.

Why go through all the trouble to use a VPN, then use Google services?

Don’t you get captchas with Mullvad too, though?

Can I ask you what is your desktop environment in Debian 12 and what is your technique/service to rule out leaks?

Proton only officially supports Debian with GNOME, that’s why I’m asking here, because I don’t use GNOME.

You can disable Proton GUI autostart in settings. At least in version v4.3.

Proton GUI works on all my Linux machines. The problem is that when carrying out the tests, not all machines behave the same. For example, some pass the IPv6 test but not the IPv4 test and vice versa.

Thanks for the info.