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.

@aleksozolins: It's not a problem I've experienced, but my suggestion would be to check the state of whichever filesystem (and underlying hardware) your /var/lib resides on. It sounds like the contents of /var/lib/expressvpn/ is either getting corrupted or removed between boots.

Every time I restart my system I am forced to re-activate. Wondering if I'm missing something obvious here. Any advice appreciated!

I have issues with connecting:

> expressvpn connect
A new version is available, download it from https://www.vlycgtx.com/latest#linux.

Connecting to Smart Location...
Connecting to Sweden... 1.0% Still trying to connect. This might take a minute..

@Palanthis no issues here, system up-to-date as of Friday, service starting at boot as usual.

Anyone else having the (new) issue where the expressvpn.service won't start on boot? I have enabled it several times. I don't see any errors in my logs. Once the system is booted, systemctl start expressvpn.service does successfully start the service (after 60 seconds) and then the VPN can connect. I tested this same version in Debian and Arch VMs. It is alive on boot in Debian, but not Arch. Not sure if it's due to a newer kernel version or systemd or something. Kernel 5.17.1.arch1-1, SystemD 250.4-2

I can't seem to get expressvpn to work anymore. It just cycles from 0.0% and up to high 80s then eventually says unable to connect... Resolved itself after installing a new arch setup, not sure what went wrong with Garuda Linux install....

@jmonger: I don't use Firefox or Chrome, so I can't test this, but I believe you just need to run mkdir -p "${HOME}/.mozilla/native-messaging-hosts"; cp "/usr/lib/expressvpn/firefox/com.expressvpn.helper.json" "${HOME}/.mozilla/native-messaging-hosts/com.expressvpn.helper.json" (I believe that expressvpn install-firefox-extension used to do this on your behalf, but these days it just seems to open a firefox addons page). You may also need to start the agent daemon expressvpn-agent --daemon.

Any tips to get this package working with the Firefox extension? When I click on the extension the message displayed is "App Not Found."

Works great from the terminal, but I would like to use the extension as well.

I don't know if I've set my systemd-resolvd up differently, but the default DNS changes that expressvpn so boldly makes on my system don't work. What's more there's no way to change force_vpn_dns to false, either with the CLI or manually in /.config/expressvpn/config.

The only solution I could find for now is to manually add expressvpn's private network DNS IP address (look in /etc/resolv.conf when connected) to /etc/systemd/resolved.conf.d/dns_server.conf