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.

I've been having ongoing--yet intermittent--problems with mullvad-vpn working. I suspect they're similar to what others are describing here, but I'm hoping my additional input will help pinpoint what seems to be affecting so many people.

When I try to use the app to establish a vpn connection, it responds "Blocked Connection" (and my awesome wm icon shows a green lock with a red circle in the middle). This happens even if I use wireguard only, instead of automatic or openvpn (under the app's advanced settings).

Also note that I have already tried the suggestions others have posted here: -I always do a clean build -I've tried the beta--no difference -I've enabled and started systemd-resolved, installed systemd-resolveconf and linked /etc/resolv.conf to /run/systemd/resolv/stub-resolv.conf -none of these seem to help (though when I first set up systemd-resolved, after a reboot it worked for a while)

However, it happens only intermittently. Sometimes after having problems (and just running without the vpn for a while), I'll reboot and it will work. It will keep working for day or even a week or so (with some reboots) and then later it stops working again.

I believe each time it has stopped working, it is after I run a pacman update (and AUR update with yay) and the kernel has been updated. The update has to run hooks for my wireless kernel: the broadcom-wl-dkms module, which has long-standing issues that were eventually solved with the new hook system. So the first idea to consider is that the problem is related to

1) broadcom-wl-dkms and hooks

Another possibility that might help isolate the issue is that I'm not using network manager. I'm using

2) netctl

Note: Just today I tried using NetworkManager instead. It appears to work; but given the intermittent nature of the problem, I'm not sure yet.

Is there any journal info or other data I could collect to help troubleshoot it?

@madhogs: No, unfortunately not. Only files installed during package installation can be tracked.

Is there a way of making this package track the folder /etc/mullvad-vpn/ ? For some reason pacman does not track this folder and thinks it does not belong to any package, even though mullvad-vpn creates this itself.

Changed back from beta to this doing a clean build. I was having the ""failed to set system DNS" error when trying to connect using openvpn. Both beta and 2021.2 are perfectly usable but only using wireguard.

Does not build for me:

Copying binaries
Updating relay list...
    Finished release [optimized] target(s) in 0.10s
     Running `target/release/relay_list`
Request timed out
==> ERROR: A failure occurred in build().
    Aborting...

i can't make it work with the problem of DNS not found and i try to compile it , one time on two i have have this :

  Compiling mullvad-rpc v0.1.0 (/home/david/repos/mullvad-vpn/src/mullvadvpn-app/mullvad-rpc) error[E0277]: 

the trait bound `std::net::SocketAddr: std::cmp::Ord` is not satisfied    --> mullvad-rpc/src/address_cache.rs:170:23
    |
170 |             addresses.sort();
    |                       ^^^^ the trait `std::cmp::Ord` is not implemented for `std::net::SocketAddr`

error[E0277]: the trait bound `std::net::SocketAddr: std::cmp::Ord` is not satisfied
   --> mullvad-rpc/src/address_cache.rs:173:28
    |
173 |             current_sorted.sort();
    |                            ^^^^ the trait `std::cmp::Ord` is not implemented for `std::net::SocketAddr`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0277`.
error: could not compile `mullvad-rpc`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERREUR : Une erreur s’est produite dans build().
    Abandon…

@eaburto Thanks, I know. I just installed mullvad-vpn-cli 2020.7 and it is working - even after restarts! :)

systemd says:

$ systemctl -all | grep mullvad

sys-devices-virtual-net-wg\x2dmullvad.device loaded active plugged /sys/devices/virtual/net/wg-mullvad
sys-subsystem-net-devices-wg\x2dmullvad.device loaded active plugged /sys/subsystem/net/devices/wg-mullvad
mullvad-daemon.service loaded active running Mullvad VPN daemon

So, again, I wonder why mullvad-vpn 2021.1-1, the GUI version, refuses to find a/the DNS address.

I am beginning to think there is something wrong in Arch, or my setup. I am using KDE, FWIW.

@yochananmarqos I do a clean install every time

@Hubro: Do a clean install like the pinned comment says.

@FIN4LSHAR3: It's not related to system package versions, it's an internal node module. See the error again:

/src/mullvadvpn-app/gui/node_modules/grpc-tools/node_modules/.bin/node-pre-gyp