Sourcegraph Repository Not Cloning or Not Updating

How to fix it

Try these in order — the most common fix is first.

1. 1. Refresh the repo

   Copy steps
   1. Open the repo, then Settings > Mirroring and review Last refreshed, queue position and last sync log
   2. Click Refresh Now
   3. If that fails, trigger updates with repository webhooks
   Did this fix it? Yes No

2. 2. Test the code host connection

   Copy steps
   1. On the code host configuration page click Test connection
   2. Errors like 'context deadline exceeded' or 'no such host' mean network or DNS must be fixed
   Did this fix it? Yes No

3. 3. Check logs and resources

   Copy steps
   1. Check gitserver logs and the worker container or pod logs
   2. Compare resources with the resource estimator; a small Postgres (driver: bad connection) or crash-looping worker blocks syncing, so raise memory
   Did this fix it? Yes No

Symptoms

Repositories show up but never clone, or stay stale after commits.

Why it happens

• Very large, empty, locked or corrupted repo
• Code host overloaded or permission problems
• Instance short on resources
• Code host unreachable from Sourcegraph

This guide also covers

• sourcegraph repository not cloning
• sourcegraph repo not updating
• sourcegraph repositories not showing up

Other Sourcegraph errors

• Sourcegraph Cody Free and Pro Discontinued: What Happened and What to Do
• Sourcegraph Cody Not Working in VS Code
• Sourcegraph Cody Sign-In Error: Authentication Failed or Signed Out on Restart
• Sourcegraph Cody Not Working in JetBrains (IntelliJ, Android Studio)
• Sourcegraph Cody Rate Limit or Usage Limit Reached
• Sourcegraph Search Not Finding Results
• Sourcegraph Search Slow or Timing Out (Zoekt Crash Loop)
• Sourcegraph Upgrade Failed: Dirty Database Migration Error