Troubleshooting

🔧 Troubleshooting

Common issues and solutions for easiarr and *arr applications.

---

🐳 Docker Issues

Container Won't Start

Symptoms: Container exits immediately or enters restart loop.

Solutions:

1. Check logs:

   docker logs <container-name>

2. Verify permissions:

   ls -la ~/.config/easiarr/config/<app>/
   # Should be owned by PUID:PGID

3. Fix permissions:

   sudo chown -R 1000:1000 ~/.config/easiarr/config/

4. Check disk space:

   df -h

---

Port Already in Use

Symptoms: bind: address already in use

Solutions:

1. Find conflicting process:

   sudo lsof -i :8080  # Replace with port number

2. Change port in easiarr App Manager

3. Stop conflicting service:

   sudo systemctl stop <service>

---

Container Can't Access Network

Symptoms: No internet inside container, DNS failures.

Solutions:

1. Check Docker network:

   docker network ls
   docker network inspect easiarr_default

2. Restart Docker:

   sudo systemctl restart docker

3. Check DNS:

   docker exec <container> nslookup google.com

---

🔍 *Arr Application Issues

API Key Not Found

Symptoms: easiarr can't extract API key.

Solutions:

1. Start the app first - API key is generated on first run
2. Check config file exists:

   cat ~/.config/easiarr/config/radarr/config.xml | grep ApiKey

3. Restart the container

---

Root Folder Not Working

Symptoms: "Path does not exist" errors.

Solutions:

1. Verify path exists inside container:

   docker exec radarr ls -la /data/media/movies

2. Check volume mounts:

   docker inspect radarr | grep Mounts -A 20

3. Create directory:

   mkdir -p ~/.config/easiarr/data/media/movies

---

Download Client Connection Failed

Symptoms: Can't connect to qBittorrent/SABnzbd.

Solutions:

1. Use container name as hostname (e.g., qbittorrent, not localhost)

2. Check container is running:

   docker ps | grep qbittorrent

3. Verify network:

   docker exec radarr ping qbittorrent

---

🌐 Network Issues

Traefik Not Routing

Symptoms: 404/502 errors, can't access services.

Solutions:

1. Check Traefik dashboard at http://localhost:8083

2. Verify labels on container:

   docker inspect <container> | grep Labels -A 50

3. Check Traefik logs:

   docker logs traefik

4. Verify DNS points to correct IP

---

HTTPS Certificate Issues

Symptoms: Certificate errors, insecure warnings.

Solutions:

1. Check ACME status:

   docker logs traefik 2>&1 | grep -i acme

2. Verify domain DNS:

   nslookup yourdomain.com

3. Check rate limits - Let's Encrypt has limits

4. Try staging first:

   # In traefik.yml
   certificatesResolvers:
     letsencrypt:
       acme:
         caServer: "https://acme-staging-v02.api.letsencrypt.org/directory"

---

Cloudflare Tunnel Not Working

Symptoms: Sites not accessible externally.

Solutions:

1. Check cloudflared status:

   docker logs cloudflared

2. Verify tunnel token in .env

3. Check Cloudflare dashboard for tunnel status

4. Verify DNS records in Cloudflare

---

🛡️ VPN Issues

VPN Not Connecting

Symptoms: Gluetun fails to connect.

Solutions:

1. Check credentials:

   docker logs gluetun 2>&1 | grep -i auth

2. Try different server:

   SERVER_COUNTRIES=Sweden

3. Check provider status page

4. Verify WireGuard key format

---

No Internet Through VPN

Symptoms: Containers using VPN have no internet.

Solutions:

1. Check Gluetun health:

   docker exec gluetun wget -qO- ifconfig.me

2. Verify DNS:

   docker exec gluetun nslookup google.com

3. Check kill switch isn't blocking

---

qBittorrent Not Accessible via VPN

Symptoms: WebUI not reachable when using VPN.

Solutions:

1. Check port exposure - ports must be on Gluetun:

   gluetun:
     ports:
       - "8080:8080"

2. Verify container network mode:

   qbittorrent:
     network_mode: "service:gluetun"

---

📊 Performance Issues

Slow Imports

Symptoms: Imports take very long instead of being instant.

Cause: Hardlinks not working (different filesystems).

Solutions:

1. Verify same filesystem:

   df ~/.config/easiarr/data/torrents
   df ~/.config/easiarr/data/media
   # Should be same filesystem

2. Check hardlinks working:

   ls -li /path/to/file
   # Same inode = hardlink working

---

High CPU/Memory Usage

Solutions:

1. Check resource usage:

   docker stats

2. Reduce concurrent operations in *arr apps

3. Add resource limits:

   services:
     radarr:
       deploy:
         resources:
           limits:
             cpus: "0.5"
             memory: 512M

---

🔍 Debugging Commands

Container Logs

# View logs
docker logs <container>

# Follow logs
docker logs -f <container>

# Last 100 lines
docker logs --tail 100 <container>

Container Shell

# Access container shell
docker exec -it <container> /bin/bash
# or
docker exec -it <container> /bin/sh

Network Debugging

# Test connectivity
docker exec <container> ping <other-container>

# Test DNS
docker exec <container> nslookup <hostname>

# Test HTTP
docker exec <container> curl -v http://<service>:<port>

File Permissions

# Check permissions
docker exec <container> ls -la /config

# Check user
docker exec <container> id

---

💡 Getting Help

If you can't resolve an issue:

1. Check existing issues on GitHub

2. Search TRaSH Guides for app-specific issues

3. Open a new issue with:

   • easiarr version
   • Docker logs
   • Steps to reproduce
   • Expected vs actual behavior

---

🔗 Related

• FAQ - Frequently asked questions
• Configuration - Configuration reference
• VPN-Configuration - VPN troubleshooting