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.

Dont works EVPN. Im from Russia. We have a hard censorship. Help me, friends. Thanks.

Hm, well the expressvpn.service messages seem to be benign (I have the same), and apart from network_lock, your preferences are identical to mine. You didn't mention what your networking setup is, but that's what I would check in this situation. I don't see why disabling network_lock would affect the situation if that was responsible though -- afaik, that setting only affects what happens when expressvpn loses connection to the server you have selected, not the initial connection itself.

If checking your journal for suspicious entries from your network manager/custom networking solution doesn't give you any hints, then you might want to contact expressvpn support.

@WorMzy thanks for a prompt reply. Answers:

1. Yes, that's all I get from expressvpn diagnostics. It's really not very helpful.
2. journalctl -b -u expressvpn.service:

-- Logs begin at Fri 2017-03-24 12:28:26 CET, end at Thu 2018-04-05 10:41:06 CEST. --
Apr 05 10:39:29 arch systemd[1]: Started ExpressVPN Daemon.
Apr 05 10:39:29 arch expressvpnd[17909]: 2018/04/05 10:39:29 method Authenticate has wrong number of ins: 2
Apr 05 10:39:29 arch expressvpnd[17909]: 2018/04/05 10:39:29 method SetAuth has wrong number of ins: 2

Because you mentioned network_lock I've set it from default to off and it started working again (yay!). Any suggestion how to troubleshoot this further? I'd prefer to have network_lock ON, since it's a really nice feature.

My current (workable) preferences:

$ expressvpn preferences
auto_connect            false
desktop_notifications   true
disable_ipv6            true
force_vpn_dns           true
network_lock            off
preferred_protocol      auto
send_diagnostics        false

@lknix: No problems here. I'm up-to-date on Arch (as of 10 minutes ago), using Network Manager and have expressvpn's "network_lock" enabled.

Is that all the output you get from expressvpn diagnostics? There should be a log.

Is there any useful information in # journalctl -b -u expressvpn.service?

Note that you can make terminal output more readable on the AUR comments by surrounding it with three backticks (like github)

like so

Anyone else has a problem with ExpressVPN not connecting after the latest package upgrade? I'm getting this:

$ expressvpn connect es Selecting a location in Spain for you... Connecting to Spain... Unable to connect to Spain

• Check your internet connection or try a different location.
• Internet traffic is blocked to protect your privacy.
• To retry the connection, type 'expressvpn connect'
• To disconnect from the VPN and unblock internet traffic, type 'expressvpn disconnect'

AND

$ expressvpn diagnostics

ExpressVPN client version : 1.4.1 ExpressVPN client build : 1.4.1 (2966) Operating system version : Arch Linux Timestamp: 2018-04-04 12:40:59.765946882 +0200 CEST Cluster list file version: 20180404|1| Cluster list download date: 2018-04-04 12:19:55.01692747 +0200 CEST

==============================================

Connecting to Spain - Madrid, ip: 245.141.0.172, protocol: udp Diagnostics: has internet: true udp ping: is_timeout: false, latency: 50.6 ms cluster stats: min/avg/max/stddev = 50.497/50.667/50.844/0.123 ms, x cluster packet loss rate: 0.0% dns: 192.168.1.1,1.0.0.1,8.8.4.4

No matter which VPN server, protocol I use (and wifi/ISP) - always the same. At the same time it works w/o a problem on Android. Any suggestions?

Thanks WorMzy you are a person of your word as you have indeed upgraded EVPN to the latest version which works a treat. Best wishes, Aurelias

@Aurelias: I'm currently on holiday in Japan, but my OOD packages will be updated shortly after I get back to my desktop (approx. five days time).

EDIT: forgot I'm a co-maintainer of this package. 2bluesc, are you still active?

Hello WorMzy, Seems EVPN has (yet again) released a newer version than is currently available in the AUR. Any chance you will be upgrading it shortly? I note someone has flagged the current package here as out-of-date on 2018-03-04. Cheers.

I have solved my problem. Is seem that expressvpn (in some previous version?) substituted /etc/resolv.conf with a link to /var/run/expressvpn/resolv.conf Now I have changed resolv.conf from symbolic link to the real file and all is working.