Package Details: awsvpnclient 4.1.0-3

Git Clone URL: https://aur.archlinux.org/awsvpnclient.git (read-only, click to copy)
Package Base: awsvpnclient
Description: AWS VPN Client
Upstream URL: https://aws.amazon.com/vpn/
Keywords: aws aws-clientvpn aws-vpn aws-vpnclient clientvpn
Licenses: custom
Submitter: project0
Maintainer: project0
Last Packager: project0
Votes: 10
Popularity: 0.90
First Submitted: 2021-06-26 08:56 (UTC)
Last Updated: 2024-12-13 18:25 (UTC)

Pinned Comments

project0 commented on 2021-06-28 15:58 (UTC) (edited on 2024-02-12 11:07 (UTC) by project0)

Please note the following requirements for AWS VPN Client:

For troubelshooting its worth checking first the logs:

/home/$USER/.config/AWSVPNClient/
/var/log/aws-vpn-client/$USER/

See also the official docs: https://docs.aws.amazon.com/vpn/latest/clientvpn-user/client-vpn-connect-linux.html

If you face any other problem please check the troubleshooting guide (DNS issues): https://docs.aws.amazon.com/vpn/latest/clientvpn-user/linux-troubleshooting.html#aws-provided-client

Latest Comments

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

bigcajun826 commented on 2024-12-16 15:48 (UTC) (edited on 2024-12-16 15:49 (UTC) by bigcajun826)

@project0 The latest changes work for me, with one minor change I needed on my end (Running X11 with XFCE)

diff --git a/awsvpnclient.desktop.patch b/awsvpnclient.desktop.patch
index a95757d..be462ac 100644
--- a/awsvpnclient.desktop.patch
+++ b/awsvpnclient.desktop.patch
@@ -4,7 +4,8 @@
  Encoding=UTF-8
  Name=AWS VPN Client
  Comment=AWS VPN Client
+-Exec="/opt/awsvpnclient/AWS\sVPN\sClient" %u
 +StartupWMClass=AWS VPN Client
- Exec="/opt/awsvpnclient/AWS\sVPN\sClient" %u
++Exec="/opt/awsvpnclient/AWS\ VPN\ Client" %u
  Path=/opt/awsvpnclient
  Icon=acvc-64.png

Apparently the \s doesn't work quite right so I had to change them to space characters.

project0 commented on 2024-12-13 18:39 (UTC) (edited on 2024-12-13 18:39 (UTC) by project0)

Hey there, there had been some significant updates:

  • desktop file fixed the whitespaces, patching the the additional StartupWMClass
  • openssl 3.0 is bundled with openvpn and fips module support has been adopted from original debian install scripts.
  • removing openssl-1.1 dependency, it should no longer be necessary.
  • .NET 3 -> 8 removing the icu patch fix, translation should work again.

I have currently no AWS Client VPN running somewhere, so i couldnt test the connection fully at my own. Please let me know if this is not working, also check the logs in case of problem.

project0 commented on 2024-12-12 17:02 (UTC)

Sorry guys, i actually tested the build locally and it did look fine to me, but it turned out to be some caching issue. Reverted the change and will look at the weekend into. I apologize for the late response.

damentz commented on 2024-12-12 16:15 (UTC)

I agree, and if maintainer doesn't have time to "fix", just revert the last change for now:

git revert 56a25519f56a6bbd8b8f1fbd1e381bd95c25a5d9

npreining commented on 2024-12-12 15:35 (UTC)

PKGBUILD is completely broken, maintainer please build the package ONCE before publishing a new version.

cor3000 commented on 2024-12-12 02:24 (UTC) (edited on 2024-12-16 02:00 (UTC) by cor3000)

same error here, so I changed the extraction command in PKGBUILD to use .zst instead

-  tar -xf "${srcdir}/data.tar.xz" -C "${pkgdir}"
+  tar --zst -xvf "${srcdir}/data.tar.zst" -C "${pkgdir}"

however this leads to additional errors, due to incompatible patch files. Which I also adjusted manually.

awsvpnclient.desktop.patch (replace one line)

-Exec=/opt/awsvpnclient/AWS\ VPN\ Client %u

new

-Exec="/opt/awsvpnclient/AWS\sVPN\sClient" %u

awsvpnclient.runtimeconfig.json.patch (replace one line)

old

"tfm": "netcoreapp3.1",

new

"tfm": "net8.0",

then updated the related sha512 sums in PKGBUILD

old

'615154162a69b99f5e3f7ab450ea7fbd58e944075bd762e3ceacfb1a71e8faa894de2595d8b72cde143702a0f8d2844c2b847d403ae528b4d3c48ab195a1df2b'          
'1d45e50de14b9e10b6463692df63bfb4cbedfed952022c95f05bde46ece37ac1a433b76e49f255f38b1bd67c0f0f13d2d8c963051a144553c63149e6041d6603')

new

'db634786c7b745299d727a8320d3ee76795f2d6bdc52b4bb543e8303313f859469d4a13c1328a40733c25009535506633a25b09d2e28178ab349fa99ff8f24c6'          
'b8bf877cff341ab79737bbb77a3c7d6686807e10a6a3b6cd097d04f04edac15680a0775878f9c6c02ffdf7873a8f380528df8a393bddaa0983a46f87a2c87a79')

after those changes the build succeeded and I was able to install the package however the result still didn't work with my current VPN configuration so I reverted back to version 4.0.0

maybe this helps someone

UPDATE 2024-12-16 the latest version 4.1.0-3 fixed the errors above, thanks @project0, connecting using my previous vpn config works again without changes

Accessory commented on 2024-12-10 13:50 (UTC)

I cannot update or install the awsvpnclient package.

I got the following error message:

tar: /home/xxxxxx/.cache/yay/awsvpnclient/src/data.tar.xz: Funktion open fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: Error is not recoverable: exiting now
==> FEHLER: Ein Fehler geschah in package().
Breche ab...
-> Fehler beim Erstellen: awsvpnclient-exit status 4
-> Die folgenden Pakete konnten nicht installiert werden. Ein manueller Eingriff ist erforderlich:
awsvpnclient - exit status 4

The error points to a data.tar.xz that does not exist. But there is a data.tar.zst. Maybe something changed and need to be adjusted in the PKGBUILD file.

joshm commented on 2024-05-01 14:11 (UTC)

@beregond -- thanks for reminding me. I had tried that but something else must have been wrong. With a new VPN config and enabling systemd-resolved, it's working.

I do wish it would just work with openvpn directly, but oh well.

beregond commented on 2024-05-01 11:32 (UTC)

@joshm - had the same error, turns out I had to fix my DNS resolver, like in pinned post is suggested - sudo systemctl --now enable systemd-resolved.service

joshm commented on 2024-04-19 16:01 (UTC) (edited on 2024-04-19 16:01 (UTC) by joshm)

I can't get this to work. I get the same error as in this comment. I have enabled/started the awsvpnclient unit. I get pretty far in the process (browser window opens and I'm told to close it -- we're using SAML), but then the connection fails:

2024-04-19 12:00:17.387 -04:00 [DBG] [TI=58] [PID: 19637] Fri Apr 19 12:00:17 2024 WARNING: Failed running command (--up/--down): external program exited with error status: 1
2024-04-19 12:00:17.387 -04:00 [DBG] [TI=58] [PID: 19637] Fri Apr 19 12:00:17 2024 Exiting due to fatal error
2024-04-19 12:00:17.417 -04:00 [DBG] /bin/ps exit code: 0
2024-04-19 12:00:18.403 -04:00 [DBG] /bin/ps exit code: 1
2024-04-19 12:00:18.403 -04:00 [ERR] [TI=53] Failed to get process owner of PID: 19637. Stdout: , stderr: 
2024-04-19 12:00:18.403 -04:00 [WRN] [TI=53] Exception occured checking process alive: System.Exception: Failed to get process owner of PID: 19637
   at ACVC.GTK.Service.DBus.OvpnGtkService.GetProcessOwner(Int32 pid) in /home/ubuntu/Jenkins/workspace/GtkBuild/SecureConnectClient/ACVC.GTK.Service/DBus/OvpnGtkService.cs:line 345
   at ACVC.GTK.Service.DBus.OvpnGtkService.IsAliveAsync(Int32 pid) in /home/ubuntu/Jenkins/workspace/GtkBuild/SecureConnectClient/ACVC.GTK.Service/DBus/OvpnGtkService.cs:line 254
2024-04-19 12:00:18.404 -04:00 [DBG] [TI=53] Wait for OpenVPN processes to finish graceful shutdown
2024-04-19 12:00:18.409 -04:00 [DBG] [TI=53] All OpenVPN processes exited properly
2024-04-19 12:00:18.409 -04:00 [DBG] [TI=53] Finished waiting OpenVPN graceful shutdown. Proceed with killing any orphaned OpenVPN processes
2024-04-19 12:00:18.513 -04:00 [DBG] Orphaned process are alive: False
2024-04-19 12:00:18.513 -04:00 [DBG] [TI=53] Attempting to restore /etc/resolv.conf if /etc/resolv.conf.ovpnsave exists
2024-04-19 12:00:18.513 -04:00 [DBG] [TI=53] /etc/resolv.conf.ovpnsave not found

Anyone have any thoughts?

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