Sorry you hit this issue! We are currently working on making it easier to configure Chef 11 Server to listen on non-standard HTTP/HTTPS ports. This includes requiring less configuration in the /etc/chef-server/chef-server.rb file AND ensuring these values are linked together correctly in the internal chef-solo recipe code (i.e. the underpinnings to “chef-server-ctl reconfigure”).
I’ve created a ticket to track the issue you hit:
If you have the cycles, please attach any additional debug info to that ticket (like the knife upload with -VV output).
Software Development Engineer, Opscode, Inc.
IRC, Skype, Twitter, Github: schisamo
On Feb 8, 2013, at 12:13 AM, Martin Eigenbrodt firstname.lastname@example.org wrote:
i installed chef server via the omnibus installer (ubuntu). And used
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:
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?