Common issues and solutions for SafeDep Cloud authentication and usage.
Authentication Errors
User Not Found
Error Message:
ERRO[0001] Failed to execute whoami: rpc error: code = Unauthenticated desc = unauthenticated: Token auth failed: No user: record not found
Cause: The user account is not registered with SafeDep Cloud.
Solution:
Verify Registration
Ensure you’ve completed the full onboarding process including tenant creation
Check Email Verification
Verify your email address if required during registration
Tenant Not Found
Error Message:
ERRO[0001] Failed to execute query: rpc error: code = Unknown desc = failed to resolve tenant: record not found
Cause: The tenant is not properly configured in vet, or the tenant domain is incorrect.
Solution:
API and Connectivity Issues
Rate Limiting
Error Message:
ERRO[0001] Request failed: rpc error: code = ResourceExhausted desc = rate limit exceeded
Solution:
- Wait for the rate limit window to reset (typically 1 hour)
- Reduce the frequency of API calls
- Contact support for increased rate limits if needed
- Use batch operations where possible
Network Connectivity
Error Message:
ERRO[0001] Failed to connect: dial tcp: lookup api.safedep.io: no such host
Solution:
- Check internet connectivity
- Verify DNS resolution for
api.safedep.io
- Check firewall settings and proxy configuration
- Ensure HTTPS traffic on port 443 is allowed
SSL/TLS Issues
Error Message:
ERRO[0001] Failed to connect: x509: certificate verify failed
Solution:
- Update your system’s CA certificates
- Check system clock accuracy
- Verify no proxy is interfering with SSL
- Try updating vet to the latest version
Configuration Issues
Invalid API Key
Error Message:
ERRO[0001] Authentication failed: invalid API key
Solution:
Generate New Key
Create a new API key in your SafeDep Cloud tenant settings
Update Configuration
export SAFEDEP_API_KEY=your-new-api-key
vet auth configure --tenant your-tenant
Verify Permissions
Ensure the API key has the necessary permissions for your operations
Expired Tokens
Error Message:
ERRO[0001] Token expired: please re-authenticate
Solution:
# Re-authenticate with device flow
vet cloud login --tenant your-tenant
# Verify authentication
vet cloud whoami
Configuration File Issues
Error Message:
ERRO[0001] Failed to load config: permission denied
Solution:
- Check file permissions on vet configuration directory
- Ensure user has write access to
~/.config/vet/
- Try running with appropriate permissions
- Clear and recreate configuration if corrupted
Data Sync Issues
Sync Failures
Error Message:
WARN[0001] Failed to sync data to cloud: project not found
Solution:
- Verify project name and version are correctly specified
- Check that tenant has permissions for data sync
- Ensure API key includes sync permissions
- Retry with proper project identification
Missing Data
Issue: Scanned data doesn’t appear in SafeDep Cloud
Solution:
Check Sync Flags
Ensure --report-sync
is included in your scan command
Verify Project Info
vet scan -D . --report-sync \
--report-sync-project "your-project" \
--report-sync-project-version "main"
Query Failures
Error Message:
ERRO[0001] Query execution failed: syntax error
Solution:
- Verify SQL syntax is correct
- Check table and column names in schema
- Use
vet cloud query schema
to view available tables
- Ensure proper quoting for identifiers with special characters
GitHub Actions Issues
Secret Configuration
Issue: GitHub Action fails with authentication errors
Solution:
Check Secrets
Verify these secrets are set in your repository:
SAFEDEP_CLOUD_API_KEY
SAFEDEP_CLOUD_TENANT_DOMAIN
Update Workflow
- name: Run vet
uses: safedep/vet-action@v1
with:
cloud: true
cloud-key: ${{ secrets.SAFEDEP_CLOUD_API_KEY }}
cloud-tenant: ${{ secrets.SAFEDEP_CLOUD_TENANT_DOMAIN }}
Action Version Issues
Issue: Action fails with “unknown parameter” errors
Solution:
- Update to the latest version of vet-action
- Check the action documentation for parameter changes
- Verify you’re using supported parameters for your action version
Slow Scans
Issue: Scans take too long to complete
Solution:
- Use path exclusions to skip irrelevant directories
- Scan specific manifest files instead of entire directories
- Adjust timeout settings for malware analysis
- Use JSON dump workflow for repeated analysis
Memory Issues
Issue: vet runs out of memory during scans
Solution:
- Scan smaller directory trees
- Use exclusions to skip large dependency directories
- Increase available memory in CI/CD environments
- Process large monorepos in batches
Getting Additional Help
Common Debugging Commands
Check Authentication Status
Verify API Configuration
Test Cloud Connectivity
vet cloud query execute --sql "SELECT 1"
Clear Configuration
vet auth logout
rm -rf ~/.config/vet/
Re-authenticate
vet cloud login --tenant your-tenant
View Detailed Logs
vet --log-level debug scan -D . --report-sync
Responses are generated using AI and may contain mistakes.