2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
3
Hello.
Looking at this answer, it seems that you cannot select if the ACM domain is empty.
https://repost.aws/questions/QUoTNWCpiJRt62bMup7YzhCA/client-vpn-endpoint-creation-not-detecting-client-certificate-in-acm#AN8FlDxzKKTHa0Yrw6g9KYIg
Try specifying the domain when creating the server certificate as shown below.
./easyrsa build-server-full server.com nopass
I tried it with my AWS account, and it became possible to select it if there was a domain.
1
Verify that your server certificate is of the correct type, active, and in the same region as your VPN endpoint, and check for any permissions issues.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 9 Monaten
Here’s the same question I answered a few days ago also https://repost.aws/questions/QUMYbBBsxcQGCLWekupTG-Ow/clientvpn-mutual-auth-server-cert-missing-domain-name-thus-fails-to-work-with-clientvpnendpoint#AN8JwP-FC9R7iWdRSFnFdYZQ