# Fetcharr

Fetcharr is a lightweight automation companion for Sonarr, Radarr, Lidarr, and other *arr apps. It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/1379/fetcharr

## Description

Fetcharr is a lightweight automation companion for Sonarr, Radarr, Lidarr, and other *arr apps. It continuously scans your libraries for missing, wanted, or upgradeable content and triggers active searches automatically to improve media acquisition beyond standard RSS syncing. Designed for self-hosted environments with simple Docker deployment and low resource usage.

## Platform availability

Available on 1 of 9 platforms: Unraid.

## Health score

57/100 (Fair), based on 3 of 4 factors.
- Maintained: 71 (last commit 68 days ago)
- Popular: 51 (347 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/egg82/fetcharr/
- Unraid: https://ca.unraid.net/apps/fetcharr-174k9140ojgaz8?q=Fetcharr

## Common questions

### Does Fetcharr support plugins?

Yes. Fetcharr offers plugin support for customization and extensibility beyond the base application.

### Why does the Fetcharr Docker container need host networking?

Fetcharr finds the box by listening for SSDP announcements on the network. Those broadcasts do not reach Docker's private network, so the container must run with host networking.

### What file permission issue is mentioned for a self-hosted *arr stack that includes Fetcharr?

Most problems are from file/folder permissions for the default user. The source notes it is unclear whether each service needs its own media group or user account.

### Is there a community forum for Fetcharr?

Fetchforum is a community forum site named Fetchforum.

---
Source: Our Local Host (https://ourlocalhost.com/app/1379/fetcharr), the self-hosted and open-source app directory.