- Mais recentes
- Mais votos
- Mais comentários
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)
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 8 meses