Skip to content
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

knife ssl check mismatched cert error message is not helpful #9024

Open
tas50 opened this issue Oct 25, 2019 · 0 comments

Comments

@tas50
Copy link
Member

@tas50 tas50 commented Oct 25, 2019

I burned a ton of time after hitting this one. It seems like a common getting started error with Chef that we should really handle better. If you spin up a node in EC2 it ends up with the cert being signed by the internal hostname and you can't use that self signed cert with knife. The solution it to update the API URL in the server config and reconfigure, but good luck finding anything online to tell you that. We should expand this error message to point to some sort of help documentation otherwise users are going to just drop off here after they can't get the server and knife to talk w/o turning off SSL verification.

Connecting to host 34.213.52.123:443
ERROR: The SSL cert is signed by a trusted authority but is not valid for the given hostname
ERROR: You are attempting to connect to:   '34.213.52.1233'
ERROR: The server's certificate belongs to 'ip-172-31-25-123.us-west-2.compute.internal'```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.