SeedCross
Cross-seed torrents across multiple BitTorrent clients
SeedCross - Cross-Seed Automation
SeedCross is a web application for cross-seeding torrents across Deluge, qBittorrent, and Transmission. It’s a fork of Cross-Seed-AutoDL, providing an intuitive interface for automated torrent matching and management.
What is SeedCross?
SeedCross helps you maximize your seeding ratio by automatically finding and cross-seeding torrents across different trackers:
Multi-Client Support
Works with Deluge, qBittorrent, and Transmission seamlessly
Automated Matching
Automatically finds matching torrents across trackers
Web Interface
Easy-to-use Django-based web dashboard
History Tracking
Keep track of all cross-seeded torrents
Settings Management
Configure tracker connections and preferences
Ratio Optimization
Maximize upload credit across multiple trackers
You must have at least one supported BitTorrent client (Deluge, qBittorrent, or Transmission) installed and configured before using SeedCross.
Supported Integrations
BitTorrent Clients
Tracker Types
Technology Stack
Installation
Install from the Dashboard
Open App Dashboard → Package Management (/dashboard?mode=packages), find SeedCross in the catalog (browse the Automation category or search), and click Install. The dashboard streams the install log live and SeedCross appears in your Application Control panel when it finishes. Reinstall, Update, and Remove are available from the same panel.
What you see is gated by your account: admins manage any user’s apps; regular users manage their own. See App Management for the full flow.
The installer sets up an isolated Python 3.11 virtual environment, clones the latest SeedCross release, configures the Django app with a SQLite database, creates the admin superuser from your QuickBox credentials, and registers a systemd service behind the nginx reverse proxy. Each user gets their own isolated instance with separate configuration and database.
SeedCross needs a supported BitTorrent client (Deluge, qBittorrent, or Transmission) installed and configured before it can match and cross-seed torrents.
Install from the CLI (automation)
The CLI runs the same scripts as the Dashboard and is suited to automation and scripting:
qb install seedcross -u username
qb reinstall seedcross -u username
qb update seedcross -u username
qb remove seedcross -u usernameFull flag reference: CLI Reference.
Features
SeedCross on QuickBox Pro includes several enhanced features:
Isolated Environment
Runs in a dedicated Python virtual environment with per-user isolation and security
Auto-Restart
Systemd service with automatic restart on failure for reliable operation
Nginx Reverse Proxy
Integrated with QuickBox's nginx configuration with proper URL rewriting and CSRF handling
Automatic Backups
Database and configuration automatically backed up during installation and updates
SSO Integration
Superuser account automatically created using your QuickBox credentials
WAL Mode Database
SQLite configured with Write-Ahead Logging for improved performance and reliability
Service Management
SeedCross runs as a systemd service for reliable operation:
Check Service Status
systemctl status seedcross@usernameRestart Service
systemctl restart seedcross@usernameStop Service
systemctl stop seedcross@usernameView Live Logs
journalctl -u seedcross@username -fThe SeedCross service is configured to automatically restart on failure (with a 5-second delay), ensuring continuous operation.
Accessing SeedCross
After installation, access the dashboard at:
https://your-server-ip/username/seedcross/Or via your QuickBox Pro dashboard navigation, or the Service Control Panel on the main QuickBox dashboard.
Default Credentials
SeedCross uses your QuickBox Pro credentials:
- Username: Your QuickBox username
- Password: Your QuickBox password
- Email: Your registered email address
Dashboard Features
The SeedCross interface provides:
- Cross-Seed List - View and manage cross-seeded torrents
- History - Track all cross-seeding activity
- Settings - Configure tracker connections and client settings
- Admin Panel - Django admin interface for advanced configuration
Configuration
Installation Paths
Default Port
SeedCross runs on port 8019 by default (auto-assigned if unavailable). The service is accessed via nginx reverse proxy at /username/seedcross/.
Troubleshooting
Common Issues
SeedCross not loading:
# Check if service is running
systemctl status seedcross@username
# Restart the service
systemctl restart seedcross@username
# Check logs for errors
journalctl -u seedcross@username -n 50Permission errors:
# Fix ownership
chown -R username:username /opt/username/SeedCross
chown -R username:username /opt/username/lib/python/SeedCross
# Reinstall if issues persist
qb reinstall seedcross -u usernameDatabase issues:
# Check database integrity
sqlite3 /opt/username/SeedCross/db/db.sqlite3 "PRAGMA integrity_check;"
# Run migrations
/opt/username/lib/python/SeedCross/.venv/bin/python3 /opt/username/SeedCross/manage.py migrateNginx 502 errors:
# Test nginx configuration
nginx -t
# Reload nginx
systemctl reload nginx
# Check if SeedCross service is running
systemctl status seedcross@usernameBest Practices
Do
- Install your preferred BitTorrent client before SeedCross
- Configure tracker API credentials securely in the web interface
- Review cross-seed history regularly to verify successful operations
- Use the same download paths across trackers for efficient matching
- Keep SeedCross updated for latest tracker compatibility
- Monitor your ratio requirements and adjust cross-seeding accordingly
Don't
- Don't cross-seed content that violates tracker rules
- Don't share your tracker API keys or passkeys
- Don't run multiple SeedCross instances pointing to the same client
- Don't ignore database integrity warnings
- Don't forget to verify torrent hashes match before cross-seeding
- Don't cross-seed without understanding tracker hit-and-run policies
Additional Resources
Related Applications
BitTorrent Clients
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.