Package Details: mullvad-vpn 2024.7-1

Git Clone URL: https://aur.archlinux.org/mullvad-vpn.git (read-only, click to copy)
Package Base: mullvad-vpn
Description: The Mullvad VPN client app for desktop
Upstream URL: https://www.mullvad.net
Licenses: GPL-3.0-or-later
Submitter: gin078
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 137
Popularity: 2.73
First Submitted: 2018-10-24 17:33 (UTC)
Last Updated: 2024-10-30 16:32 (UTC)

Pinned Comments

yochananmarqos commented on 2022-11-11 19:31 (UTC) (edited on 2022-11-13 19:21 (UTC) by yochananmarqos)

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

yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2024-06-06 22:09 (UTC) by yochananmarqos)

--> 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.

Latest Comments

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 45 Next › Last »

<deleted-account> commented on 2021-04-04 22:49 (UTC)

@yochananmarqos Just want to add I also use iwd and 2021.2-1 is able to create a wireguard interface just fine without networkmanager. I do have libnm installed however, perhaps that is all that is needed? (It also seems to work fine for me without resolvconf, but maybe I don't understand the issue below)

yochananmarqos commented on 2021-04-04 22:03 (UTC) (edited on 2021-04-04 22:09 (UTC) by yochananmarqos)

@quantized: I added networkmanger with 2021.2-2, you must still have 2021.2-1 installed. However, you just helped me realize all that's required is resolvconf for DNS management. 2021.2-3 is updated to reflect that.

EDIT: Do you use OpenVPN or Wireguard? It turns out networkmanager is required for created a Wireguard interface (wg-mullvad).

quantized commented on 2021-04-04 21:32 (UTC) (edited on 2021-04-04 21:32 (UTC) by quantized)

Hi,

Is networkmanager a new dependency? I currently have the same 2021.2 version, but it's not dependent on networkmanager. Curious, because I use iwd instead of networkmanager, and mullvad-vpn worked just fine with it...

yochananmarqos commented on 2021-04-03 16:33 (UTC)

@AverytheFurry: Done.

@Cant.Install: Read the pinned comment.

@Hubro: Can't reproduce it.

Hubro commented on 2021-04-03 04:09 (UTC)

I am baffled, I have no clue why my install is failing. I have been unable to update this package for months now. I get this error every time:

Installing JavaScript dependencies...
npm WARN EBADENGINE Unsupported engine { package: 'mullvad-vpn@2021.2.0',
npm WARN EBADENGINE   required: { node: '>=12', npm: '>=6.12' },
npm WARN EBADENGINE   current: { node: 'v10.24.0', npm: '7.8.0' } }
npm ERR! code 6
npm ERR! path /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp@0.15.0
npm ERR! node-pre-gyp info using node@10.24.0 | linux | x64
npm ERR! node-pre-gyp WARN Using needle for node-pre-gyp https download 
npm ERR! node-pre-gyp info check checked for "/home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/bin/grpc_tools.node" (not found)
npm ERR! node-pre-gyp http GET https://node-precompiled-binaries.grpc.io/grpc-tools/v1.9.1/linux-x64.tar.gz
npm ERR! node-pre-gyp http 301 https://node-precompiled-binaries.grpc.io/grpc-tools/v1.9.1/linux-x64.tar.gz
npm ERR! node-pre-gyp ERR! Completion callback never invoked! 
npm ERR! node-pre-gyp ERR! System Linux 5.11.11-arch1-1
npm ERR! 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"
npm ERR! node-pre-gyp ERR! cwd /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! node-pre-gyp ERR! node -v v10.24.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.15.0
npm ERR! node-pre-gyp ERR! This is a bug in `node-pre-gyp`.
npm ERR! node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
npm ERR! node-pre-gyp ERR!     <https://github.com/mapbox/node-pre-gyp/issues>

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-04-03T04_06_32_624Z-debug.log

I am deleting the source directory before installation:

rm -rf .cache/yay/mullvad-vpn

And I'm choosing to "cleanBuild" the package in yay when installing. I don't see anybody else in the comments with the same problem. Any ideas?

Cant.Install commented on 2021-04-02 23:42 (UTC)

Help? This thing can't install even if I use do 'git clone' and 'makepkg -si' thing. I'm a total beginner with this OS, I really hope I don't offend anyone because I don't know what to do or what's going on, but it's been over a month since I've popped this in a virtual machine and barely anything works.

:: Resolving dependencies... :: There are 4 providers available for mullvad-vpn: :: Repository AUR: 1) mullvad-vpn 2) mullvad-vpn-beta 3) mullvad-vpn-beta-bin 4) mullvad-vpn-bin Enter a number (default=1): 1 :: Calculating conflicts... :: Calculating inner conflicts...

Aur (1) mullvad-vpn-2021.2-1

:: Proceed to review? [Y/n]: y

:: Downloading PKGBUILDs... PKGBUILDs up to date nothing new to review :: keys need to be imported: 8339C7D2942EB854E3F27CE5AEE9DECFD582E984 wanted by: mullvad-vpn-2021.2-1 EA0A77BF9E115615FC3BD8BC7653B940E494FE87 wanted by: mullvad-vpn-2021.2-1 :: import? [Y/n]: y gpg: keyserver receive failed: Server indicated a failure fetching devel info... ==> Making package: mullvad-vpn 2021.2-1 (Fri 02 Apr 2021 07:38:03 PM EDT) ==> Retrieving sources... -> Updating mullvadvpn-app git repo... Fetching origin -> Updating mullvadvpn-app-binaries git repo... Fetching origin -> Found mullvad-vpn.sh ==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped mullvad-vpn.sh ... Passed ==> Verifying source file signatures with gpg... mullvadvpn-app git repo ... FAILED (unknown public key 78CEAA8CB72E4467) mullvadvpn-app-binaries git repo ... FAILED (unknown public key AEE9DECFD582E984) ==> ERROR: One or more PGP signatures could not be verified! :: Packages failed to build: mullvad-vpn-2021.2-1

<deleted-account> commented on 2021-04-02 23:16 (UTC)

the issue was uninstalling gnome uninstalled networkmanager, probably should be a dependency.

<deleted-account> commented on 2021-04-02 23:09 (UTC)

After uninstalling gnome, I am getting "failed to set system DNS" - maybe there's a dependency not listed?

yochananmarqos commented on 2021-03-18 16:20 (UTC)

@rbarrett: I may need to add networkmanager as a dependency. See if using it resolves your issues.

rabarrett commented on 2021-03-18 16:10 (UTC) (edited on 2021-03-18 17:21 (UTC) by rabarrett)

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?

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 45 Next › Last »