Troubleshooting
This guide will help you diagnose and resolve issues with Reaparr. Follow these steps systematically to identify and fix problems.
General Debugging Steps
1. Check System Requirements
Before troubleshooting, ensure your system meets the minimum requirements:
- Docker: Version 20.10 or higher
- CPU: Modern multi-core processor
- RAM: Minimum 2GB available
- Storage: Adequate space for downloads and database
- Network: Stable internet connection
2. Verify Container Status
Check if the Reaparr container is running:
docker ps -a | grep reaparr
If the container is not running or constantly restarting:
# Check container logs
docker logs reaparr
# Check last 100 lines
docker logs --tail 100 reaparr
# Follow logs in real-time
docker logs -f reaparr
3. Review Log Files
Logs are your best friend when debugging. They contain detailed information about what's happening.
Log Location: /Config/Logs (inside container) or your mapped host directory
# If using Docker, access logs from host
cd /path/to/your/config/Logs
# View the latest log file
tail -f reaparr.log
# Search for errors
grep -i "error" reaparr.log
grep -i "exception" reaparr.log
grep -i "failed" reaparr.log
What to look for in logs:
- Error messages with stack traces
- Failed authentication attempts
- Network connection issues
- Permission denied errors
- Database errors
4. Check Configuration Files
Verify your configuration is correct:
# Check ReaparrSettings.json
cat /path/to/config/ReaparrSettings.json
# Validate JSON syntax
python -m json.tool /path/to/config/ReaparrSettings.json
Common configuration issues:
- Invalid JSON syntax
- Incorrect file paths
- Wrong port numbers
- Invalid Plex credentials
5. Verify Network Connectivity
Test network access to Plex servers:
# Test connectivity to Plex
curl -I https://plex.tv
# Test connectivity to your Plex server
curl -I http://your-plex-server:32400
# Check DNS resolution
nslookup plex.tv
6. Check File Permissions
Permission issues are common with Docker containers:
# Check ownership of config directory
ls -la /path/to/your/config
# Check ownership of download directory
ls -la /path/to/your/downloads
# Fix permissions if needed (replace PUID:PGID with your values)
sudo chown -R 1000:1000 /path/to/your/config
sudo chown -R 1000:1000 /path/to/your/downloads
sudo chmod -R 755 /path/to/your/downloads
Common Issues and Solutions
Cannot Access Web Interface
Symptoms: Unable to reach Reaparr at http://localhost:7000
Solutions:
- Check if container is running:
docker ps | grep reaparr - Verify port mapping:
docker port reaparr
Should show:7000/tcp -> 0.0.0.0:7000 - Check firewall:
# Linux - check if port is open sudo ufw status sudo ufw allow 7000 # Check if something else is using the port sudo netstat -tuln | grep 7000 - Test from inside container:
docker exec -it reaparr curl http://localhost:7000 - Try different browser: Some extensions (ad blockers, Dark Reader) can interfere
Downloads Not Starting
Symptoms: Downloads stuck in queue or not starting
Debugging Steps:
- Check Plex account connection:
- Go to Settings → Plex Accounts
- Verify account shows as "Connected"
- Check token is valid
- Verify server accessibility:
- Ensure Plex server is online
- Check server shows as "Available" in Reaparr
- Test server connection manually
- Review download settings:
- Check download location is valid
- Verify download limits aren't reached
- Ensure bandwidth limits aren't too restrictive
- Check logs for errors:
docker logs reaparr | grep -i "download"
Permission Denied Errors
Symptoms:
Permission deniederrors in logsAccess to the path is denied- Files not being written
Solution:
- Check PUID/PGID environment variables:
docker inspect reaparr | grep -i puid docker inspect reaparr | grep -i pgid - Find your user's PUID/PGID:
id your-username - Update Docker configuration:
Docker Compose:environment: - PUID=1000 - PGID=1000
Docker CLI:docker run -e PUID=1000 -e PGID=1000 ... - Fix directory permissions:
sudo chown -R 1000:1000 /path/to/downloads sudo chmod -R 755 /path/to/downloads - Restart container:
docker restart reaparr
Authentication Issues
Symptoms:
- Cannot login to Plex
- "Invalid credentials" errors
- Token authentication failing
Solutions:
- Verify Plex credentials:
- Ensure username/email and password are correct
- Check if 2FA is enabled on Plex account
- Check username login setting:
- Go to plex.tv → Settings → Account
- Enable "Allow username to be used when signing in"
- Try authentication token method:
- Get your Plex token: Finding X-Plex-Token
- Use token instead of password
- Clear authentication cache:
# Stop container docker stop reaparr # Remove cached authentication (if exists) rm -f /path/to/config/auth-cache.json # Start container docker start reaparr
Database Corruption
Symptoms:
- Reaparr won't start
- Database errors in logs
- Missing data after restart
Solutions:
- Backup current database:
cp /path/to/config/reaparr.db /path/to/config/reaparr.db.backup - Check database integrity:
sqlite3 /path/to/config/reaparr.db "PRAGMA integrity_check;" - Restore from backup (if available):
# Stop Reaparr docker stop reaparr # Restore backup cp /path/to/config/backups/reaparr.db /path/to/config/reaparr.db # Start Reaparr docker start reaparr - Reset database (last resort - loses all data):
docker stop reaparr rm /path/to/config/reaparr.db docker start reaparr
Slow Performance
Symptoms:
- UI is sluggish
- Downloads are slow
- High CPU/RAM usage
Debugging Steps:
- Check resource usage:
docker stats reaparr - Review concurrent downloads:
- Reduce number of simultaneous downloads
- Lower download speed limits
- Check disk I/O:
iostat -x 1 - Monitor network:
# Check bandwidth usage iftop - Review system load:
htop
Images Not Loading
Symptoms: Poster images not showing in library view
Solutions:
- Verify Plex server is online: Images are loaded directly from Plex server
- Disable browser extensions:
- Disable ad blockers (uBlock Origin, AdBlock)
- Disable Dark Reader
- Disable privacy extensions
- Check browser console:
- Press F12 to open developer tools
- Check Console tab for errors
- Check Network tab for failed requests
- Test in different browser: Try Chrome/Firefox without extensions
- Check HTTPS/HTTP issues:
- Firefox may block non-HTTPS connections
- Mixed content warnings in browser console
Container Won't Start
Symptoms: Container starts then immediately stops
Debugging Steps:
- Check logs immediately:
docker logs reaparr - Common causes:
- Port already in use
- Invalid volume mounts
- Corrupted configuration
- Missing required environment variables
- Verify Docker setup:
# Check Docker version docker --version # Check Docker is running sudo systemctl status docker - Test with minimal configuration:
docker run -d \ --name reaparr-test \ -p 7001:7000 \ -v /tmp/reaparr-test:/Config \ reaparr/reaparr:latest - Check for conflicting containers:
docker ps -a
Advanced Debugging
Enable Debug Logging
For more detailed logs, enable debug mode:
- Stop Reaparr
- Edit
/Config/ReaparrSettings.json - Set
"LogLevel": "Debug" - Restart Reaparr
{
"LogLevel": "Debug",
...
}
Inspect Docker Container
Get detailed container information:
# Full container inspection
docker inspect reaparr
# Check environment variables
docker inspect reaparr | grep -A 20 "Env"
# Check mounted volumes
docker inspect reaparr | grep -A 20 "Mounts"
# Check networking
docker inspect reaparr | grep -A 20 "Networks"
Network Debugging
Test connectivity from inside the container:
# Enter container shell
docker exec -it reaparr sh
# Test DNS
nslookup plex.tv
# Test HTTP connectivity
wget -O- https://plex.tv
# Check open connections
netstat -an | grep ESTABLISHED
Database Inspection
Inspect the Reaparr database:
# Open database
sqlite3 /path/to/config/reaparr.db
# List tables
.tables
# Check schema
.schema
# Query example
SELECT * FROM PlexServers;
# Exit
.quit
Getting Help
If you've tried all the above steps and still have issues:
1. Gather Information
Before asking for help, collect:
- Reaparr version: Check in Settings → About
- Docker version:
docker --version - Operating system:
uname -a(Linux) or system info - Docker compose file or run command (remove sensitive data)
- Relevant log excerpts (last 50-100 lines)
- Steps to reproduce the issue
2. Search Existing Issues
Check if others have reported the same issue:
3. Create a Bug Report
If it's a new issue, create a detailed bug report:
- Go to GitHub Issues
- Use the bug report template
- Include all information gathered above
- Be specific about what you expected vs what happened
4. Join the Community
Get real-time help:
- Discord Server
- Be patient and respectful
- Provide all requested information
Prevention Tips
Regular Maintenance
- Keep Reaparr updated: Pull latest Docker image regularly
- Monitor disk space: Ensure adequate free space
- Review logs periodically: Catch issues early
- Backup configuration: Regularly backup
/Configdirectory
Backup Strategy
# Create backup script
#!/bin/bash
DATE=$(date +%Y%m%d_%H%M%S)
BACKUP_DIR="/backups/reaparr"
CONFIG_DIR="/path/to/config"
mkdir -p "$BACKUP_DIR"
tar -czf "$BACKUP_DIR/reaparr-config-$DATE.tar.gz" "$CONFIG_DIR"
# Keep only last 7 backups
ls -t "$BACKUP_DIR"/reaparr-config-*.tar.gz | tail -n +8 | xargs rm -f
Monitoring
Set up basic monitoring:
# Check if Reaparr is responding
curl -f http://localhost:7000 || echo "Reaparr is down!"
# Monitor disk space
df -h /path/to/downloads
# Check log for errors
grep -i "error" /path/to/config/Logs/reaparr.log | tail -n 10
Quick Reference
Useful Commands
# View logs
docker logs -f reaparr
# Restart container
docker restart reaparr
# Check resource usage
docker stats reaparr
# Enter container
docker exec -it reaparr sh
# Update Reaparr
docker pull reaparr/reaparr:latest
docker stop reaparr
docker rm reaparr
# Run with same parameters
docker start reaparr
Important File Locations
| Item | Container Path | Description |
|---|---|---|
| Configuration | /Config | Main config directory |
| Settings | /Config/ReaparrSettings.json | Application settings |
| Database | /Config/reaparr.db | SQLite database |
| Logs | /Config/Logs | Log files |
| Downloads | Varies | Your mapped download path |
Common Error Messages
| Error | Likely Cause | Solution |
|---|---|---|
Permission denied | Wrong PUID/PGID | Set correct PUID/PGID and fix file permissions |
Address already in use | Port conflict | Change port mapping or stop conflicting service |
Connection refused | Service not running | Check if Reaparr is running |
Invalid token | Expired auth | Re-authenticate with Plex |
Database locked | Multiple instances | Ensure only one Reaparr instance is running |
Disk full | No storage space | Free up disk space |
Frequently Asked Questions
Find answers to common questions about Reaparr, including installation, Plex account setup, troubleshooting, and how to support the project. If you have a question that isn't answered here, please check the documentation or ask in the community.
Overview
Show your support for Reaparr and help the project grow! This page outlines various ways you can contribute to the development and improvement of Reaparr, whether you're a programmer, writer, tester, or just a fan of the project.