My Ubuntu 20.04 installation decided 1,5 hours ago to update awsvpnclient from version 2.0.0 to 3.0.0, and it has not worked since because it seems to think that its configuration directory is hosted on a network file system, which is not supported (the file is, and always was hosted on a local, eCryptFS-encrypted file system). The UI shows a dialog "Connection failed, try again".
This is from the logs in /var/log/aws-vpn-client/$USER
2022-03-07 17:36:56.875 +01:00 [DBG] [TI=6] Start method called: OpenVPN validation file: /home/stefan/.config/AWSVPNClient/OpenVpnConfigs/current_connection.txt, management password file: /home/stefan/.config/AWSVPNClient/xxxx-1234.txt
2022-03-07 17:36:56.875 +01:00 [ERR] Drive type Network not supported.
2022-03-07 17:36:56.875 +01:00 [ERR] [TI=6] Unhandled exception
ACVC.Core.OpenVpn.ReferencedFilePathInvalidException: File: /home/stefan/.config/AWSVPNClient/OpenVpnConfigs/current_connection.txt may be a path to an unsupported drive type, which is not allowed for security reasons
I downgraded successfully back to 2.0.0 so that my connection is working again, for now. As I'm sure this is a temporary solution and the 2.0.0 client will be rejected by the AWS VPN service at some point, is it possible for me to file a bug about this problem, or can I solve it in some other way?
I tried moving /home/$USER/.config/AWSVPNClient to a location outside of the encrypted drive and create a symbolic link to this directory in ~/.config/, but the Network drive error kept occurring.
I'm having the same issue too.
AWS Support told me today, this: Yes, our internal team is already aware of this issue and we they are working on a fix for this. Unfortunately, I do not have an ETA but a fix is in the pipeline and team is actively working to get this fixed.
Hopefully we'll have a 3.0.1 out soon.