GitHub Troubleshooting

Solutions for common problems with Vidoc’s GitHub integration.

​

Scans Not Triggering

​

Check Integration Status

1. Go to Settings → Integrations
2. Verify GitHub shows as “Connected”
3. If disconnected, click “Connect GitHub”

​

Verify Repository Settings

1. Go to Repositories
2. Click settings (gear) on the repository
3. Ensure “Auto Scan” is enabled

​

Check Webhooks

1. Go to GitHub → Repository → Settings → Webhooks
2. Find the Vidoc webhook
3. Check “Recent Deliveries”
4. Look for failed deliveries (red X)

Common webhook issues:

• 401 Unauthorized - Reconnect GitHub integration
• 404 Not Found - Repository may not be configured
• 500 Server Error - Temporary issue, should auto-retry

​

Verify PR Settings

If PR scans aren’t triggering:

1. Check if the PR is a draft (drafts may be skipped)
2. Verify the target branch is monitored
3. Check if the repository has auto-scan enabled

​

Repository Not Appearing

​

Check Organization Access

1. Go to GitHub → Settings → Applications → Vidoc
2. Click “Configure”
3. Verify the organization is listed
4. Add any missing repositories

​

Request Organization Approval

If you don’t have admin access:

1. Ask an organization admin to approve Vidoc
2. Go to GitHub → Organization → Settings → Third-party access
3. Approve the Vidoc application

​

Refresh Repository List

1. In Vidoc, go to Repositories
2. Click “Add Repository”
3. Click “Refresh” to sync with GitHub

​

PR Comments Not Posting

​

Check Permissions

1. Go to GitHub → Settings → Applications → Vidoc
2. Verify write access to pull requests
3. Re-authorize if needed

​

Check Comment Settings

1. Go to Vidoc Settings → Integrations → GitHub
2. Ensure “Post PR Comments” is enabled
3. Check the minimum severity setting

​

Verify Issue Existence

Comments are only posted if issues are found:

1. Check the scan completed successfully
2. Review issues in the Vidoc dashboard
3. Verify issues meet the minimum severity threshold

​

Authentication Errors

​

”Bad Credentials” Error

1. Go to Settings → Integrations
2. Click “Disconnect” next to GitHub
3. Click “Connect GitHub”
4. Re-authorize the application

​

”Resource Not Accessible”

The token may have expired or lost permissions:

1. Disconnect GitHub in Vidoc
2. In GitHub, revoke Vidoc’s access (Settings → Applications)
3. Reconnect from Vidoc

​

Scan Failures

​

”Repository Not Found”

1. Verify the repository exists
2. Check Vidoc has access (not removed in GitHub)
3. Refresh the repository list

​

”Branch Not Found”

1. Check the branch name is correct
2. Verify the branch exists in GitHub
3. Push the branch if it’s local only

​

”Clone Failed”

1. Repository may be too large
2. Check for submodules requiring separate auth
3. Try scanning a specific branch

​

Rate Limiting

​

GitHub API Rate Limits

If you see rate limit errors:

1. Wait for the rate limit to reset (usually 1 hour)
2. Reduce the number of concurrent scans
3. Contact support for enterprise rate limits

​

Vidoc Rate Limits

1. Check if multiple scans are running
2. Avoid triggering scans on every commit
3. Use branch filters to reduce scan frequency

​

Sync Issues

​

Issues Not Syncing

If issues in Vidoc don’t match GitHub:

1. Refresh the browser
2. Wait for scan to complete
3. Check for sync errors in scan history

​

Stale Data

1. Click “Sync” on the repository
2. Wait for re-scan to complete
3. Clear browser cache if needed

​

Quick Fixes

​

Getting Help

If issues persist:

1. Check the Vidoc Status Page for outages
2. Email support at [email protected]
3. Include:
   • Repository URL
   • Error messages
   • Steps to reproduce

​

Related Pages