Skip to content

Troubleshooting

  1. Verify GITHUB_TOKEN is set in the Admin UI under the GitHub connector’s Credentials tab
  2. Navigate to the Connectors page and toggle GitHub to enabled
  3. Check the Health page for connection errors
  4. If the token was added after startup, click Test Connection on the connector card — no restart is required
  1. Verify Sourcebot is running and accessible from FluidRAG
  2. Check that SOURCEBOT_HOST and SOURCEBOT_API_KEY are configured in the GitHub connector’s Credentials tab
  3. Verify your repositories are indexed in Sourcebot
  4. Try a broader search query — Sourcebot uses regex matching
  1. Check the GitHub API rate limit status in server logs
  2. Reduce github_max_search_concurrent (default: 2) to limit concurrent requests
  3. Increase github_search_min_delay to space out requests
  4. If using a fine-grained PAT, verify it has sufficient rate limit allocation
  1. Verify GITHUB_TOKEN has the repo scope
  2. Confirm the github_org setting matches your actual organization name (or leave it blank for auto-detection)
  3. Check that repos are not being excluded by ignore patterns
  4. Ensure the selected repos contain supported file types (.md, .txt, .mdx, .rst, .adoc)