Arch Linux User Repository

Info from expressvpn's site ...

wget https://www.expressvpn.com/expressvpn_release_public_key_0xAFF2A1415F6A3A38.asc

gpg --import expressvpn_release_public_key_0xAFF2A1415F6A3A38.asc

All installed fine; thank you very much for maintaining.

Looks like update notifications are working for the linux client now, but unfortunately the current version (2.3.2) thinks it's an older version (2.3.1 -- check expressvpn --version), so the update alert people get when they run expressvpn status may be a false positive.

Please check what version is reported at https://www.expressvpn.com/latest (or https://www.expressvpn.com/support/troubleshooting/china-status/#linux as this sometimes gets updates listed sooner) before flagging the package as out-of-date.

Please note that, from v2.0.0, ExpressVPN will be providing signed Arch packages on their website (alongside the deb and rpm packages). I'll be continuing to update this package, but for those that find using the AUR cumbersome or just don't want to wait, please be aware of this option.

EDIT: packages were delayed for testing, but seem to be live as of 2019-01-23.

So, is this supposed to work on Manjaro as well? I have a fresh install and after activating the vpn, the connection is fine until it randomly drops, despite showing still connected. I have to disconnect and reconnect about once every 10 minutes.

Some older comments reference different solutions for this, but I thought I'd go ahead and say that if you have NetworkManager and experience occasional DNS errors that require you to reconnect expressvpn manually, I needed to prevent NetworkManager from editing /etc/resolv.conf, which seemed to occur whenever I had any connection hiccups. I didn't realize that expressvpn and NetworkManager were fighting over owning this file.

I used the solution from https://askubuntu.com/questions/623940/network-manager-how-to-stop-nm-updating-etc-resolv-conf by adding this to /etc/NetworkManager/NetworkManager.conf:

[main]
dns=none
rc-manager=unmanaged

@marakasmalan: No. At a guess your /var/lib/expressvpn/userdata2.dat is getting corrupted at shutdown. Is it possible your filesystem is damaged and/or the underlying hardware is degraded?

every time the system reboots I have to reactivate expressvpn, is that normal?

Pinned instructions do not work for me. Still fails complaining about PGP signatures ` [root@arch ~]# gpg --import expressvpn_release_public_key_0xAFF2A1415F6A3A38.asc gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key AFF2A1415F6A3A38: public key "ExpressVPN Release release@expressvpn.com" imported gpg: Total number processed: 1 gpg: imported: 1 [root@arch ~]# yay -S expressvpn -> Avoid running yay as root/sudo. AUR Explicit (1): expressvpn-3.57.1.2_1-1 :: PKGBUILD up to date, skipping download: expressvpn 1 expressvpn (Build Files Exist) ==> Packages to cleanBuild? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> 1 expressvpn (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> ==> Making package: expressvpn 3.57.1.2_1-1 (Mon Nov 6 12:37:32 2023) ==> Retrieving sources... -> Found expressvpn_3.57.1.2-1_amd64.deb -> Found expressvpn_3.57.1.2-1_amd64.deb.asc ==> WARNING: Skipping verification of source file PGP signatures. ==> Validating source_x86_64 files with sha512sums... expressvpn_3.57.1.2-1_amd64.deb ... Passed expressvpn_3.57.1.2-1_amd64.deb.asc ... Skipped :: (1/1) Parsing SRCINFO: expressvpn gpg: directory '/tmp/.gnupg' created gpg: keybox '/tmp/.gnupg/pubring.kbx' created gpg: /tmp/.gnupg/trustdb.gpg: trustdb created gpg: error reading key: No public key

:: PGP keys need importing: -> 1D0B09AD6C93FEE93FDDBD9DAFF2A1415F6A3A38, required by: expressvpn :: Import? [Y/n] :: Importing keys with gpg... gpg: directory '/tmp/.gnupg' created gpg: keybox '/tmp/.gnupg/pubring.kbx' created gpg: /tmp/.gnupg/trustdb.gpg: trustdb created gpg: key AFF2A1415F6A3A38: public key "ExpressVPN Release release@expressvpn.com" imported gpg: Total number processed: 1 gpg: imported: 1 ==> Making package: expressvpn 3.57.1.2_1-1 (Mon Nov 6 12:37:44 2023) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found expressvpn_3.57.1.2-1_amd64.deb -> Found expressvpn_3.57.1.2-1_amd64.deb.asc ==> Validating source_x86_64 files with sha512sums... expressvpn_3.57.1.2-1_amd64.deb ... Passed expressvpn_3.57.1.2-1_amd64.deb.asc ... Skipped ==> Verifying source file signatures with gpg... expressvpn_3.57.1.2-1_amd64.deb ... FAILED (unknown public key AFF2A1415F6A3A38) ==> ERROR: One or more PGP signatures could not be verified! -> error making: expressvpn-exit status 1 -> Failed to install the following packages. Manual intervention is required: expressvpn - exit status 1 [root@arch ~]# `

I've noticed "Failed unmounting Temporary Directory /tmp" when expressvpn service is enabled. On a boot with it disabled, the error doesn't appear. Besides that, everything seems to work fine.

@JedPhillips: When you click the download link on their website, it directs you to the .works URL, so my guess is it's their CDN. In any case, the downloads are verified with ExpressVPN's release signing key, so unless makepkg fails to validate the files, you can either assume they're genuine, or that ExpressVPN has leaked the private key, someone has made their own spoof packages, AND hijacked the .com website to make the download link point to a site hosting the spoof packages, AND they've been keeping up this charade since September 2021 (which is when the .works URL replaced the old .xyz URL) without anyone noticing on ExpressVPN's side. I'm not saying the latter is impossible, but it's incredibly unlikely. ;)

If you are genuinely worried about the downloads, please contact ExpressVPN support for clarification on why the downloads are served from the .works URL. All we can provide here is speculation.

Why is this pulling from expressvpn.works rather than expressvpn.com? I can't find any information on expressvpn.works and whether it's legit.

If you're having problems and need to update to the latest version, navigate to:

http://www.expressvpn.com/latest#linux

and upgrade the package with sudo pacman -U <downloaded tarball>

Also flagged this out of date for now, as this package is 2 minor versions behind.

You can use the official package if you prefer (see the sticky comment from 2019), however, it's just a repackaging of the same content in the deb/rpm packages using fpm with some packaging issues (creates untracked files, tries to modify files in $HOME, enables systemd services). Also the official Arch package only comes in x86_64 flavour.