- Le plus récent
- Le plus de votes
- La plupart des commentaires
From what I recall - this issues comes when "Domain Name" on certificates is empty. Can you please confirm in your ACM if your certificates have appropriate Domain Name ?
Edit: To fix it, you need to use FQDN e.g. ./easyrsa build-client-full client2.example.com nopass
This will generate certificate with correct domain i.e. client2.example.com and that should make it visible in the Client VPN console. I'll provide feedback to the service team as well on this as we should clarify our documentation bit more.
I am facing the same issue, where the server domain name is not populating. Its empty after importing to AWS certificate manager.
Also the server needs FQDN eg
./easyrsa build-server-full vpn.example.com nopass
then it will show in the client vpn console , otherwise i can't select it the server certificate menu (import was ok)
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a un an
- demandé il y a 2 ans
- demandé il y a 5 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 9 mois
Why does amazon let me import certificates without a FQDN in the first place if Services like AWS Client VPN does not let me use them... This is poorly designed.