Skip to content

Instantly share code, notes, and snippets.

@thiagozs
Created June 19, 2024 18:55
Show Gist options
  • Save thiagozs/4d8c6e090a027fae3dd883163615f91e to your computer and use it in GitHub Desktop.
Save thiagozs/4d8c6e090a027fae3dd883163615f91e to your computer and use it in GitHub Desktop.
AWSVPNClient Fixes on ubuntu 24.04

Steps

Download

wget http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.0g-2ubuntu4_amd64.deb

sudo dpkg -i libssl1.1_1.1.1f-1ubuntu2.13_amd64.deb

Edit files and add Env vars

sudo vim /etc/systemd/system/awsvpnclient.service

Put the Enviroment line

[Service]
Type=simple
ExecStart=/opt/awsvpnclient/Service/ACVC.GTK.Service
Restart=always
RestartSec=1s
User=root
Environment=DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1

[Install]
WantedBy=multi-user.target

Create a simbolic link

cd /opt/awsvpnclient 

/opt/awsvpnclient  …
➜ sudo ln -s AWS\ VPN\ Client awsvpnclient  

Edit the menu

find / -name 'awsvpnclient.desktop' 2>&1 | grep -v 'Permissão negada'

/home/thiagozs/.local/share/applications/awsvpnclient.desktop
/usr/share/applications/awsvpnclient.desktop

Put this content here.

[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=AWS VPN Client
Comment=AWS VPN Client
Exec=/opt/awsvpnclient/awsvpnclient %U
Path=/opt/awsvpnclient
Icon=acvc-64
Terminal=false
Categories=Network;VPN;
Keywords=vpn;aws;
@dmirandaa
Copy link

I had to downgrade to version 3.13.0 to works, removed aws from apt list and not planning to update.

@babichmaxim
Copy link

Hello. I solved this issue with add Exec=env DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 /opt/awsvpnclient/AWS\ VPN\ Client %u
in "/usr/share/applications/awsvpnclient.desktop"

@varfrog
Copy link

varfrog commented Oct 16, 2024

Is anyone interested in running a VM for the VPN client, and route traffic through the VM? I have a few ways to set that up and can share some updated scripts.

@Davidster
Copy link

@aadit-panta I am getting the same issue as you even after installing version 3.15.0. did you have any luck finding a fix?

@Davidster
Copy link

@aadit-panta actually I was able to fix the issue by following these instructions 🎉

@reiakvam
Copy link

Got it working with ubuntu 24.04 and v 3.12.0 after a reboot.

@mrbeiertz
Copy link

mrbeiertz commented Nov 13, 2024

The service runs, but I can't see the UI when clicking on the AWS icon. However, after a reboot, it worked.

@varfrog
Copy link

varfrog commented Nov 13, 2024

Ubuntu 24.04 is now supported. At last!

image

@mrbeiertz
Copy link

It would be nice to provide an update to this guide to undo what we did here, for those that don't know how to do it, now that there is official support for it.

@mrbeiertz
Copy link

This is what I did:

# check if libssl1.1 has any dependencies
sudo apt-cache rdepends libssl1.1
sudo apt-get remove --purge libssl1.1
sudo apt update
sudo apt autoremove
sudo apt autoclean
sudo apt-get remove --purge awsvpnclient
ls -l /opt/awsvpnclient
sudo rm -rf /opt/awsvpnclient/awsvpnclient
sudo rm -rf /opt/awsvpnclient/ConnectionInfoFiles
sudo systemctl status awsvpnclient

Then follow the instructions on AWS to install AWS VPN 4.1+

@Ruhshan
Copy link

Ruhshan commented Nov 25, 2024

Using Ubuntu 24.04.1 LTS

Hi @mrbeiertz , just saw your comment and then realized that 4.1 is out now! Thanks a lot!

I followed your instruction to uninstall the old version then installed the new version from here.

Thought this time installation, starting and connection was without any hassle, but I was still unable to access the private resource. Then I looked into the logs and found this error

/opt/awsvpnclient/Service/Resources/openvpn/configure-dns: line 24: systemd-resolve: command not found

I have to create a symbolic link named systemd-resolve that points to resolvectl.

sudo ln -s /usr/bin/resolvectl /usr/bin/systemd-resolve

These additional steps got the vpn client working on ubuntu machine.

@unigazer
Copy link

unigazer commented Apr 23, 2025

The AWS VPN Client is now officially available for Ubuntu 24.04. If you are still experiencing issues, you can follow the official troubleshooting process.

I had an issue with the DNS, and just by adding one line of instruction in the OpenVPN configuration file, I was able to connect to the private resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment