[chef] Re: chef-client "Bad Request"

[Daniel DeLeo <dan@kallistec.com>]

I'm pretty sure this means that the FQDN on your ssl cert doesn't match the hostname. Have a look at your chef.json file.

You might also want to look at this thread: http://lists.opscode.com/sympa/arc/chef/2009-06/msg00000.html

HTH,

Dan DeLeo

On Wed, Jul 8, 2009 at 12:35 PM, John Timms <john@gnoso.com> wrote:

When running chef-client, I am getting a 400 "Bad Request" error, instead of the 401 error that I should be getting. the server thereafter shows up in the chef-server admin interface for registrations, but even after validation, the server does not show up in the list of nodes and running chef-client again produces the same error. I'm not really sure what to do here, though I've done a good bit of searching through the documentation. Looking through the logs on the chef-server, I noticed that there was the following warning:

 

"WARNING: making https request to https://10.4.4.37/openid/server/node/juliet without verifying server certificate; no CA path was specified."

 

and on the next line:

 

"Discovery failed for https://10.4.4.37/openid/server/node/juliet: Failed to fetch identity URL https://10.4.4.37/openid/server/node/juliet : Error connecting to SSL URL https://10.4.4.37/openid/server/node/juliet: hostname does not match - (Merb::ControllerExceptions::BadRequest)"

 

What is the cause of this problem and how can I resolve it? Happy to provide more information if needed.

 

John Timms