[chef] Re: How to change ssl port for chef 11 omnibus server


Chronological Thread 
  • From: Jesse Nelson < >
  • To: chef < >
  • Subject: [chef] Re: How to change ssl port for chef 11 omnibus server
  • Date: Fri, 8 Feb 2013 02:08:49 -0800

I should specify that im using a custom bootstrap with the cookbook inside it and solo to provision the server via chef-server cookbook. 


On Fri, Feb 8, 2013 at 2:08 AM, Jesse Nelson < " target="_blank"> > wrote:
assuming you're using the chef-server cookbook (opscode/git) to install. Set the attribute:

node[:chef-server][:configuration][:nginx][:ssl_port]  = 8443

That should get your server installed  (if you use knife bootstrap and add chef-server to the run list with a -j to specify this data). This is working for me with chef-server/master  cookbook. I am not sure if the community cookbook has been updated to whats in git yet.




On Thu, Feb 7, 2013 at 9:13 PM, Martin Eigenbrodt < " target="_blank"> > wrote:
Hi all,

i installed chef server via the omnibus installer (ubuntu). And used

nginx['ssl_port']=8443

in my chef-server.rb.  Unfortunately cookbook uploading via knife fails, as it sill tries to use 443 (while, for example, knife node list works). I had a look
at the code and also added:

nginx['url']="https://#{node['fqdn']}:8443"
bookshelf['vip']=node['fqdn']+":8443"

This time the upload phase uses the right url, but the commit (during cookbook upload) fails, because it still uses 443.

So there is yet another Attribute to change?


Regards,

Martin





Archive powered by MHonArc 2.6.16.

§