Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

knife cookbook upload does not respect port in chef_server_url #3846

Closed
dan-bolsun opened this issue Aug 31, 2015 · 4 comments
Closed

knife cookbook upload does not respect port in chef_server_url #3846

dan-bolsun opened this issue Aug 31, 2015 · 4 comments

Comments

@dan-bolsun
Copy link

Hi,

Currently I testing chef server on virtual machine and do some DNAT to access it. Server is configured due to guide and nginx listens on default 443 port. On my host system port 444 is used.
So knife.rb looks like this:
...
chef_server_url "https://my.chef.server.com:444/organizations/testorg"
...

After server and workstation setup some commands runs well. knife ssl fetch, knife ssl check and even knife data bag from file .... But when I try to upload some cookbooks with knife cookbook upload my_cookbook -V fails and INFO loglines look like:

INFO: Uploading chef-repo/cookbooks/my_cookbook/resources/manage.rb (checksum hex = ...) to https://my.chef.server.com:443/...
...

As you may see knife cookbook upload ... is sending cookbook to 443 port instead of 444 listed in knife.rb.

`knife cookbook upload -v' output:
Chef: 12.4.1

@stevendanna
Copy link
Contributor

This is likely a chef-server configuration problem. The chef-server generates upload links that the client is supposed to be able to just follow.

@dan-bolsun
Copy link
Author

Okay, thank you. I just need to run it on 443 port without any redirects

@stevendanna
Copy link
Contributor

@dan-bolsun It should be possible to change the listen port but isn't currently because of this bug:

chef/chef-server#50

Going to close this issue out in favor of the chef-server one above. Apologies for the trouble this bug has caused you.

@dan-bolsun
Copy link
Author

Not a problem. And thank you for quick response!

@chef chef locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants