Skip to main content

Common Issues

Quick reference for common Git sync problems:
Symptoms:
  • “Permission denied (publickey)”
  • “Authentication failed”
  • “Could not read from remote repository”
Solutions:

For SSH:

For HTTPS:

Verify Authentication:

  • Check SSH key is added to Git service
  • Verify token has correct permissions
  • Ensure token hasn’t expired
Symptoms:
  • “Updates were rejected”
  • “Failed to push some refs”
  • “Non-fast-forward”
Cause: Remote has changes you don’t have locallySolution:
In Auk:
  1. Click “Sync Now” to pull changes
  2. Resolve any conflicts
  3. Sync again to push
Symptoms:
  • “Automatic merge failed”
  • “CONFLICT (content)”
  • Sync paused with conflict warning
Solution: See Conflict Resolution guideQuick steps:
  1. Open conflict resolution UI
  2. Choose resolution strategy
  3. Resolve conflicts
  4. Complete sync
Symptoms:
  • “Repository not found”
  • “Could not resolve host”
  • 404 error
Solutions:
  • Verify repository URL is correct
  • Check you have access to repository
  • Ensure repository exists
  • Try cloning manually to test:
Symptoms:
  • “Connection timed out”
  • “Failed to connect”
  • Sync hangs indefinitely
Solutions:
  • Check internet connection
  • Verify firewall isn’t blocking Git
  • Try different network
  • Increase timeout in settings:
Symptoms:
  • “You are in ‘detached HEAD’ state”
  • Commits not appearing on branch
Solution:
Symptoms:
  • “File too large”
  • Push fails with size error
  • Slow sync performance
Solutions:
  • Remove large files from Git:
  • Use Git LFS for large files:
  • Split large collections into smaller files
Symptoms:
  • Sync shows “In progress” indefinitely
  • Cannot cancel sync
  • Auk becomes unresponsive
Solutions:
  1. Wait 5 minutes for timeout
  2. Force quit Auk if needed
  3. Restart Auk
  4. Check workspace Git status:
  1. Reset if needed:

Diagnostic Commands

Check Git Status

Test Connectivity

View Sync Logs

Recovery Procedures

Reset to Remote State

If local state is corrupted, reset to remote:
This will discard all local changes. Backup first if needed.

Recover Lost Commits

If commits are lost:

Fix Corrupted Repository

If Git repository is corrupted:

Performance Issues

Slow Sync

If sync is slow:
1

Check Network Speed

2

Enable Compression

3

Use Shallow Clone

For large repositories:
4

Reduce Sync Frequency

High CPU Usage

If Git sync uses too much CPU:

Platform-Specific Issues

macOS

Symptoms: Repeated password promptsSolution:
Symptoms: Git not found or outdatedSolution:

Windows

Symptoms: Files show as modified but no changesSolution:
Symptoms: “Filename too long” errorSolution:

Linux

Symptoms: Cannot write to workspace directorySolution:
Symptoms: SSH key not foundSolution:

Error Messages

Common Error Messages and Solutions

Getting Help

Enable Debug Logging

Collect Diagnostic Information

When reporting issues, include:
  1. Auk Version
    • Help → About Auk
  2. Git Version
  3. Operating System
    • macOS: System Preferences → About
    • Windows: Settings → System → About
    • Linux: uname -a
  4. Error Logs
    • Copy from Auk logs directory
  5. Git Status

Contact Support

Prevention Tips

Backup workspaces regularly:
Test Git sync with a test workspace first:
  1. Create test workspace
  2. Configure Git sync
  3. Test sync operations
  4. Verify everything works
  5. Apply to production workspaces
Regularly check sync status:
  • Review sync history
  • Check for errors in logs
  • Verify remote repository is updated
Use latest Git version:

Next Steps

Git Sync Setup

Set up Git synchronization

Conflict Resolution

Learn conflict resolution

Best Practices

Git collaboration best practices

Support

Get additional help