[chef] Re: Unable to reach latest version installation Chef server webUI

[Brad Knowles < >]

On Aug 29, 2013, at 11:33 AM, Russell Bateman 
<
 >
 wrote:

> The delta here appears to be the Chef versions and, of course, the contents 
> and placement of Chef configuration.

Including the default ports that the Chef server listens on.  With Chef 11, 
it's now port 80 for http and 443 for https, and both API and WebUI calls can 
be handled on either port -- The 4000/4040 split no longer exists.

Also note that Chef 11 uses nginx as a front-end proxy, so I think the 
chef-server process itself may actually listen on 127.0.0.1, and lets nginx 
handle the communication with the outside world -- which might include 
terminating the SSL connection on behalf of chef-server.

In addition, IIRC it uses a self-signed cert, and certain libraries like 
spice & ridley will insist on validating the SSL cert and rejecting the 
connection if it is not correct -- which will cause failures on self-signed 
certs.


Can you tell that we've recently switched from Chef 10 to Chef 11?  ;-)

--
Brad Knowles 
<
 >
LinkedIn Profile: <http://tinyurl.com/y8kpxu>