| 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: | 139 |
| Popularity: | 3.50 |
| First Submitted: | 2018-10-24 17:33 (UTC) |
| Last Updated: | 2024-12-13 02:39 (UTC) |
I'm facing problems in three cases
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! :)
For the people not wanting to change to systemd-resolved I just found another approach. You can still use openresolv with no problem adding this line to /etc/resolvconf.conf:
dynamic_order="tap[0-9]* tun[0-9]* vpn vpn[0-9]* wg-mullvad wg[0-9]* ppp[0-9]* ippp[0-9]*"
It's just the default value with the mullvad wireguard interface name added so it consider it a higher priority when adding the DNS servers to /etc/resolv.conf
@andykluger did it like you described it and it works now, thanks ^^
@null_matter ya your probably right ;D actually it's sad because i think many comment here but don't reach the Mullvad People :)
cedricbambooza, I'm also just an arch user that has paid for the VPN and is upset it doesn't work sometimes :D
You can see the package maintainer above, but they are just another arch user as well as far as I know. You would want to contact Mullvad directly to give them feedback, I doubt any employee would read this package page. cheers
So is anyone working on getting this issue fixed?
only because I'm getting to see a pattern in this failures happing, first with the DNS not working with OpenVPN due to some network related changes from a kernel update i guess, that got fixed... and now again DNS issues with the whole thing not working at all also because of some update, this time probably networkmanager. what is going on?
not to be mean or something, but I've paid good money for a year of VPN Usage, but that doesn't help when it's broken most of the time...
and telling people to use the beta version can't be the fix either. why call it beta then if it is always the go to solution when the main release is broken?
when you need people to test your beta, just say so :) but don't force us to use it just by not fixing the main release, please.
for some reason i can't get electron to download during build of the beta package, it takes ages and stops before finishing. So even if tried i can't run beta at the moment...
I have not had any issues since the last release, using systemd-resolved.
That is, I have:
For more info: https://wiki.archlinux.org/index.php/Systemd-resolved
Sadly no. I already tried reinstalling openresolv. It's curious how the proven solutions for this problem don't seem to work for me. I tried the different beta-packages (2020.8-beta2 still is the package I am using now) and openresolv was and is installed. Only downgrading NetworkManager seems to work for me. It's a minor annoyance for now, but I still wonder what's going on here.
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-bininstead.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.