Arch Linux User Repository

PSA: Upstream does not support building natively for ARM64, only cross-compiling. You can use mullvad-vpn-bin instead.

--> ALWAYS DO A CLEAN BUILD <--

This package will verify the signature of the git tag / commit. Developer keys are available here and instructions are here. See the PKGBUILD to determine which developer key you need.

Please do not create upstream issues about the AUR package, they do not support it.

@Hubro Have you tried upgrading node-pre-gyp? You're running version 0.15.0 while the current version is 1.0.0

https://github.com/mapbox/node-pre-gyp

My mullvad client (v. 2021.1) went on a reconnecting loop this morning (wireguard). Took me some time to figure out that apparently the client failed to generate a new wireguard key, after generating one manually in the gui it's working fine again. Maybe this helps someone.

With regards to openvpn: I'm still having problems getting openvpn to run properly. I noticed that for some reason mullvad uses the wg-mullvad (wireguard) adapter to connect via openvpn, is that normal? Also I either get some error "failed to set system DNS" or it connects but I can only reach DNS servers (eg. ping 8.8.8.8 works, but ping www.google.com doesn't) Using firefox I can only connect to websites by setting up the mullvad socks proxy ("10.8.0.1:1080"), otherwise I can't connect.
I manly use wireguard so it's not really urgent, but maybe someone here can make sense of this mess.

Failing to install for me :(

> grpc-tools@1.9.1 install /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
> node-pre-gyp install

node-pre-gyp WARN Using needle for node-pre-gyp https download 
node-pre-gyp ERR! Completion callback never invoked! 
node-pre-gyp ERR! System Linux 5.10.14-arch1-1
node-pre-gyp ERR! command "/usr/bin/node" "/home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/node_modules/.bin/node-pre-gyp" "install"
node-pre-gyp ERR! cwd /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
node-pre-gyp ERR! node -v v10.23.2
node-pre-gyp ERR! node-pre-gyp -v v0.15.0
node-pre-gyp ERR! This is a bug in `node-pre-gyp`.
node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
node-pre-gyp ERR!     <https://github.com/mapbox/node-pre-gyp/issues>
npm ERR! code ELIFECYCLE
npm ERR! errno 6
npm ERR! grpc-tools@1.9.1 install: `node-pre-gyp install`
npm ERR! Exit status 6
npm ERR! 
npm ERR! Failed at the grpc-tools@1.9.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tomas/.cache/yay/mullvad-vpn/src/npm-cache/_logs/2021-02-14T13_23_58_046Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: mullvad-vpn

@whaler I suspect "the unit" refers to the systemd unit. You can check if it's started using "systemctl status mullvad-daemon" in the terminal. And if it's not started you can use "sudo systemctl enable --now mullvad-daemon" to start it and make it start in every boot.

@eaburto @andykluger @yochananmarqos

In continuation to my previous comment. I would be grateful to any one who could clearly state the steps (not just instructions but ACTUAL COMMANDS) so that newbies like me could upgrade to Mullvad & Network-Manager.

Thanks for support & cooperation!

So, I followed the tips from @andykluger and @yochananmarqos. Enabled and started systemd-resolved, installed systemd-resolveconf and linked /etc/resolv.conf to /run/systemd/resolv/stub-resolv.conf. No dice.

I then removed mullvad-vpn and reinstalled with git. Mullvad immediately worked fine, but, again, after a restart it is, assumably, not able to make a valid DNS lookup. It says "the unit" is not connected. What am I missing or doing wrong?

@eaburto Your solution worked instantly, but only for the current session. After a restart, Mullvad VPN complains "the unit" is not connected. Also the "Reconnect" in the Mullvad icon is grayed out. Is there a fix other than switching to systemd-resolved or trying the beta version?

I'm facing problems in three cases

1. with older or latest version of network manager & latest mullvad-vpn. The error throws up -- cannot establish a tunnel (wireguard) and in openvpn the wait is endless.
2. in latest version of everything -- same problem.
3. after systemd-resolved and symlink still nothing works with the latest version. Even the older version of mullvad throws up DNS error while pacman upgrade.

Please update me in this concern. BTW even beta is of no help.

I was going to say I had to switch to the beta cause I was having very weird DNS issues where mullvad did make a connection, I could browse the web through TOR, but everything else was offline. Don't have systemd-resolved installed, beta works indeed.

@eaburto Thank you, this worked for me with the newest version of NetworkManager and Mullvad-VPN-beta. I was hesitant to switch to systemd-resolved. No more downgrading Networkmanager for me! :)