Arch Linux User Repository

Please note that, as of version 4.0, ExpressVPN have switched to a new "universal installer" which replaces their previous distro-specific packages (.deb/.rpm/.pkg) and bypasses package managers entirely (mostly dumping stuff to /opt). I have rewritten the PKGBUILD to repackage what this new installer does so it can still be tracked by pacman, but there's no telling how well this will work going forward (particularly since this new version supposedly has a self-updater built in.)

The new ExpressVPN version is still in beta, so I've not pushed an update to this package yet, if you're interested in testing it out, it's available at https://aur.archlinux.org/packages/expressvpn-beta

Note: you may need to flush your iptables rules after upgrading in order to restore internet access, use iptables -F to do so.

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.

@WorMzy Awesome, thanks!

expressvpn-beta package now available at https://aur.archlinux.org/packages/expressvpn-beta

@wheat32: sure, I can upload the package I shared on codeberg to a new package. The beta is taking longer than I anticipated, so it makes sense.

Would it be possible to create an expressvpn-beta package for the 4.1.1 beta? Would love to try it out but with a package manager. Might be a good way to provide feedback before it is promoted out of beta.

4.0.2 beta update pushed to codeberg: https://codeberg.org/WorMzy/aur-packages/src/branch/main/expressvpn

@WorMzy I am running a pretty standard Manjaro setup and the PKGBUILD you wrote seems to be working out of the box.

4.0.1 beta update pushed to codeberg: https://codeberg.org/WorMzy/aur-packages/src/branch/main/expressvpn

Please do let me know if you get it working, pendo324. I don't allow gtk3 on my systems, so can't test chrom{e,ium} or firefox browser plugins, but if there are some improvements to make to the PKGBUILD to help people who do use these browsers, I'd be happy to include them.

From testing the upcoming 4.0 package:

Seems like the /opt/expressvpn/share/browser_helper_wrapper.sh script doesn't work properly with the native messaging host config:

{
  "name": "com.expressvpn.helper",
  "description": "ExpressVPN Browser Helper",
  "path": "/opt/expressvpn/share/browser_helper_wrapper.sh",
  "type": "stdio",
  "allowed_extensions": [
    "firefox-addon@expressvpn.com",
    "firefox-addon-internal@expressvpn.com",
    "firefox-pwm-alpha@expressvpn.com",
    "firefox-pwm-beta@expressvpn.com",
    "firefox-pwm-release@expressvpn.com"
  ]
}

It prints stderr output from native app com.expressvpn.helper: 2025/02/27 12:28:19 unauthorized access attempt

I couldn't find the source code for the included /opt/expressvpn/bin/browser_helper Go executable, so I haven't been able to fix this yet (may not be possible?)

Please note that, as of version 4.0, ExpressVPN have switched to a new "universal installer" which replaces their previous distro-specific packages (.deb/.rpm/.pkg) and bypasses package managers entirely (mostly dumping stuff to /opt). I have rewritten the PKGBUILD to repackage what this new installer does so it can still be tracked by pacman, but there's no telling how well this will work going forward (particularly since this new version supposedly has a self-updater built in.)

The new ExpressVPN version is still in beta, so I've not pushed an update to this package yet, if you're interested in testing it out, it's available at https://aur.archlinux.org/packages/expressvpn-beta

Note: you may need to flush your iptables rules after upgrading in order to restore internet access, use iptables -F to do so.