Skip to content

After upgrading to AWS VPN Client 4.1.0 Can't connect to VPN

0

As soon as our staff upgraded to AWS VPN Client 4.1.0 they can no longer connect to VPN. Error: connection failed due to a TLS handshake error.

I realize that we may need to upgrade TLS on our gateway server - we will do so but this will take time. What we need RIGHT NOW is a way to download and install a prior version of the VPN Client as a quick workaround.

I'd appreciate any advice or direction.

asked 2 years ago753 views

1 Answer
0

Hi GilS,

You can download the previous versions of the AWS VPN client application from the respective Operating System Release notes page[1].

The " TLS handshake error" usually appears when there is an issue with the certificates, therefore its better to verify if the certificates which you are using to connect to the client VPN endpoint are still valid.

References
[1]- AWS Client VPN for Windows release notes

[2]- Troubleshooting AWS Client VPN: Client software returns a TLS error when trying to connect to Client VPN - AWS Client VPN

[3]- Troubleshooting common AWS Client VPN problems - AWS Client VPN

answered 2 years ago

AWS
SUPPORT ENGINEER

revised 2 years ago

AWS
SUPPORT ENGINEER

revised 2 years ago

  • While I appreciate the automated response, I don't think it is relevant. As I explained, several of our staff upgraded the AWS client to version 4.1.0 - and were immediately blocked. This implies that there is nothing wrong with the users' credentials. It cannot be a Firewall issue, as the firewall has not changed. VPN was working fine just before the update.

    Therefore the problem is with the new VPN client. We need Either AWS needs to issue a version upgrade hot fix, or we need to downgrade. This is a critical urgent issue.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.