Troubleshooting GitHub Sync Failure

1. Sync Failed with Error- 404 Not Found

This error occurs when the Organization Id provided in the Zilla application instance configuration is incorrect. To get the correct Organization Id, navigate to your GitHub account and click on your profile image located in the upper-right corner. Select Your organizations from the popup menu.

You will be redirected to Organizations page. There you can find all organizations associated with your GitHub account.

The name(s) shown here are the usernames of the organization. For example, if we want to use Zilla Test Organization then the Organization Id to specify in the Zilla application instance configuration will be Zilla-Test-Organization.

2. Error-HTTP Error Response: 401 Unauthorized with error response

{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest"}

Authenticating with invalid credentials will return 401 Unauthorized.

Please refer to Github.

3. HTTP Error Response: 403 Forbidden - Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization.

Root cause: This error occurs when you have enabled SAML enforcement on GitHub. The resources are protected by organization SAML enforcement and you haven’t granted your OAuth token access to that organization.

Solution: To resolve this issue, Please refer to Authorizing a personal access token for use with SAML single sign-on - GitHub Enterprise Cloud Docs.

4. HTTP Error Response: 422 Unprocessable Entity - Only owners can use this filter.

Root cause: This error occurs when the OAuth app is created from an organization’s non-owner account. There are some GitHub APIs which requires owner access, For example, two-factor-auth filter in members API. That’s why It throws 422 error when the OAuth app you created is from organization’s non-owner account.

Solution: To resolve this issue, create new OAuth app and authenticate it from organization’s owner account.

Please refer to Github .

5. HTTP Error Response: 403 Forbidden with error response - You must be an owner of this organization to list outside collaborators.

Root cause: This error occurs when the OAuth app is created from an organization’s non-owner account. There are some GitHub APIs which requires owner access, For example, outside collaborators API. That’s why It throws 403 error when you created OAuth app and authenticated it from organization’s non-owner account.

Solution: To resolve this issue, create new OAuth app and authenticate it from organization’s owner account.

Please refer to Github .

Still having trouble? Please contact support@zillasecurity.com.