Package Details: expressvpn 2.1.0_1-1

Git Clone URL: (read-only)
Package Base: expressvpn
Description: Proprietary VPN client for Linux
Upstream URL:
Licenses: custom
Submitter: 2bluesc
Maintainer: 2bluesc (WorMzy)
Last Packager: WorMzy
Votes: 30
Popularity: 1.587153
First Submitted: 2016-03-26 03:18
Last Updated: 2019-04-09 22:03

Pinned Comments

WorMzy commented on 2019-01-11 11:38

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.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

WorMzy commented on 2019-05-07 17:41

@rgill that would be a great help. If you find a solution that is easy to incorporate into the package, I'll happily include it.

rgill commented on 2019-05-06 08:36

@WorMzy thanks for the package! I started using it recently, however, I can confirm that the auto_connect is not working. If I look at my preferences, it is set to true but after a reboot it doesn't connect although the service is started. I have to manually run expressvpn connect.

For now I've set a autostart script to run every time on boot but I would like to help diagnose the issue in the package if you want.

evernow commented on 2019-04-09 22:31

Thanks for updating so fast!

Hendrikto commented on 2019-04-02 23:47

I case anybody has the same problem as eperez: the correct command to use is

systemctl start expressvpn.service 

WorMzy commented on 2019-01-28 21:28

Yeah, it seems like the autoconnect feature is broken. I recommend contacting expressvpn support to see whether we're missing something. I have a theory that /etc/default/expressvpn should have some option or value set to make autoconnect at boot work, and/or the aforementioned autostart entry for autoconnect on log in, but that's all I have -- theories.

NZCyrus commented on 2019-01-26 20:51

@WorMzy - Firstly, thanks for all your effort with this package :-) I downloaded the Arch package from the expressvpn site and installed it with 'pacman -U' and made sure that autoconnect was enabled. Upon a reboot my chosen VPN location still didn't connect so under my username I included 'Exec=expressvpn connect location' and autoconnect now functions as expected.

evernow commented on 2019-01-26 14:38

@WorMzy Not sure if I installed the package on their website incorrectly, I just downloaded it from their websites, went to pamac and hit install local packages and selected it, but it doesn't work, like the package doesn't even connect. I deleted it from


And installed yours again which does work! But the autoconnect functionality doesn't. Any ideas? If any information is needed, feel free to ask.

WorMzy commented on 2019-01-26 13:24

muncrief, rather than doing that (which will leave you with an expressvpn.install written for v2.0.0 and upwards, you can just grab the previous build files from the git history:

@evernow and NZCyrus, Upon further examination, I don't use the autoconnect feature, so sorry for that misinformation. Years ago I made a script that literally just runs expressvpn connect and added it to my plasma startup. I also have a function in my zshrc that prints out the currently connected status:

conn=$(expressvpn status)
if ! grep -q Connected <<<$conn; then
  echo "Not connected"
  head -1 <<<$conn

I've checked the auto_connect preference, and my guess is enabling it is supposed to create an autostart entry under .config/autostart (linking to /usr/lib/expressvpn/expressvpn-agent.desktop), but the expressvpn-agent binary doesn't seem to do anything when I run it manually, so I'm not entirely sure whether this functionality still exists.

My advice would be to try the official package. If the autoconnect feature still doesn't work, contact ExpressVPN support.

plorenz commented on 2019-01-26 09:37

Thanks for upgrading! Works for me.

evernow commented on 2019-01-25 18:37

@muncrief Not sure if you are referencing to the issue me and @NZCyrus are having, but I was having my issue on 1.5.1 as well.