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.

Thanks for upgrading! Works for me.

@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.

Unfortunately version 2.0.0 breaks network bridging, so if you have one you'll have to downgrade back to 1.5.1. Note that this is not a packaging issue, but a bug in the binary itself. So here are some quick instructions on how to modify this package to create and install version 1.5.1:

cd

yay -G expressvpn

cd ~/expressvpn

mousepad .SRCINFO PKGBUILD &

Change all instances of both 2.0.0_1 and 2.0.0-1 to 1.5.1 in both files

Change all sha512sums_x values to SKIP in both files

makepkg --syncdeps

sudo pacman -U *.tar.xz

Now have pacman ignore the AUR expressvpn package so it won't nag you to upgrade:

sudo mousepad /etc/pacman.conf &

Add "IgnorePkg = expressvpn"

Can confirm what @evernow has stated. Even though I have an 'expessvpn autoconnect enabled' status, it does not autoconnect. Also tried to connect with the chrome extension but the button is inactive. I have to 'expressvpn connect location' each startup to activate VPN.

@WorMzy Thank you for updating the package! I updated and activated it. And I made sure to run "expressvpn autoconnect true". I restarted, and like always when I check with the command line with "expressvpn status" it says the service has not started, so I have to run "systemctl start expressvpn.service" to start it up. Then I check again and it still doesn't connect automatically so I have to run the connect command, here is what I get when I type "expressvpn diagnostics"

Client Version: 2.0.0 Client Shared Version: v1.3.1-6-g283984e OS Name: linux OS Version: Manjaro Linux Internal diagnostics data: D01: 459, OK D02: 457, OK D03: 443 D04: 443, OK D05: 443, OK D06: 443 D07: 443, OK D08: 443, OK D09: 443, OK D10: 443, OK D11: 443, OK D12: N, N D13: https://www.crezm4l.net D14: USA - Miami D15: auto

If any additional information is needed, please ask, and I greatly appreciate your work!

@evernow: Package works for me. Post your diagnostics if you want help debugging it. Please note that expressVPN have updated their setup page to include their own Arch packages, so feel free to switch to that and see if it works any better.

I'll have access to my dev box from tomorrow, so I'm hoping to get an update pushed out then.

I think this package is rather buggy.

I turned on the feature where its supposed to start and connect automatically on startup, but it doesn't work, and when I noticed I wasn't connected I already have been seeding torrents for hours, which may have gotten me a DMCA...

Then when I try to connect, it takes like 10 attempts(without exaggeration).

Hi guys, I'm not able to update this package for a few days. The expressvpn guys have told me that their own package has also been delayed. I'll try to get an update out in the next few days, but anyone who can't wait and makes their own package in the meantime, please be aware that there is some post_install shenanigans that need to be done with this release -- it's not just a pkgver bump as normal. I can't remember the specifics, and I don't have access to my dev box to check, but if you go this route, take a look at the deb file's postinst file to see what it is that the deb package does.

Alternatively just hang fire for now, 1.5.1 still works and an update will be available one way or another in a few days.

The Express VPN website does not have a arch package on their website as far as I'm aware

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.