使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款
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.

主題
網路與內容交付
標籤
Amazon VPC網路與內容交付AWS Client VPN
語言
English
rePost-User-7288041
已提問 1 年前檢視次數 335 次
1 個回答
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
已回答 1 年前
  • rePost-User-7288041
    1 年前

    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.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋，同時有助於提問者的專業成長。

回答問題指南

相關內容