- Newest
- Most votes
- Most comments
The core problem often stems from background processes interfering with the Client VPN's ability to launch browser pop-ups.
Troubleshooting Steps:
-
Check for Conflicting Software:
- Look for and disable any other VPN clients running in background
- Temporarily disable antivirus/security software, or add AWS VPN Client to exceptions
- Check and disable any configured proxy settings
-
Reinstallation Process:
- Completely uninstall AWS VPN client
- Restart your Mac
- Install latest version to a non-default location
- Test connection
-
Additional Verification:
- Test the connection from a different device to isolate if it's machine-specific
- Check system logs for any blocking events
If these steps don't resolve the issue, it would be worth logging a case with AWS Support for further insights and in-depth troubleshooting assistance.
Based on the information provided, you're experiencing an issue with the AWS VPN Client not opening a browser window for SSO authentication on your M3 MacBook. This is a known issue with the AWS Client VPN when using federated authentication (SAML-based SSO).
Here are some potential solutions:
-
Make sure your client configuration file contains the
auth-federateflag. From your description, it seems it does, but it's worth double-checking. -
Try exporting the latest configuration file from the AWS Client VPN service and reimporting it into the AWS VPN Client application.
-
If you're using Google Chrome as your default browser, there might be compatibility issues with recent Chrome versions and AWS Client VPN SAML authentication. Try disabling the Chrome flag "Reduce waiting time for Private Network Access preflights response" by going to chrome://flags/ in your browser.
-
It's worth noting that the AWS VPN Client for macOS is not yet natively optimized for Apple Silicon (M-series) processors and runs through Rosetta 2 emulation, which might contribute to some instability.
-
If the issue persists, try clearing any cached credentials or browser cookies related to your SSO provider (JumpCloud).
The intermittent nature of the issue (working after logoff/logon or reboot) suggests there might be a session or state management issue between the VPN client and the authentication process.
Sources
Troubleshooting AWS Client VPN: Client does not open browser for an endpoint — federated authentication - AWS Client VPN
Latest Google Chrome breaks AWS Client VPN SAML Auth | AWS re:Post
Native AWS VPN Client for Apple Silicon (arm64) | AWS re:Post
1+2 was tried, and since it works after a fresh restart I doubt the profile is the problem. 3. That flag does not exists, or is hidden. I'm using Chrome v138. But this also happens when not using Chrome as default browser. 4. could be...? 5. The problem is, the VPN app doesn't even attempt to open a browser. I can make sure there is no Chrome (or Firefox or Safari or MS Edge) running, and the app will not open one for the SSO login as it should.
The original log ended where the app hangs... if the app doesn't hang it continues with:
2025-06-26 10:08:15.559 -04:00 [DBG][TI=1][prod] Calling helper command /Applications/AWS VPN Client/AWS VPN Client.app/Contents/Resources/AWS VPN Client/Contents/MacOS/ACVCHelperTool --start "/Users/aaa/.config/AWSVPNClient/ovpn-mgmt-prod" "/Users/aaa/.config/AWSVPNClient/OpenVpnConfigs/validation-prod" "False"
2025-06-26 10:08:15.559 -04:00 [DBG][TI=1][prod] Starting process
2025-06-26 10:08:15.585 -04:00 [DBG][TI=18][prod] Start to read process output
2025-06-26 10:08:16.715 -04:00 [DBG][TI=18][prod] End reading process output
2025-06-26 10:08:16.913 -04:00 [DBG][TI=1][prod] Calling helper command /Applications/AWS VPN Client/AWS VPN Client.app/Contents/Resources/AWS VPN Client/Contents/MacOS/ACVCHelperTool --isAlive "2431" "8096"
2025-06-26 10:08:16.931 -04:00 [DBG][TI=1][prod] Called isAliveProcess
2025-06-26 10:08:16.932 -04:00 [DBG][TI=1][prod] Connecting to management port: 8096
2025-06-26 10:08:16.937 -04:00 [INF][TI=1][prod] Connecting to management interface... host 127.0.0.1, port 8096
2025-06-26 10:08:16.948 -04:00 [DBG][TI=1][prod] Socket connected
2025-06-26 10:08:16.948 -04:00 [DBG][TI=1][prod] Starting to listen to management port
2025-06-26 10:08:16.951 -04:00 [DBG][TI=1][prod] Setting localNetworkCidrsStringForCurrentConnection to 192.168.0.0/22,192.168.0.0/22
2025-06-26 10:08:16.952 -04:00 [INF][TI=11][prod] Received bytes: 15
2025-06-26 10:08:16.953 -04:00 [DBG][TI=11][prod] Message marshalling complete
2025-06-26 10:08:16.954 -04:00 [DBG][TI=11][prod] CM received: ENTER PASSWORD:
2025-06-26 10:08:16.963 -04:00 [DBG][TI=11][prod] CM processsing: ENTER PASSWORD:
...
So the app clearly never tries to call the helper tool. But I checked with ps that it is running. If I kill it and restart the VPN app, it restarts it, but doesn't log the line, and of course doesn't work.
I assume there are no alternative tools that can be used?
Relevant content
- asked 4 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 18 days ago
I think I'll have to talk IT if they can disable some of their "security" software, but this is not a problem isolated to just my computer, but since I can't find others with this problem it might have to-do with our computer setup.
Thanks everyone for giving me a few new ideas. I'll post a reply here if I ever figure it out.