[chef] Re: Chef behing nginx proxy

[Seth Falcon < >]

Hey there,

It's a bit hard to tell what exactly is going on from the logs you posted. Would it be possible for you to test a `knife cookbook upload` operation talking directly to your Chef server (not via the additional nginx proxy that you've configured). It's unclear to me whether you have a config issue causing bookshelf authn to fail or whether it is related to the addition of the extra proxy layer.

It might also help others help if you provided some client side output with `-l debug` and more of the server logs -- since it looks like it is the interaction with bookshelf that is a problem, would be interesting to see access log for the /bookshelf/organization-00000000000000000000000000000000/checksum-defbf24ccb9a0875f212a13a468a53b2 request (or similar) at your proxy nginx, chef server nginx.

On Fri, Aug 2, 2013 at 12:27 PM, Павел Сафронов < " target="_blank"> > wrote:

Hi all. Have an issue. When I run on a workstation with knife installed upload of cookbook I getting 403 from chef server. Here is the full log http://pastebin.com/Pd7q9xUn

And here is the piece of log on the server http://pastebin.com/jzN0tYKe

There is a user created on chef-server and such operations as "knife node list" is working fine. But when I'm trying to upload cookbook.

While I was writing this messages it's become clear, that the problem is reproducing only if chef is behind nginx proxy. Is there anyone, who has chef behind another nginx? How to get it working?

Here is my nginx configuration http://pastebin.com/Ej0tcQat

# sorry for my english