| Git Clone URL: | https://aur.archlinux.org/expressvpn.git (read-only, click to copy) |
|---|---|
| Package Base: | expressvpn |
| Description: | Proprietary VPN client for Linux |
| Upstream URL: | https://expressvpn.com |
| Licenses: | LicenseRef-custom |
| Submitter: | 2bluesc |
| Maintainer: | 2bluesc (WorMzy) |
| Last Packager: | WorMzy |
| Votes: | 49 |
| Popularity: | 0.000216 |
| First Submitted: | 2016-03-26 03:18 (UTC) |
| Last Updated: | 2024-12-10 09:46 (UTC) |
@rgill: Dunno if you have been working with the eVPN guys, but auto_connect is fixed in 2.2.0:
$ zcat /usr/share/doc/expressvpn/changelog.gz | head
expressvpn (2.2.0)
* Improved activation & connection reliability in some countries.
* Fixed an issue where the app wouldn’t auto-connect on boot.
\o/
@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.
@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.
Thanks for updating so fast!
I case anybody has the same problem as eperez: the correct command to use is
systemctl start expressvpn.service
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.
@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.
@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
/usr/share/bash-completion/completions/
And installed yours again which does work! But the autoconnect functionality doesn't. Any ideas? If any information is needed, feel free to ask.
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:
https://aur.archlinux.org/cgit/aur.git/tree/?h=expressvpn&id=d2a8ac08c397471861b6e4b699c75495c8ed72c9
@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"
else
head -1 <<<$conn
fi
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.
Pinned Comments
paintie commented on 2020-07-28 21:16 (UTC)
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 commented on 2019-11-06 13:15 (UTC)
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 runexpressvpn statusmay 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.
WorMzy commented on 2019-01-11 11:38 (UTC) (edited on 2019-01-23 20:41 (UTC) by WorMzy)
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.