-
Notifications
You must be signed in to change notification settings - Fork 59
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
403 Forbidden #21
Comments
While this is a necessary, it's unfortunately not sufficient.
Thanks! |
I actually have the same issue, during converge the audit cookbook simply gives error 403 "Forbidden". My chef_gate log looks like this:
I also completely reinstalled compliance (still evaluating), but this did not change anything. Is there any log on the compliance server, that could help with this? |
@JTabel this is a stab in the dark, but does your node in question has a node_name != client_name? The described code path in chef_gate does this: given a signed request coming from a chef-client, it fetches the client's public key using |
I ended up cleansing the install, upgrading to the latest version of compliance, and re-running the integration steps and was able to get it to work. |
I am facing the same issue while running the audit cookbook. I am using the latest version of compliance, chef server and inspec. Please help. Logs below:
|
I was able to fix this by restarting the compliance core service.
|
Thanks all for the feedback. Please reopen the issue if it persists. |
I configured my Chef Server and Chef Compliance instances for integration. When I attempting to run an audit cookbook this is the error message I am getting:
Both servers are able to access each other over 443.
The text was updated successfully, but these errors were encountered: