I also use NordVPN, and it was easy to get going on Tumbleweed, with just a few things to fix after install (such as analytics). Just curious: why the “dare I say this”? Is there something I should know about Nord?
It doesn’t work in the countries were government is spaying on the communication ex. middle east.
If you travel a lot, I can recommend surfshark or ExpressVPN. ExpressVPN works with openvpn available in OpenSuse repo. Surfshark I’ve only used on the phone. Didn’t try to set this up on my computer. As per their webpage, you can install it from snap (didn’t try).
1 Like
Ah, so it’s blocked in certain places. I’m already getting Nord bundled with my email service, but I’ll take a look at Express. Thanks for info 
i have been using nordVPN for 4 years now as daily and i started as bundled, but then moved away to only VPN since i took better password manager (1password) and then i use proton mail plus that gives VPN for 1 devices.
my advice is not to use bundle especially password managers and drives etc on one provider split those for better managment.
nordVPN is really solid choise and it works all places that hasent been blocked by country rules. ProtonVPN is decent on my experience tho i get more blocked IP addresses on protonVPN servers due suspected activities etc than nordVPN
nordVPN is fully no policy and dont give anything to any country even on court orders since they are based on country that dosent support those. ProtonVPN is swiz based and still need to give what they can if court orders are issued
1 Like
Yeah, the apparent no share policy is why I accepted the offer. So far Nord has worked very well for me [on Tumbleweed], with the small exception of having to disable “analytics” manually before use (should be off by default, imo). I keep my services and accounts separate by choice, so the “bundle” is more of a referral than a traditional bundle of services. But it was a good deal, and I was in the market for a solid VPN service anyway. (And it works out of the box with minimal effort on Tumbleweed, a definite plus.)
i am on Kalpa and it works i am now on latest 3.19.1 version of nordVPN and maxed out settings almost meshnet is not working when using Post-Quantum VPN for now you need to choose what you use and disable/enable if need something and for me i dont use meshnet feature so no loss there
phatle@kalpa:~> nordvpn settings
Technology: NORDLYNX
Firewall: enabled
Firewall Mark: 0xe1f1
Routing: enabled
Analytics: enabled
Kill Switch: enabled
Threat Protection Lite: enabled
Notify: enabled
Tray: enabled
Auto-connect: enabled
IPv6: enabled
Meshnet: disabled
DNS: disabled
LAN Discovery: disabled
Virtual Location: enabled
Post-quantum VPN: enabled
1 Like
Since we are all telling which VPN we use without issue, I have been using Proton VPN for about 2 years, 8 or 9 months on openSUSE. Zero problems and the gui works too.
3 Likes
Thx for that one, Capistro . Will look into it 
I’ve used Mullvad on Tumbleweed (Gnome) for the past year and it has worked fine. I just installed the RPM downloaded from the Mullvad site. I did have to make a couple small tweaks with RPMRebuild to ensure it pulled the proper dependencies, but the GUI works like it should.
I use the Nordvpn and it works very well on TW. It is mostly cli, but very good
Hey there,
Just a quick question, what client are you using for ProtonVPN?
The RPM from the website for Fedora or the “old ones” from offical openSUSe Repo?
Thanks
proton-vpn from the opensuse repo, it just got updated recently. The last time I checked, there were two versions. One was the deprecated version called protonvpn-gui, and the other was the newer version using the gtk app called proton-vpn-gtk-app by proton but listed as proton-vpn in opensuse repo.
1 Like
Works like a charm. Thanks.
I really used the wrong client.
Just for information, I use purevpn in tumbleweed with no discernible problems. It is run from web extension in vivaldi.
adguardvpn-cli works nicely. They have an install script
I had an irrational fear that by mentioning Nordvpn I’d be in violation of forum rules
nothing sus just been a while since I’ve replied to anything in these forums.
1 Like
Another Proton VPN user here. I generally connect using the browser extension, which works for me in Firefox, Google Chrome and Microsoft Edge. I do have to gui installed as well, just for completeness, currently as the flatpack package since version 4.3.2 from the repos grew some issues - https://bugzilla.suse.com/show_bug.cgi?id=1232851 - though I see now that it has been updated to 4.7.4 and will install.
Hi,
Would you be so kind to share the steps you took to get this working. I’m currently using nuklly build from osb. Latest version (mullvadvpn-2025.2-3.1.x86_64.rpm) causes service to not start. Reinstall with necessary steps doesn’t solve it.
The Fedora RPM I download from Mullvad works fine on openSUSE. You just have to rename a couple of the dependencies. This is done using rpmrebuild.
First, test the RPM to find out if it will fail. If it fails, it will tell you which dependencies failed. Make sure “MullvadFilename” matches whatever your downloaded file is called.
sudo rpm -ivh --test MullvadFilename.rpm
Output will be something like:
error: Failed dependencies:
libnotify is needed by MullvadFilename
Use rpmrebuild to rename the dependency.
rpmrebuild -enp MullvadFilename.rpm
Find the lines with the dependencies called out in the first step. In this case, we need to change “libnotify” to “libnotify4”. Once you’re finished renaming, hit ESC key to end. Type :x and hit ENTER. Press Y to continue. The output will then show the directory where the new RPM was saved.
Navigate to that folder and test dependencies again using the same command from the first step. Output should say “verifying” and “preparing” both 100%. Now you can install using the new RPM.
Thank you for the quick response. I’ve managed to follow your steps successfully, however after trying multiple versions from mullvad’s github I ruled out that this is a mullvad problem. It started after a recent major update on my tumbleweed system. Still not possible to start the mullvad service (or deamon) on boot. This is a first time in years.
Writing the configuration failed:
Could not set 'mullvad-daemon' to be started on boot.
Could not start 'mullvad-daemon' which is currently not running.
Would you like to continue editing?
1 Like