Troubleshooting¶

Having issues with qBitrr? This section provides solutions to common problems and debugging techniques.

Quick Links¶

• Common Issues - Frequently encountered problems and solutions
• Docker Issues - Docker-specific troubleshooting
• FAQ - Frequently asked questions

Common Problems¶

Connection Issues¶

Can't connect to qBittorrent or Arr instances?

Quick Fixes: - Verify all services are running - Check host/port configuration - Verify API keys are correct - Test connections from qBitrr container/host

Detailed Guide: Connection Problems

Import Issues¶

Downloads complete but don't import to Arr?

Quick Fixes: - Check path mappings - Verify file permissions - Enable instant import - Check Arr logs

Detailed Guide: Import Failures

Docker Networking¶

Problems with Docker container communication?

Quick Fixes: - Use container names instead of localhost - Check Docker network configuration - Verify port mappings - Test inter-container connectivity

Detailed Guide: Docker Networking

Stalled Torrents¶

Torrents stuck and not completing?

Quick Fixes: - Check torrent health monitoring is enabled - Verify tracker connectivity - Check available disk space - Review torrent client logs

Detailed Guide: Stalled Torrents

Debugging Steps¶

1. Check Logs¶

qBitrr logs provide detailed information about operations:

# View logs
docker logs qbitrr

# Follow logs in real-time
docker logs -f qbitrr

# Save logs to file
docker logs qbitrr > qbitrr.log 2>&1

# View logs
journalctl -u qbitrr

# Follow logs
journalctl -u qbitrr -f

# Recent logs
journalctl -u qbitrr -n 100

# Logs are in ~/config/logs/
tail -f ~/config/logs/Main.log

2. Verify Configuration¶

Check your configuration file for errors:

# Native
cat ~/config/config.toml

# Docker
docker exec qbitrr cat /config/config.toml

Common configuration mistakes: - Wrong API keys - Incorrect host/port - Missing required fields - Typos in service names

3. Test Connectivity¶

Verify services are accessible:

# Test qBittorrent
curl http://localhost:8080

# Test Radarr
curl http://localhost:7878/api/v3/system/status \
  -H "X-Api-Key: your-api-key"

# Test Sonarr
curl http://localhost:8989/api/v3/system/status \
  -H "X-Api-Key: your-api-key"

4. Check Service Status¶

Ensure all required services are running:

docker ps | grep -E "qbittorrent|radarr|sonarr|qbitrr"

systemctl status qbittorrent radarr sonarr qbitrr

5. Review Permissions¶

File permission issues can cause imports to fail:

# Check ownership
ls -la /path/to/downloads

# Check qBitrr can read files
docker exec qbitrr ls -la /downloads

Getting Help¶

Before Asking for Help¶

1. Check the documentation:
2. Common Issues
3. Docker Troubleshooting

4. FAQ

5. Gather information:

6. qBitrr version
7. Installation method (Docker/pip/binary)
8. Arr versions
9. Relevant log excerpts

10. Configuration (redact API keys!)

11. Search existing issues:

12. GitHub Issues
13. Discussions

Where to Get Help¶

• GitHub Issues - For bugs and feature requests
• GitHub Discussions - For questions and community support
• Discord - Real-time help from the community

Creating a Good Issue Report¶

Include:

1. Environment:

   qBitrr version: 5.5.5
   Installation: Docker
   OS: Ubuntu 22.04
   qBittorrent: 4.6.0
   Radarr: 5.0.0
   

2. Problem Description:

3. What you expected to happen
4. What actually happened

5. Steps to reproduce

6. Relevant Logs:

   [Include relevant log excerpts]
   

7. Configuration:

   # Redact sensitive information!
   [Settings.Qbittorrent]
   Host = "http://qbittorrent"
   Port = 8080
   Username = "admin"
   Password = "REDACTED"
   

Debug Mode¶

Enable debug logging for more detailed information:

[Settings]
LogLevel = "DEBUG"

Warning: Debug logs can be very verbose and may impact performance. Only enable when troubleshooting.

Performance Issues¶

High CPU Usage¶

Symptoms: qBitrr consuming excessive CPU

Common Causes:

1. Too frequent torrent checks:

   [Settings]
   CheckInterval = 300  # Increase interval (default: 60)
   

2. Too many concurrent health checks:

   [Settings]
   MaxConcurrentChecks = 5  # Reduce concurrent operations
   

3. Large torrent counts:

4. Limit categories to only what qBitrr needs to manage

5. Use category filtering in qBittorrent

6. FFprobe validation on large files:

   [Settings]
   EnableFFprobe = false  # Temporarily disable to test
   

Monitor Resource Usage:

# Docker
docker stats qbitrr --no-stream

# Native
ps aux | grep qbitrr
top -p $(pidof qbitrr)

High Memory Usage¶

Symptoms: qBitrr using excessive RAM

Solutions:

1. Reduce log retention:

   [Settings]
   LogRetentionDays = 7  # Reduce from default 30
   

2. Limit torrent history:

   [Settings]
   TorrentHistoryDays = 30  # Clean old entries
   

3. Vacuum database regularly:

   sqlite3 ~/config/qBitrr.db "VACUUM;"
   

4. Restart qBitrr periodically:

5. Set up a cron job or systemd timer for weekly restarts

Slow WebUI Response¶

Symptoms: WebUI is slow or unresponsive

Solutions:

1. Reduce data fetching:
2. Limit log entries displayed (50-100 instead of 500)
3. Use filters to reduce table sizes

4. Disable auto-refresh when not actively monitoring

5. Check API response times:

   time curl http://localhost:6969/api/health
   

6. Database optimization:

   # Check database size
   ls -lh ~/config/qBitrr.db
   
   # If > 100MB, vacuum
   sqlite3 ~/config/qBitrr.db "VACUUM;"
   

7. Browser performance:

8. Clear browser cache
9. Disable unnecessary browser extensions
10. Try a different browser

Slow Import Processing¶

Symptoms: Torrents complete but imports take a long time

Solutions:

1. Enable instant imports:

   [[Radarr]]
   InstantImport = true  # Trigger immediate imports
   

2. Optimize Arr refresh intervals:

   [[Radarr]]
   RefreshDownloadsTimer = 1  # Check every 1 minute
   

3. Check Arr instance performance:

4. Review Arr logs for slow operations
5. Optimize Arr database

6. Reduce Arr's own refresh intervals

7. Path mapping issues:

8. Verify paths are consistent across all services
9. See Path Mapping Guide

Network Issues¶

Timeout Errors¶

Symptoms: "Connection timeout" errors in logs

Solutions:

1. Increase timeout values:

   [Settings]
   ConnectionTimeout = 60  # Increase from default 30
   ReadTimeout = 120       # Increase from default 60
   

2. Check network connectivity:

   # Test from qBitrr container/host
   ping qbittorrent
   ping radarr
   curl -v http://qbittorrent:8080
   

3. Verify services are responding:

   # Check service health
   docker exec qbitrr curl http://qbittorrent:8080/api/v2/app/version
   

4. Review firewall rules:

   # Ubuntu/Debian
   sudo ufw status
   
   # Check if ports are open
   sudo netstat -tulpn | grep 8080
   

DNS Resolution Issues¶

Symptoms: "Name or service not known" errors

Solutions:

1. Use IP addresses instead of hostnames:

   [Settings.Qbittorrent]
   Host = "http://192.168.1.100"  # Instead of hostname
   

2. Check DNS configuration (Docker):

   services:
     qbitrr:
       dns:
         - 8.8.8.8
         - 1.1.1.1
   

3. Verify container can resolve names:

   docker exec qbitrr nslookup radarr
   docker exec qbitrr ping -c 3 radarr
   

4. Use Docker network aliases:

   services:
     radarr:
       networks:
         mediastack:
           aliases:
             - radarr
   

Connection Refused¶

Symptoms: "Connection refused" when trying to reach services

Solutions:

1. Verify service is listening:

   docker ps | grep radarr  # Check if running
   netstat -tulpn | grep 7878  # Check if listening
   

2. Check bind address:

3. Services should bind to 0.0.0.0 not 127.0.0.1 for Docker

4. Verify port mappings (Docker):

   docker port qbitrr
   docker port radarr
   

5. Test from correct network namespace:

   # From within qBitrr container
   docker exec qbitrr curl http://radarr:7878
   

Configuration Issues¶

Invalid TOML Syntax¶

Symptoms: qBitrr won't start, "Invalid configuration" error

Common Mistakes:

1. Missing quotes:

   # ❌ Wrong
   Host = http://localhost
   
   # ✅ Correct
   Host = "http://localhost"
   

2. Wrong quotes:

   # ❌ Wrong (single quotes don't work for all values)
   APIKey = 'abc123'
   
   # ✅ Correct
   APIKey = "abc123"
   

3. Unclosed brackets:

   # ❌ Wrong
   [[Radarr]
   Name = "Movies"
   
   # ✅ Correct
   [[Radarr]]
   Name = "Movies"
   

4. Duplicate sections:

   # ❌ Wrong (duplicate [Settings])
   [Settings]
   LogLevel = "INFO"
   
   [Settings]
   CheckInterval = 60
   
   # ✅ Correct
   [Settings]
   LogLevel = "INFO"
   CheckInterval = 60
   

Validate TOML:

# Python validation
python3 -c "import toml; toml.load(open('config.toml'))"

# Online validator
# Copy config to https://www.toml-lint.com/

Missing Required Fields¶

Symptoms: "Config key 'X' requires a value" error

Solutions:

Check these required fields are set:

[Settings.Qbittorrent]
Host = "http://localhost:8080"  # REQUIRED
# Username and Password (if qBit has auth enabled)

[[Radarr]]
URI = "http://localhost:7878"   # REQUIRED
APIKey = "your-api-key"         # REQUIRED
Category = "radarr"             # REQUIRED (must match qBit download client)

Environment Variable Overrides Not Working¶

Symptoms: Environment variables don't override config file

Solutions:

1. Check variable naming:

   # Correct format: QBITRR_SECTION__KEY
   export QBITRR_SETTINGS__LOGLEVEL=DEBUG
   
   # For array items:
   export QBITRR_RADARR__0__URI=http://radarr:7878
   

2. Verify variables are passed to container:

   docker exec qbitrr env | grep QBITRR
   

3. Check Docker Compose syntax:

   environment:
     - QBITRR_SETTINGS__LOGLEVEL=DEBUG
     # or
     QBITRR_SETTINGS__LOGLEVEL: DEBUG
   

Automated Search Issues¶

Searches Not Triggering¶

Symptoms: qBitrr doesn't search for missing content

Solutions:

1. Enable search functionality:

   [[Radarr]]
   [Radarr.EntrySearch]
   SearchMissing = true
   

2. Check search intervals:

   SearchRequestsEvery = 300  # Search every 5 minutes
   

3. Verify Arr has indexers:

4. Radarr/Sonarr/Lidarr must have working indexers configured

5. Test indexers in Arr UI

6. Review search logs:

   grep -i "search" ~/config/logs/Radarr-Movies.log
   

7. Check for rate limiting:

8. Some indexers rate limit searches
9. Review indexer API limits

Too Many Searches¶

Symptoms: Overwhelming indexers with searches, rate limited

Solutions:

1. Increase search interval:

   SearchRequestsEvery = 600  # 10 minutes instead of 5
   

2. Reduce search limit:

   SearchLimit = 3  # Fewer concurrent searches
   

3. Disable upgrade searches temporarily:

   DoUpgradeSearch = false
   QualityUnmetSearch = false
   

4. Monitor indexer stats:

5. Check Prowlarr for indexer statistics
6. Review API hit counts

Seeding & Tracker Issues¶

Torrents Removed Too Early¶

Symptoms: Torrents deleted before reaching seeding goals

Solutions:

1. Adjust seeding limits:

   [[Radarr]]
   [Radarr.Torrent.SeedingMode]
   MaxUploadRatio = 2.0      # Increase ratio
   MaxSeedingTime = 1209600  # 14 days in seconds
   RemoveTorrent = 4         # Remove only when BOTH met
   

2. Check tracker-specific rules:

   [[Radarr.Torrent.Trackers]]
   Name = "PrivateTracker"
   URI = "https://tracker.example.com"
   MaxUploadRatio = 3.0      # Higher for private trackers
   

3. Disable automatic removal:

   RemoveTorrent = -1  # Never auto-remove
   

Dead Tracker Detection Issues¶

Symptoms: Torrents marked as failed due to temporary tracker issues

Solutions:

1. Increase stall delay:

   StalledDelay = 30  # 30 minutes before considering stalled
   

2. Disable tracker error removal:

   RemoveDeadTrackers = false
   

3. Customize tracker error messages:

   RemoveTrackerWithMessage = [
     # Only remove on these specific errors
     "info hash is not authorized with this tracker"
   ]
   

Logging Issues¶

Too Many Logs¶

Symptoms: Log files growing too large

Solutions:

1. Reduce log level:

   [Settings]
   LogLevel = "INFO"  # Change from DEBUG
   

2. Enable log rotation:

   LogRotation = true
   LogMaxSize = 10485760    # 10 MB
   LogBackupCount = 5
   

3. Reduce retention:

   LogRetentionDays = 7  # Keep only 1 week
   

Can't Find Logs¶

Symptoms: Don't know where logs are located

Log Locations:

# Console logs
docker logs qbitrr

# File logs (if volume mounted)
ls -la /path/to/config/logs/

~/config/logs/
├── Main.log
├── WebUI.log
└── Radarr-Movies.log

# Journald logs
journalctl -u qbitrr -f

# File logs
ls -la /home/qbitrr/config/logs/

Update & Upgrade Issues¶

Update Fails¶

Symptoms: Auto-update or manual update fails

Solutions:

1. Check for sufficient disk space:

   df -h /path/to/qbitrr
   

2. Verify permissions:

   # For pip install
   pip install --upgrade qBitrr2 --user
   
   # For Docker
   docker pull feramance/qbitrr:latest
   

3. Check for breaking changes:

4. Review CHANGELOG.md

5. Backup config before upgrading

6. Manual update:

   # pip
   pip install --upgrade qBitrr2 --force-reinstall
   
   # Docker
   docker-compose pull qbitrr
   docker-compose up -d qbitrr
   

Version Mismatch Issues¶

Symptoms: Errors after update, incompatible features

Solutions:

1. Check version:

   qbitrr --version  # pip/native
   docker exec qbitrr qbitrr --version  # Docker
   

2. Review config migrations:

3. qBitrr auto-migrates config on version change

4. Check logs for migration messages

5. Rollback if needed:

   # pip
   pip install qBitrr2==5.4.0  # Specific version
   
   # Docker
   docker pull feramance/qbitrr:5.4.0
   

Clean Restart¶

Sometimes a clean restart resolves issues:

docker stop qbitrr
docker rm qbitrr
# Then recreate with your docker run command

sudo systemctl restart qbitrr

# Stop qBitrr (Ctrl+C if running in foreground)
# Then restart
qbitrr

Database Issues¶

If the database becomes corrupt:

1. Backup existing database:

   cp ~/config/qBitrr.db ~/config/qBitrr.db.backup
   

2. Let qBitrr recreate:

   rm ~/config/qBitrr.db
   # Restart qBitrr - it will create a new database
   

3. Recovery: qBitrr has automatic database recovery. Check logs for recovery messages.

Still Need Help?¶

If you've tried the troubleshooting steps and still have issues:

1. Review Common Issues for detailed solutions
2. Check Docker-specific issues if using Docker
3. Search GitHub Issues
4. Ask in GitHub Discussions

We're here to help! 🚀