-
-
Notifications
You must be signed in to change notification settings - Fork 3
Troubleshooting
Christian Blank edited this page Nov 8, 2024
·
1 revision
- Check if the bot is running
- Docker:
docker psto verify container status - Manual: Check the process is running
- Docker:
- Verify your Telegram token is correct
- Ensure you're an authorized user in config.ini
- Verify host URLs are correct
- Check API keys
- Ensure Sonarr/Radarr are running
- Check network connectivity
- Verify port forwarding if using remote access
- "Unauthorized": Check your Telegram user ID in config.ini
- "Connection refused": Verify host/port settings
- "API key invalid": Double-check your API keys
- Ensure config.ini exists
- Check file permissions
- Verify syntax is correct
- Confirm all required fields are filled
- Verify root folders exist
- Check folder permissions
- Use absolute paths
- Ensure correct path format for your OS
- Docker:
docker logs addarr - Manual: Check the application logs in the Addarr directory
To enable detailed logging:
- Edit config.ini
- Set debug = true
- Restart Addarr
- Stop Addarr
- Backup config.ini
- Delete config.ini
- Copy config.ini.example to config.ini
- Reconfigure settings
- Start Addarr
- Stop Addarr
- Remove cache files
- Restart Addarr
If issues persist:
- Gather logs
- Check GitHub issues
- Create a new issue with:
- Error messages
- Configuration (remove sensitive data)
- Steps to reproduce