The CHEF is not able to access the client nodes due to SSL issue.
Can CHEF download internal files using https connection as well?
Currently our internal links to download any files are using only http:// and probably this is the first time we are trying to use https://
When I am trying to check the SSL from check(knife ssl check) it seems its not validating properly for the SSL connections.
Without more detail it's hard to be sure, but it sounds like you might just need to update the SSLs. This doc is likely a good place to start. If you've already gone through that, please add more detail about the error you're seeing, how it's getting triggered, and what you have tried so far.
Hi Benny, Thanks for your reply, below is the error i am getting when trying to access a https link using cookbook.
[2020-10-01T17:32:09+01:00] FATAL: Stacktrace dumped to c:/.chef/local-mode-cache/cache/chef-stacktrace.out
[2020-10-01T17:32:09+01:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2020-10-01T17:32:09+01:00] FATAL: OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain)
I tried to follow the document you shared by no luck, We are still using CHef server 12.5.0, Will SSL configuration work on this older version of CHEF?
Do we need to change anything on Certificate for enabling SSL
The error you are getting there is that you have a self signed certificate on the chef server.
The document Benny linked will help you get setup with a standard certificate from a public issuer that will be recognized by default, alternatively if you are happy with self signed, you can get the certificate into the knife cache with knife ssl fetch
You will also need to get this setup for the chef-client on the nodes - Joshua Timberman has a blog post on this, from a few years ago. I'm not 100% certain if it is still valid though. The easiest option is however to use a certificate from a trusted CA.