-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certificate validation failure for CLI #5730
Comments
Forgot to mention that server accepts certificate and works fine it just problem appears using CLI/CURL |
Hello @vasilij-icabbi You will be able to add more IP addresses in the SANs of your certs in a future release: check this merged PR #5602 For now, you'll need to use DNS names and/or fill /etc/hosts if you dont have a DNS servers |
Thanks @tristan-weil I think you're pointing @vasilij-icabbi in the right direction here – hopefully that will resolve the issue. That fix is in 1.5.0 which is available now. |
Thank you @pearkes and @tristan-weil . Confirm that issue is solved in Consul 1.5.0. For prior versions I guess viable option is to use OpenSSL or alike to generate certificates with SAN. |
Consul Version: 1.4.4
OS: Ubuntu Minimal 18.04
Cloud: AWS
Hello,
I am trying to add TLS certificates following this tutorial: https://learn.hashicorp.com/consul/advanced/day-1-operations/certificates
It all works fine, I create CA and Server TLS, but when it comes to CLI cert I get following error:
If I try to change Private IPv4 to either private or public IPv4 DNS I get following error:
Could you please help me identify what am I doing wrong?
Thank you.
The text was updated successfully, but these errors were encountered: