Anyone else running into this? Seems to affect all platforms but its the new versions released today. I’m getting this error:
The VPN connection is being terminated due to a discrepancy between the IP address of the connected server and the expected VPN server IP. Please contact your network administrator for assistance in resolving this issue.
If I roll back to the previous version of the client VPN, I can connect just fine.
I personally stopped using the aws client vpn software and moved to Viscosity and has worked well for me.
Is it the AWS VPN Client or the AWS Client VPN endpoint irrespective of actual VPN client?
Are you connecting using an IP or DNS name?
Per What is AWS Client VPN? - AWS Client VPN under limitations it says “We do not recommend connecting to a Client VPN endpoint using IP addresses. Because Client VPN is a managed service, you will occasionally see changes in the IP addresses to which the DNS name resolves. In addition, you will see Client VPN network interfaces deleted and recreated in your CloudTrail logs. We recommend connecting to the Client VPN endpoint using the DNS name provided.”
For anyone else running into this issue - looks like a new version was released (3.7.0 on Ubuntu) over the weekend that fixes this.
Also, seems like the release notes for AWS VPN Client are not being updated…
This happened to me, when I was using a hotspot. Once I changed to another hot spot it worked.
If you need to get an older version you can change the download URL for a previous version.
https://d20adtppz83p9s.cloudfront.net/WPF/3.6.0/AWS_VPN_Client.msi
https://d20adtppz83p9s.cloudfront.net/WPF/3.1.0/AWS_VPN_Client.msi
As an example
My OS is Windows 10 Enterprise 64 bit, and I’m having this VPN connection issue as soon as I upgraded to AWS Client VPN v3.9.0. Whenever I attempted to connect (using v3.9.0_, I got error popups saying: “The VPN connection is being terminated because the address space of the local network your device is connected to has changed. Please establish a new connection.”
If I uninstalled v3.8.0 and then re-installed v3.8.0 (or even v3.5.0), I would be able to connect without any problems!
What is going on? Any help is greatly appreciated!
The VPN logs shows a IP mismatch when connecting.
While troubleshooting this issue i found out that disabling ipv6 makes the error disappear.
I’d say it’s more related to AWS’s actual VPN client software because if I install the previous rev, I can connect fine. But I have not tried any other OpenVPN clients since we use SAML - I haven’t spent the time to really find a client that can do AWS’s SAML auth.
It’s connecting to a DNS endpoint. The weird thing is it will actually finish connecting and then a second after will display the error message and disconnect.
This worked, so I guess it was an actual bug in the client.
Same. Happened when I switched to my hotspot. Resolved when I quit and restarted the VPN client.
3.9.0 gave me this error on an M2000 hotpsot (t-mobile), but downgraded to version 3.5.0 and it works fine.
Thank you deeply, Sir; the solution worked! I’ve been struggling with this issue for two months. May God bless You!
Did you get this resolved, was it a issue with 3.8 client version?
Ah gotcha. Sorry to hear that, but thanks for the data points. I’ve been evaluating using vpn endpoints w/SAML federation to Okta and this is helpful.
I’m having two SIMs in Germany. With my freank/telekom SIM I see this error as well. When switching to my sipgate/O2 SIM the error is gone.
I updgraded to an X Pro 5G hotspot, and it worked fine for a while, but then I had this problem with version 3.6.0, 3.9.0, and 3.10, but 3.5.0 still works.
Yes, the VPN connection issue was gone right after I upgraded to version 3.10.0, which contained some bug fixes.
Thanks!