Turns out that this was a bug already reported a while ago. Changing the port for Chef server is broken. Here is the bug report: https://github.com/chef/chef-server/issues/50
It includes the root cause analysis, as well as a workaround that worked for me.
Kevin Keane
The NetTech
http://www.4nettech.com
Our values: Privacy, Liberty, Justice
See https://www.4nettech.com/corp/the-nettech-values.html
-----Original message-----
From: Chris Magnuson < >
Sent: Monday 17th August 2015 11:21
To:
Subject: [chef] Re: Changing listen ports for chef server?
I found this with Google, maybe you did as well.
CJ
From: Kevin Keane Subscription
Reply-To: " " target="_blank" title="This external link will open in a new window"> "
Date: Monday, August 17, 2015 at 11:16 AM
To: " " target="_blank" title="This external link will open in a new window"> "
Subject: [chef] Changing listen ports for chef server?
I would like my open-source chef server to change the ports it listens to. The goal is for it to coexist with a regular Web server.
Apparently, there are entries in chef-server.rb that accomplish this:
nginx['non_ssl_port'] = 4080
nginx['ssl_port'] = 4443However, when I do this (and of course change the client URL correspondingly), Chef reports internal errors. The nginx log file shows that an internal connection fails:
[error] 15162#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: <redacted>, request: "GET /organizations/<redacted>/cookbooks/base_files/0.3.2 HTTP/1.1", upstream: "http://127.0.0.1:8000/organizations/<redacted>/cookbooks/base_files/0.3.2", host: "<redacted>:4443"
When I remove the entries in chef-server.rb, everything goes back to normal.
Is there something else I have to do in order to change the listen ports?
Kevin Keane
The NetTech
Our values: Privacy, Liberty, Justice
See https://www.4nettech.com/corp/the-nettech-values.html
Archive powered by MHonArc 2.6.16.