It just starting working in Safari for me now
Well, now Edge is exhibiting this behavior as well.
Any news on the new vpn client version release?
Hello,
Sorry to hear about this! These troubleshooting steps will point you in the right direction.
If not, you can reach out for help in these ways too.
- Ann D.
Try logging in with a different browser.
Change default browser to other than chrome will fix the issue
Hmm. I started another thread about this issue with macOS/Safari, but the error here doesn’t match? In Safari it just complains that the page can’t be open because Safari can’t establish a secure connection to 127.0.0.1.
Otherwise your example does sound similar. We use Google as our IdP and then our VPN is configured as an app with an ACS URL of http://127.0.0.1:35001.
Ahh, so first is the Safari error and then I guess eventually the client pops an unknown error. Fun!
Why am I not surprised that the AWS VPN team has again failed to maintain their client…
This a 5 month old thread and I updated the post to say the issue has been fixed why are you replying to this, is it to just shill Nord VPN which I see you do in a lot of your previous comments?
Thanks for sharing their response. Now we wait, I guess!
This VPN solution has it’s limitations but its been nice to not have to manage much more than the config so I really don’t want to have to roll a different solution.
Great thanks for sharing that.
I don’t know why Safari broke, but that was my original default and it just stopped working this week. I don’t recall restarting or explicitly updating prior to it breaking, but Chrome certainly broke as soon as I popped in to see what version I was on…
Thanks for sharing.
I followed your suggestion and disabled the Block insecure private network requests flag from the chrome://flags page, this workaround seems to work.
Regards.
Interesting. I guess the issues are similar but not quite the same between Safari and Chrome? My issues started in Safari and I used chrome as a backup until it auto updated. In Chrome it appears the auth workflow was successful, and then unknown error. In Safari the redirect to 127.0.0.1 is completely blocked because it seems to be trying to upgrade that redirect to HTTPS. 
I’m on 123.0.6312.59 and it’s not working as well.
Do you also not have an official support plan? I don’t know where else to get AWS’s attention on what is very likely a client issue at this point.
The AWS Client VPN team is aware of an issue affecting customers that use Google Chrome version 123 and SAML authentication.
We are working on a new client release to address this issue, and as a workaround, we recommend using another browser, such as Firefox. Alternatively, some MacOS users have reported a successful workaround of launching Chrome with these options:
open -a "Google Chrome" --args --disable-features=PrivateNetworkAccessForNavigations,PrivateNetworkAccessForNavigationsWarningOnly
Thanks for sharing! Odd that they didn’t see this coming and have an updated client available in time, but hopefully soon…
I don’t know an easy way to do it, but if you still have Firefox installed, put that as your default browser. Hopefully they’ll have a patch out soon, but who knows…
I found a command on stackoverflow and generated this script to download the previous version 122, install it and mark the package not to be updated when running apt upgrade.
sudo wget http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_122.0.6261.128-1_amd64.deb && \
sudo apt install ./google-chrome-stable_122.0.6261.128-1_amd64.deb -y && \
sudo apt-mark hold google-chrome-stable && \
google-chrome-stable --version \