Troubleshooting
Common issues and how to resolve them.
Troubleshooting Guide
Find solutions to common issues you might encounter while using GitProductivity.
Connection Issues
GitHub Connection Failed
Symptoms: Unable to connect GitHub account or repositories not appearing.
Solutions:
- Check permissions: Ensure you have admin/maintain access to repositories
- Re-authorize: Disconnect and reconnect your GitHub account
- Check GitHub status: Verify GitHub is operational
- Browser issues: Try a different browser or clear cache
If you see "API rate limit exceeded", wait 15 minutes before retrying.
GitLab Connection Issues
Symptoms: Cannot connect to GitLab or repositories not syncing.
Solutions:
- Verify instance URL: Ensure correct GitLab URL (cloud or self-hosted)
- Check access token: Verify token has required scopes (
read_api,read_repository) - Test API access: Use the GitLab API directly to verify connectivity
- Firewall rules: Ensure GitLab instance is accessible from our servers
Repository Not Syncing
Symptoms: Connected repository shows no data or stale data.
Solutions:
- Check sync status: Look for last sync timestamp in dashboard
- Manual refresh: Click "Refresh" on the repository
- Verify commits: Ensure repository has commit history
- Check exclusions: Review any configured commit exclusions
Data Issues
Missing Developer Data
Symptoms: Developer appears in Git commits but not in analytics.
Solutions:
- Email matching: Ensure Git commit email matches team member email
- Check attribution: Review how commits are being attributed
- Invite to team: Developer must be added to your GitProductivity team
- Refresh data: Trigger a manual sync
Commits are matched by email address. Make sure developers use the same email in Git as in their GitProductivity account.
Incorrect Workday Estimates
Symptoms: Workday estimates seem too high or too low.
Solutions:
- Review exclusions: Check for excluded commits (merge, automated)
- Consider context: Large refactors may show as lower productivity
- Time range: Verify correct date range is selected
- Compare trends: Look at trends over time rather than absolute numbers
Data Not Updating
Symptoms: Dashboard shows old data despite new commits.
Solutions:
- Sync frequency: Check sync schedule in settings
- Manual sync: Trigger a manual repository sync
- Check webhook status: Verify webhooks are working (if applicable)
- API rate limits: Ensure not hitting rate limits
Authentication Issues
Can't Log In
Symptoms: Unable to access account.
Solutions:
- Password reset: Use "Forgot Password" to reset
- OAuth issues: Try signing in with different provider
- Browser issues: Clear cookies and try incognito mode
- Account exists: Verify account was created (check email)
API Key Not Working
Symptoms: API requests return 401 errors.
Solutions:
- Check key format: Ensure correct format (
gp_live_...) - Verify permissions: API key may lack required scopes
- Key not expired: Check key expiration in settings
- Generate new key: Create a new API key if needed
Performance Issues
Slow Dashboard
Symptoms: Dashboard loads slowly or times out.
Solutions:
- Large data sets: Try filtering by date range
- Browser cache: Clear browser cache
- Network issues: Check internet connection
- Browser extension: Try disabling extensions
Export Failing
Symptoms: Cannot export data or export times out.
Solutions:
- Reduce scope: Export smaller date ranges
- File format: Try different export format
- Peak hours: Try during off-peak hours
- Contact support: For large exports, contact support
Self-Hosted Issues
Docker Container Won't Start
Symptoms: Container fails to start or exits immediately.
Solutions:
- Check logs: Run
docker-compose logs app - Port conflicts: Ensure port 3000 is available
- Environment variables: Verify all required vars are set
- Resource limits: Ensure sufficient CPU/memory available
Database Connection Failed
Symptoms: App can't connect to database.
Solutions:
- Check DATABASE_URL: Verify connection string format
- Database running: Ensure PostgreSQL container is running
- Network: Verify containers can communicate
- Credentials: Check username/password in connection string
Getting More Help
If you're still experiencing issues:
- Search docs: Check our FAQ for more answers
- Contact support: Email support@gitproductivity.com
- Include details: Provide:
- Account email
- Steps to reproduce
- Error messages
- Screenshots if relevant
For fastest resolution, include as much detail as possible in your support request.