By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AWS Client VPN not negotiating a TLS connection

0

We have a AWS Client VPN since 2019 and was last successfully used 5/26. As of 5/27 we are no longer able to connect and form the client logs it appears that the server is no longer there or it is not accepting TLS connection. Log are showing that we can make a TCP connection but not TLS negotiating is available. I was able to create a new Client VPN but I am having the same issues. I also used OpenSSL to see it I could list the ciphers that the server is accepting but again there is not a valid response.

Note: we were unable to see any logging in cloud watch after 5/26 and our test client VPN has no Logs at all.

Topics
Networking & Content Delivery
Tags
Amazon VPCNetworking & Content DeliveryAWS Client VPN
Language
English
rePost-User-7288041
asked a year ago327 views
1 Answer
0

For TLS error, You can check below 2 possible causes and solutions. https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/troubleshooting.html#client-cannot-connect

Ref: https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/troubleshooting.html https://docs.aws.amazon.com/vpn/latest/clientvpn-user/common-troubleshooting.html

AWS
DarshanP
answered a year ago
  • rePost-User-7288041
    a year ago

    I have gone through these debug process and have tried different networks. Nothing has changed on my local firewall and we have not changed the network ACL for the VPN subnet. We are not getting a TLS negotiation and this was reported to us on 5/27 by our end users. I would think that we would see connection attempts in Cloud watch but there is nothing.

    Based on out testing with TCPDump we are not receiving any packets back from the VPN service.

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.

Guidelines for Answering Questions

Relevant content