You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
I installed ChefDk on my server and it broke my OpenSSL configuration/knife client. I am on open source chef server (11.4.4) on RHEL 6. Essentially, when I tried to connect to Chef Server with knife ( knife client list for example) I would get weird error like:
When I checked the SSL configuration being used using "knife ssl check" I saw that OpenSSL was using ChefDk certs instead of the certs embedded with the original omnibus install.
I had to uninstall ChefDK and reinstall chef-client.
Can Chef DK be installed alongside an existing chef-client/knife that relies on OpenSSL to connect to the server? Or am I missing something?
The text was updated successfully, but these errors were encountered:
Can you explain further? You have ChefDK and Omnibus chef-client installed on your workstation? What did you previously do to make OpenSSL trust your self-signed cert?
I installed ChefDk on my server and it broke my OpenSSL configuration/knife client. I am on open source chef server (11.4.4) on RHEL 6. Essentially, when I tried to connect to Chef Server with knife ( knife client list for example) I would get weird error like:
OpenSSL::SSL::SSLError: SSL_connect returned=5 errno=0 state=SSLv3 read server certificate B: certificate verify failed
When I checked the SSL configuration being used using "knife ssl check" I saw that OpenSSL was using ChefDk certs instead of the certs embedded with the original omnibus install.
I had to uninstall ChefDK and reinstall chef-client.
Can Chef DK be installed alongside an existing chef-client/knife that relies on OpenSSL to connect to the server? Or am I missing something?
The text was updated successfully, but these errors were encountered: