This guide helps you resolve common issues when using n8n-deploy.
Common Problems and Solutions
1. API Key Issues
Symptom: Unable to connect to n8n server
Solutions:
# Test API key
n8n-deploy apikey test my_key
# Verify with verbose output
n8n-deploy -v apikey test my_key
# List linked servers
n8n-deploy server list
If your workflow is linked to a server (
wf add --link-remote), the API key is used automatically.
2. Database Initialization Problems
Symptom: Database not found or cannot be created
Use the
--importflag to accept an existing database without prompting.
Solutions:
# Reinitialize database with import flag
n8n-deploy db init --import
# Check database status
n8n-deploy db status
# Specify custom data directory
n8n-deploy db init --data-dir ~/.n8n-deploy
3. Workflow Pull/Push Failures
Symptom: Cannot pull or push workflows
Read-only fields: n8n-deploy automatically strips read-only fields (
id,triggerCount,updatedAt,createdAt,versionId,staticData,tags,meta) before push operations.
Solutions:
# If workflow is linked to server, just use the name
n8n-deploy wf push my-workflow
# Override server if needed
n8n-deploy wf push my-workflow --remote staging
# Check linked server
n8n-deploy wf list
# For self-signed certificates, configure SSL once
n8n-deploy server ssl production --skip-verify
# Or use per-command flag
n8n-deploy wf push my-workflow --skip-ssl-verify
4. SSL Certificate Issues
Symptom: SSL verification errors with self-signed certificates
Solutions:
# Configure SSL setting per server (persistent)
n8n-deploy server ssl production --skip-verify
# Or use per-command flag (one-time)
n8n-deploy wf push my-workflow --skip-ssl-verify
# Re-enable verification
n8n-deploy server ssl production --verify
Skipping SSL verification reduces security. Use only for trusted internal servers with self-signed certificates.
5. Configuration Verification
Symptom: Unexpected configuration behavior
Solutions:
# Show current configuration
n8n-deploy env
# Show configuration in JSON
n8n-deploy env --json
# Check environment variables
echo $N8N_SERVER_URL
echo $N8N_DEPLOY_FLOWS_DIR
echo $N8N_DEPLOY_DATA_DIR
6. Folder Sync Issues
Symptom: Cannot sync folders or authentication fails
Solutions:
# Authenticate with n8n server first
n8n-deploy folder auth myserver --email user@example.com
# Or use browser cookie (DevTools ā Application ā Cookies ā n8n-auth)
n8n-deploy folder auth myserver --cookie "n8n-auth=..."
# List folders to verify connection
n8n-deploy folder list --remote myserver
# Use dry-run to preview changes
n8n-deploy folder sync --dry-run
Folder sync uses n8nās internal API (cookie-based auth), which is different from the public API (API key auth). You must authenticate separately for folder operations.
Debugging Techniques
Verbose Mode
n8n-deploy supports two levels of verbosity for debugging:
# Basic verbose - shows HTTP requests and operations
n8n-deploy -v wf push my-workflow
# Extended verbose - shows request/response details and timing
n8n-deploy -vv wf push my-workflow
# Verbose flag works at root or subcommand level
n8n-deploy -v wf push my-workflow # Root level
n8n-deploy wf -v push my-workflow # Subcommand level
n8n-deploy db -vv status # Works on any subcommand
Environment Debugging
# Set testing environment variable
N8N_DEPLOY_TESTING=1 n8n-deploy <command>
System Requirements Check
Verify Python Version
python --version # Should be 3.9+
Check Dependencies
pip list | grep -E "n8n-deploy|click|rich|pydantic|requests"
Getting Help
CLI Help
n8n-deploy --help
n8n-deploy wf --help
n8n-deploy wf push --help
n8n-deploy server ssl --help
Online Resources
Always use the latest version of n8n-deploy for bug fixes and new features.
Known Limitations
- Requires API key for server operations
- Folder sync requires separate cookie-based authentication
- Supports SQLite backend only
Related Guides
Reporting Issues
- Check existing GitHub issues
- Collect relevant logs and configuration details
- Create a new issue with:
- Detailed description
- Steps to reproduce
- Python and n8n-deploy versions
- System information