Solve AWS Client VPN issues: error loading your connection profiles

Content

After installation, if you encounter the problem There was an error loading your connection profiles: /Users/{LOGGED _IN_USER}/.config/AWSVPNClient/ConnectionProfiles

There will be 2 solutions, which are

  • Manual management by creating the file yourself and placing it in the location where the Client VPN accesses the data
  • Another way is to use this github to help fix

In this section, I will skip the part about generating server and client certificates and keys to the part where the .ovpn file is obtained

If you need more information on this part, you can read more at Getting started with Client VPN

In summary, what AWS Client VPN is looking for is ConnectionProfiles, which I'm not sure why. This issue occurs on some machines and not on others, which is a mystery that has yet to be determined 😤

Manual management by yourself

Create folder as follows

Create ConnectionProfiles file with the following content

Link
https://medium.com/@teeppiphat/%E0%B9%81%E0%B8%81%E0%B9%89%E0%B8%9B%E0%B8%B1%E0%B8%8D%E0%B8%AB%E0%B8%B2-aws-client-vpn-error-loading-your-connection-profiles-8b6e09080e0b
Summary
After installing AWS Client VPN, users may encounter the error: 'There was an error loading your connection profiles: /Users/{LOGGED_IN_USER}/.config/AWSVPNClient/ConnectionProfiles'. There are two solutions: manually create the necessary files and place them in the directory where the Client VPN reads data, or use a GitHub resource to assist with the fix. The article skips the process of generating server and client certificates and keys, focusing instead on obtaining the .ovpn file. For additional information, users can refer to the 'Getting started with Client VPN' documentation. Essentially, the AWS Client VPN seeks ConnectionProfiles, and the reason this issue occurs on some machines but not others remains unclear. The manual solution involves creating a specific folder and a ConnectionProfiles file with the appropriate content. This mysterious issue continues to perplex users, as the underlying cause has yet to be determined.
Â