Skip to main content
Docs / Advanced / Troubleshooting

Troubleshooting

Solutions to common PrivStack issues.

App Won’t Start

Windows

  1. Check if another instance is running (system tray)
  2. Try running as administrator
  3. Check Windows Event Viewer for errors
  4. Reinstall if needed

macOS

  1. Check Activity Monitor for running instances
  2. Try: xattr -cr /Applications/PrivStack.app
  3. Check Console.app for errors
  4. Reinstall if needed

Linux

  1. Run from terminal to see errors
  2. Check permissions on data folder
  3. Ensure required libs are installed

Sync Issues

Devices Not Connecting

  1. Ensure both devices are on the same network (for local sync)
  2. Check that sync is enabled on both devices
  3. Verify device IDs match
  4. Check firewall settings (port 21000)

Sync Stuck

  1. Go to Settings > Sync
  2. Click Force Sync
  3. If still stuck, click Reset Sync State

Cloud Sync Not Working

  1. Check internet connection
  2. Re-authenticate with cloud provider
  3. Check available storage space

Performance Issues

App Running Slow

  1. Check how many items you have (very large databases may be slower)
  2. Close unused modules
  3. Restart the app
  4. Check system resources (RAM, CPU)

Large Files Slow

Encrypted file operations take time. For many large files:

  • Wait for operations to complete
  • Consider splitting into smaller batches

Data Issues

Missing Data

  1. Check if you’re on the right device
  2. Check sync status — data may not have synced yet
  3. Check filters — items may be filtered out
  4. Look in Trash (deleted items)

Corrupted Data

  1. Go to Settings > Backup > Restore
  2. Choose a recent backup
  3. Contact support if backups are also affected

Log Files

Find logs for support:

  • Windows: %APPDATA%\\PrivStack\\logs
  • macOS: ~/Library/Logs/PrivStack
  • Linux: ~/.local/share/PrivStack/logs

Getting Help

  1. Check this documentation
  2. Search our FAQ
  3. Contact support with:
    • Your platform (Windows/macOS/Linux)
    • PrivStack version
    • Description of the issue
    • Relevant log files (no sensitive data)