Troubleshooting

This guide provides solutions for common issues you may encounter when using Cinephage.

Goal

Diagnose and resolve common problems with Cinephage.

Quick Diagnostics

Before diving into specific issues, perform these checks:

Check Application Status

1. Is Cinephage running?

   docker ps | grep cinephage

2. Check logs for errors:

   docker compose logs -f cinephage

3. Verify web interface loads:

   • Open browser to http://localhost:3000
   • Check for error messages

Check System Resources

• Disk Space: Ensure adequate space for database and media
• Memory: Cinephage uses 512MB-2GB RAM typically
• CPU: Normal usage is low, spikes during scans/searches

Common Issues

Cannot Access Web Interface

Symptoms: Browser shows "This site cannot be reached" or connection refused

Solutions:

1. Check if container is running:

   docker compose ps

   If not running, start it:

   docker compose up -d

2. Check port mapping:

   • Verify docker-compose.yaml has 3000:3000
   • Ensure port 3000 is not in use by another app
   • Try changing to 3001:3000 if needed

3. Check firewall:

   sudo ufw allow 3000/tcp  # For UFW
   sudo firewall-cmd --add-port=3000/tcp  # For firewalld

4. Check logs for startup errors:

   docker compose logs cinephage | tail -50

Authentication Issues

Symptoms: Cannot log in, "Invalid credentials", session expired

Solutions:

1. Reset admin password:

   • Access container shell:

     docker exec -it cinephage sh

   • Reset password via database or use recovery procedure
   • See logs for specific error

2. Check BETTER_AUTH_URL:

   • Must match your access URL exactly
   • If using reverse proxy, set to public URL
   • Example: BETTER_AUTH_URL=https://cinephage.yourdomain.com

3. Clear browser cookies:

   • Try incognito/private window
   • Clear cookies for your Cinephage domain
   • Try different browser

4. Check ORIGIN environment variable:

   • Must match your access URL
   • Required for CSRF protection

Downloads Not Starting

Symptoms: Searches find releases but nothing downloads

Solutions:

1. Check download client connection:

   • Go to Settings > Integrations > Download Clients
   • Verify status shows "Healthy"
   • Click Test to verify connection

2. Check indexer status:

   • Go to Settings > Integrations > Indexers
   • Verify indexers show "Healthy"
   • Test failing indexers

3. Check quality profile:

   • Ensure item has quality profile assigned
   • Verify profile allows the found releases
   • Check custom formats are not blocking

4. Check blocklist:

   • Go to Activity > Blocklist
   • See if releases are being blocked
   • Remove from blocklist if needed

5. Check monitoring:

   • Verify item is monitored (blue bookmark icon)
   • Unmonitored items are not downloaded automatically

Downloads Not Importing

Symptoms: Download completes but file not in library

Solutions:

1. Check path mappings:

   • Go to download client settings
   • Verify path mappings are correct
   • Ensure Cinephage can access download folder

2. Check file permissions:

   • Verify PUID/PGID in docker-compose.yaml
   • Ensure Cinephage can read download folder
   • Check file ownership in downloads directory

3. Check volume mounts:

   # Verify these paths exist and are correct
   volumes:
     - ./config:/config
     - /path/to/media:/media
     - /path/to/downloads:/downloads

4. Check logs:

   docker compose logs cinephage | grep -i import

5. Manual import test:

   • Go to Library > Import
   • Try importing the file manually
   • Check for specific error messages

TMDB API Errors

Symptoms: "TMDB API error", no search results, metadata missing

Solutions:

1. Verify API key:

   • Go to Settings > General
   • Check TMDB API key is entered
   • Click Test to verify

2. Check API key validity:

   • Visit themoviedb.org/settings/api
   • Verify key is active
   • Regenerate if needed

3. Check network connectivity:

   docker exec -it cinephage sh
   ping api.themoviedb.org

4. Check rate limits:

   • Free API has rate limits
   • Wait a few minutes if rate limited
   • Consider TMDB VIP for higher limits

Database Errors

Symptoms: "Database error", "SQLite error", data not saving

Solutions:

1. Check disk space:

   df -h

   Ensure config volume has space

2. Check database permissions:

   ls -la /path/to/config/*.db

   Should be owned by PUID/PGID

3. Database corruption check:

   docker exec -it cinephage sh
   sqlite3 /config/cinephage.db "PRAGMA integrity_check;"

4. Restore from backup:

   • If database is corrupt, restore from backup
   • Stop Cinephage first:

     docker compose down

   • Restore database file
   • Start Cinephage:

     docker compose up -d

Slow Performance

Symptoms: Slow page loads, searches take long time

Solutions:

1. Check system resources:

   • CPU usage during operations
   • Available memory
   • Disk I/O wait

2. Optimize database:

   docker exec -it cinephage sh
   sqlite3 /config/cinephage.db "VACUUM;"

3. Reduce indexer count:

   • Too many indexers slow searches
   • Use 3-5 quality indexers
   • Disable slow/broken indexers

4. Adjust worker limits:

   • Edit environment variables:

     environment:
       - WORKER_MAX_SEARCH=2
       - WORKER_MAX_SCANS=1

5. Check logs for slow queries:

   docker compose logs cinephage | grep -i "slow"

Subtitle Download Failures

Symptoms: Subtitles not downloading or syncing

Solutions:

1. Check subtitle providers:

   • Go to Settings > Integrations > Subtitle Providers
   • Verify providers are enabled
   • Test connections

2. Check language profile:

   • Ensure media has language profile assigned
   • Verify languages are configured correctly

3. Check API limits:

   • Some providers have daily limits
   • Wait for limit reset
   • Enable more providers

4. Manual sync:

   • If auto-sync fails, try manual sync
   • Go to media detail > Subtitles
   • Click Sync on subtitle file

Advanced Troubleshooting

Enable Debug Logging

Get more detailed logs:

1. Set environment variable:

   environment:
     - LOG_LEVEL=debug

2. Restart Cinephage:

   docker compose restart

3. Check detailed logs:

   docker compose logs -f cinephage

Database Inspection

Investigate database issues:

# Access database
docker exec -it cinephage sqlite3 /config/cinephage.db

# List tables
.tables

# Check table counts
SELECT COUNT(*) FROM movies;
SELECT COUNT(*) FROM series;

# Check for errors
SELECT * FROM settings WHERE key LIKE '%error%';

# Exit
.quit

Reset Specific Components

Reset tasks:

1. Stop Cinephage
2. Delete or rename task history in database
3. Restart Cinephage

Clear cache:

1. Stop Cinephage
2. Clear cache directory:

   rm -rf /path/to/config/cache/*

3. Restart Cinephage

Getting Help

If you cannot resolve the issue:

Gather Information

Before asking for help, collect:

1. Cinephage version:

   • Check Settings > System

2. Docker version:

   docker --version
   docker compose version

3. Relevant logs:

   docker compose logs cinephage --tail 100 > cinephage-logs.txt

4. Configuration (remove sensitive data):

   cat docker-compose.yaml

5. System info:

   uname -a
   free -h
   df -h

Where to Ask

1. Discord - Join community

   • Real-time chat support
   • Searchable history

2. GitHub Issues - Report bugs

   • Bug reports
   • Feature requests
   • Include logs and reproduction steps

Bug Report Template

**Description:**
Clear description of the issue

**Steps to Reproduce:**

1. Go to '...'
2. Click on '...'
3. See error

**Expected Behavior:**
What should happen

**Actual Behavior:**
What actually happens

**Logs:**

Paste relevant logs here

**Environment:**
- Cinephage version:
- Docker version:
- Host OS:
- Browser:

**Additional Context:**
Any other relevant information

Prevention

Regular Maintenance

• Check logs weekly for errors
• Monitor disk space
• Keep Cinephage updated
• Backup database regularly

Monitoring

• Watch Activity > History for patterns
• Review Settings > Logs periodically
• Monitor system resources

Best Practices

• Use stable Docker tags (not dev in production)
• Keep configuration in version control
• Document custom settings
• Test changes in non-production first

See Also

• Getting Help
• FAQ
• Performance Tuning
• Backup and Restore