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://codeberg.org/WorMzy/aur-packages/src/branch/main/expressvpn

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.

Hi! Getting the following error:

Verifying source file signatures with gpg...

expressvpn_1.4.4_amd64.deb ... FAILED (unknown public key AFF2A1415F6A3A38)

Will do, thanks WorMzy.

Sounds like those packages are red herrings, and the actual problem is something else. Compare the journal from a working boot session, with the journal from a problematic session. If nothing obvious jumps out at you, then I suggest opening a topic in AUR issues on the support forum (assuming you are still running Arch). The comments section of an AUR package isn't an ideal place for extended support discussions.

Please link to the topic here though, in case there are others with the same issue.

I uninstalled cuetools, shntool and mac (I didn't uninstall flac cause the system wouldn't let me, there were some dependency problems), rebooted and everything is fixed.

Now, what might have happened?

EDIT:

Experiment time, for science. I installed the 3 packages again and the problem reappeared. Uninstalled, OK.

Performed a trizen -Scc, installed again and the problem is there again.

I'll now do it again for each package individually to find the culprit.

EDIT 2: Something's really wrong with my system. After installing the packages separately and getting mixed and confusing results, I got to the point when they are all uninstalled but the problem reemerged.

Output of ls -l /proc/$(pgrep expressvpnd)/fd

lr-x------ 1 root root 64 Jul 27 17:07 0 -> /dev/null

lrwx------ 1 root root 64 Jul 27 17:07 1 -> 'socket:[18354]'

lr-x------ 1 root root 64 Jul 27 17:07 10 -> 'pipe:[25261]'

lr-x------ 1 root root 64 Jul 27 17:07 11 -> 'pipe:[26224]'

lr-x------ 1 root root 64 Jul 27 17:07 12 -> 'pipe:[26333]'

lr-x------ 1 root root 64 Jul 27 17:07 13 -> 'pipe:[24510]'

lr-x------ 1 root root 64 Jul 27 17:07 14 -> 'pipe:[27420]'

lr-x------ 1 root root 64 Jul 27 17:07 15 -> 'pipe:[26584]'

lrwx------ 1 root root 64 Jul 27 17:07 16 -> 'socket:[33567]'

lr-x------ 1 root root 64 Jul 27 17:07 17 -> 'pipe:[35323]'

lrwx------ 1 root root 64 Jul 27 17:07 18 -> 'socket:[46644]'

lrwx------ 1 root root 64 Jul 27 17:07 19 -> 'socket:[50770]'

lrwx------ 1 root root 64 Jul 27 17:07 2 -> 'socket:[18354]'

l-wx------ 1 root root 64 Jul 27 17:07 20 -> 'pipe:[35323]'

lrwx------ 1 root root 64 Jul 27 17:07 21 -> 'anon_inode:[eventpoll]'

lr-x------ 1 root root 64 Jul 27 17:07 22 -> 'pipe:[35324]'

l-wx------ 1 root root 64 Jul 27 17:07 23 -> 'pipe:[35324]'

lrwx------ 1 root root 64 Jul 27 17:07 24 -> 'anon_inode:[eventfd]'

lrwx------ 1 root root 64 Jul 27 17:07 25 -> 'socket:[61598]'

lrwx------ 1 root root 64 Jul 27 17:07 26 -> 'socket:[120698]'

lrwx------ 1 root root 64 Jul 27 17:07 27 -> 'socket:[125978]'

lrwx------ 1 root root 64 Jul 27 17:07 28 -> 'socket:[304332]'

lrwx------ 1 root root 64 Jul 27 17:07 29 -> 'socket:[311649]'

lrwx------ 1 root root 64 Jul 27 17:07 3 -> 'socket:[20017]'

lrwx------ 1 root root 64 Jul 27 17:07 30 -> 'socket:[320189]'

lrwx------ 1 root root 64 Jul 27 17:07 4 -> 'anon_inode:[eventpoll]'

lrwx------ 1 root root 64 Jul 27 17:07 5 -> 'socket:[16767]'

lrwx------ 1 root root 64 Jul 27 17:07 6 -> 'socket:[21761]'

lrwx------ 1 root root 64 Jul 27 17:07 8 -> 'socket:[20648]'

lrwx------ 1 root root 64 Jul 27 17:07 9 -> 'socket:[48267]'

[[Time:01:22 Location:~/Desktop]]

$ expressvpn refresh

Refreshing...

Stuck there, not a sign of life.

uname -r and pacman -Q linux are identical.

I did install cuetools, shntool, flac and mac now that I remember just before that occurence. I'll uninstall them to see if it changes anything.

Can you check what those file descriptors are?

# ls -l /proc/$(pgrep expressvpnd)/fd

I'm guessing they're just sockets, but I'm not sure why you have so many of them. (I have 11)

Your cluster list file version is outdated, but I doubt this would cause the issue you are seeing. Try updating it with expressvpn refresh just in case.

Other things to check are that your booted kernel (uname -r) matches the installed version (pacman -Q linux), and whether downgrading to the previous kernel fixes things.

I don't think that any AUR packages would cause problems for expressvpn, but going over your pacman -Qm list and rebuilding any potentially suspect packages just in case may help.

Up until this afternoon, the output of

journalctl -u expressvpn.service

has been something like

...

-- Reboot --

Jul 27 17:03:12 teo-arch systemd[1]: Started ExpressVPN Daemon.

Jul 27 17:03:14 teo-arch expressvpnd[397]: # Generated by expressvpn

Jul 27 17:03:14 teo-arch expressvpnd[397]: unlocking fd: 3

Jul 27 17:03:15 teo-arch expressvpnd[397]: 2018/07/27 17:03:15 rpc.Register:

method "Authenticate" has 2 input parameters; needs exactly three

Jul 27 17:03:15 teo-arch expressvpnd[397]: 2018/07/27 17:03:15 rpc.Register: method "SetAuth" has 2 input parameters; needs exactly three

Jul 27 17:03:15 teo-arch expressvpnd[397]: unlocking fd: 3

Jul 27 17:04:59 teo-arch systemd[1]: Stopping ExpressVPN Daemon...

Jul 27 17:04:59 teo-arch systemd[1]: expressvpn.service: Main process exited, code=exited, status=1/FAILURE

Jul 27 17:04:59 teo-arch systemd[1]: expressvpn.service: Failed with result 'exit-code'.

Jul 27 17:04:59 teo-arch systemd[1]: Stopped ExpressVPN Daemon.

-- Reboot --

Jul 27 17:05:36 teo-arch systemd[1]: Started ExpressVPN Daemon.

Jul 27 17:05:38 teo-arch expressvpnd[394]: unlocking fd: 3

Jul 27 17:05:38 teo-arch expressvpnd[394]: 2018/07/27 17:05:38 rpc.Register: method "Authenticate" has 2 input parameters; needs exactly three

Jul 27 17:05:38 teo-arch expressvpnd[394]: 2018/07/27 17:05:38 rpc.Register: method "SetAuth" has 2 input parameters; needs exactly three

Jul 27 17:05:39 teo-arch expressvpnd[394]: unlocking fd: 3

Jul 27 17:07:16 teo-arch systemd[1]: Stopping ExpressVPN Daemon...

Jul 27 17:07:17 teo-arch systemd[1]: expressvpn.service: Main process exited, code=exited, status=1/FAILURE

Jul 27 17:07:17 teo-arch systemd[1]: expressvpn.service: Failed with result 'exit-code'.

Jul 27 17:07:17 teo-arch systemd[1]: Stopped ExpressVPN Daemon.

-- Reboot --

...

After the update, I get

-- Reboot --

Jul 27 17:07:51 teo-arch systemd[1]: Started ExpressVPN Daemon.

Jul 27 17:07:52 teo-arch expressvpnd[397]: unlocking fd: 3

Jul 27 17:07:52 teo-arch expressvpnd[397]: 2018/07/27 17:07:52 rpc.Register: method "Authenticate" has 2 input parameters; needs exactly three

Jul 27 17:07:52 teo-arch expressvpnd[397]: 2018/07/27 17:07:52 rpc.Register: method "SetAuth" has 2 input parameters; needs exactly three

Jul 27 17:07:53 teo-arch expressvpnd[397]: unlocking fd: 6

Jul 27 17:09:03 teo-arch expressvpnd[397]: unlocking fd: 9

Jul 27 17:14:49 teo-arch expressvpnd[397]: unlocking fd: 9

Jul 27 17:16:04 teo-arch expressvpnd[397]: unlocking fd: 19

Jul 27 17:17:04 teo-arch expressvpnd[397]: unlocking fd: 19

Jul 27 17:27:06 teo-arch expressvpnd[397]: unlocking fd: 25

Jul 27 19:14:00 teo-arch expressvpnd[397]: unlocking fd: 26

Jul 27 19:22:13 teo-arch expressvpnd[397]: unlocking fd: 27

Jul 27 19:25:30 teo-arch expressvpnd[397]: unlocking fd: 28

Jul 27 23:29:01 teo-arch expressvpnd[397]: unlocking fd: 29

Jul 27 23:34:31 teo-arch expressvpnd[397]: unlocking fd: 30

The output of expressvpn diagnostics gives me

ExpressVPN client version : 1.4.4

ExpressVPN client build : 1.4.4 (3658)

Operating system version : Arch Linux

Timestamp: 2018-07-27 23:38:03.997169161 +0300 EEST m=+23411.928747636

Cluster list file version: 20180707|1|

Cluster list download date: 2018-07-08 00:47:58.014431156 +0300 EEST

Smart location download date: 2018-07-27 23:37:55.219059276 +0300 EEST m=+23403.150637771

Protocol pecking order download date: 2018-07-27 17:16:13.733962674 +0300 EEST m=+501.665541126

Cannot reproduce here. Check what messages expressvpn.service has logged to the journal, perhaps you will find a hint there. Failing that, check the output of expressvpn diagnostics.

Performed a trizen -Syu today on my system, it was a kernel update. After a reboot, expressvpn gets stuck at

[[Time:19:21 Location:~/Desktop]]

$ expressvpn connect smart

Connecting to Smart Location...

Connecting to UK - East London...

and never connects, even after half an hour or so. I tried connecting to other places but to no avail. New kernel: 4.17.10-1

@JohnnyDeacon: https://wiki.archlinux.org/index.php/Makepkg#Signature_checking