Troubleshoot a Code Manager webhook

To troubleshoot your webhook, you can review your Git host's logs. Refer to your Git host's documentation for information about their logs and their suggestions for resolving common webhook issues.

Deployments triggered by a webhook in Stash/Bitbucket, GitLab, or GitHub are governed by authentication and hit the POST /v1/webhook endpoint for each service type.

If you are using a GitLab version older than 8.5.0, Code Manager's webhook authentication doesn't work because of the length of the authentication token. To use the webhook with GitLab, either disable authentication or update GitLab. If you disable webhook authentication, it is disabled only for the POST /v1/webhook endpoint. It is not possible to disable authentication for the POST /v1/deploys or GET /v1/deploys/status endpoints.

To troubleshoot webhook issues, follow the instructions for Triggering Code Manager with a webhook while monitoring the Puppet Server log. To monitor the logs, open a separate terminal window and run:

tail -f /var/log/puppetlabs/puppetserver/puppetserver.log

Watch the log closely for errors and information messages when you trigger the webhook. The puppetserver.log file is the only location these errors appear. If you cannot determine the problem with your webhook this way, manually deploy to the POST /v1/deploys endpoint while monitoring the console-services.log file, as described in Troubleshooting Code Manager.

For other Code Manager issues, refer to Troubleshooting Code Manager.