[chef] Re: OSS chef-server


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: OSS chef-server
  • Date: Wed, 6 Nov 2013 07:35:31 -0800


On Tuesday, November 5, 2013 at 7:45 PM, BK Box wrote:

Ohai,

So I have been trying to spin up a new chef-server to test things out, but it is only temporary, so I have no need for an actual DNS entry to be setup. Although, no matter what configuration item I change it never downloads the cookbook from the IP address:


I have tried the following changes in the chef-server.rb and confirmed the settings are actually changed after a reconfigure:

api_fqdn "1.2.3.4"

#nginx['server_name'] = "chef.example.com"
nginx['server_name'] = "1.2.3.4"
nginx['url'] = "https://1.2.3.4"
chef_server_webui['web_ui_admin_user_name'] = "admin"

bookshelf["vip"] = node["ipaddress"]
bookshelf["url"] = "https://#{node['ipaddress']}"

I even recursively grepped all of /var/opt/chef-server to find the domain and change it from domain to IP and restarted. 

Nothing.

Has anyone used OSS chef-server with just the IP of the server?

Thanks.
--
BK Box
In the next point release of the chef-server, (11.0.10), it will defer to the provided Host header when generating URLs for responses, so that should fix your issue: https://tickets.opscode.com/browse/CHEF-4086

However, at some future time, we’re going to make chef-client verify SSL certificates by default (right now you have to opt-in). When that happens, you’ll have to have the correct CN (i.e. hostname) in your SSL certificate or disable cert verification on the client. See here for more about that: http://www.opscode.com/blog/2013/10/31/ssl-certificate-validation-in-chef/

-- 
Daniel DeLeo




Archive powered by MHonArc 2.6.16.

§