Before you startWhat is needed
- CasaOS 0.4 or later. Docker Compose v2 comes with it.
- About 10 GB of free disk for the index and the search index, and room for what you plan to download.
- SSH access to the box.
- A Telegram account, if you want Telegram. Your own is fine: only your account ever signs in to your tgarr.
No account of any kind is needed to begin. The full guide in the repository: docs/install/casaos.md.
StepsTwo files and one command
- SSH into the CasaOS box and get the two files.
sudo mkdir -p /DATA/AppData/tgarr/app sudo chown -R $USER /DATA/AppData/tgarr cd /DATA/AppData/tgarr/app curl -fsSLO https://raw.githubusercontent.com/tgarrpro/tgarr/main/docker-compose.yml curl -fsSL https://raw.githubusercontent.com/tgarrpro/tgarr/main/.env.example -o .env chmod 600 .env - Get Telegram API credentials (this can wait - see the next step). Visit my.telegram.org/apps, sign in with your phone number, create a new app - any name will do - and copy the
api_idandapi_hash. - Fill in
.env.
Four values:nano .env
Make the two secrets fresh and paste them in:TG_API_ID= # from https://my.telegram.org/apps TG_API_HASH= # from https://my.telegram.org/apps DB_PASSWORD= # a secret of your own: openssl rand -hex 24 MEILI_MASTER_KEY= # a secret of your own: openssl rand -hex 32
The two Telegram values may be left empty: tgarr then asks for them in the browser when they are first needed.echo "DB_PASSWORD=$(openssl rand -hex 24)" echo "MEILI_MASTER_KEY=$(openssl rand -hex 32)" - Start it.
docker compose up -d - Open
http://<your-host>:8765in a browser. To sign in to Telegram, scan the QR code with the Telegram app, or enter your phone number and the code Telegram sends you. Nothing is typed in a terminal, and the code never touches a file. - Follow some channels. tgarr indexes the channels your Telegram account has joined. Join one in the Telegram app; the crawler picks it up within minutes and then reads its history, which for a large channel can take from half an hour to several hours.
On the diskWhere the files and downloads end up
Everything tgarr keeps is in /DATA/AppData/tgarr/app/_data/, beside the two files:
_data/postgres- the index (PostgreSQL)._data/meili- the search index (Meilisearch)._data/session- the Telegram sign-in. You sign in once._data/downloads- grabbed and opened files. Inside the containers this is/downloads; a grab from Sonarr or Radarr lands in/downloads/tgarr/<release-name>/.
To keep downloads somewhere else - the folder Sonarr and Radarr import from, say - set TGARR_DOWNLOADS in .env to that path. The port is 8765; TGARR_PORT changes it. If others can reach the port, set TGARR_UI_PASSWORD as well.
UpdatesIt keeps itself up to date
The compose file brings an updater with it: a container named tgarr-watchtower that looks only at tgarr's own two containers - nothing else on the NAS - and checks for a new release every half hour. The index, the settings and the Telegram sign-in are kept. In tgarr, Settings → Updating tgarr has an Update now button. To stay on one version, set TGARR_TAG in .env.
By hand:
cd /DATA/AppData/tgarr/app
docker compose pull
docker compose up -dThe sign-in, the database and the downloads stay as they are.
At homeHow the household reaches it
Every browser at home opens the same address: http://<the-NAS>:8765. Open Media Center & PIN and set a PIN, and every browser that has not entered it gets only the Media Center - films, music, books and photos, and only what you ticked - with time rules for the children if you want them. More on that: a learning library for the family.


Sonarr and RadarrOn the same CasaOS box
In Sonarr and Radarr: Settings → Indexers → + → Newznab, URL http://<the-NAS>:8765/newznab/ - tgarr's Dashboard shows the exact address, with a Copy button. For grabs from Telegram, add tgarr as a download client too: Settings → Download Clients → + → SABnzbd, same host and port, URL Base /sabnzbd. Sonarr and Radarr must be able to read the finished file: either set TGARR_DOWNLOADS to the folder they import from, or mount tgarr's _data/downloads into their containers as /downloads - then the path is the same on both sides and no remote path mapping is needed. On CasaOS that folder is /DATA/AppData/tgarr/app/_data/downloads. Field by field: tgarr in Sonarr and Radarr.
OptionalConverting films on the graphics card
A film the browser cannot play is converted while it is watched. Intel graphics from 2015 on can do that for a fraction of a processor core, and tgarr uses the card by itself once its container is given one. Put a file named docker-compose.override.yml beside docker-compose.yml:
services:
api:
devices:
- /dev/dri:/dev/driThen docker compose up -d. Docker refuses to start a container that names a card which is not there, so do this only on a machine that has /dev/dri. Settings → Converting films says what is in use. NVIDIA, and the details: docs/install/gpu.md.
If something is offTroubleshooting
- Nothing indexed after half an hour. The channels the account has joined carry links or text only. tgarr indexes channels that post files.
- The page does not open. A container did not start. Look at why:
docker logs --tail 50 tgarr-api. - The Dashboard says a newer version is there and nothing happens. Check the updater with
docker ps -a --filter name=tgarr-watchtower. If it saysRestarting, readdocker logs --tail 5 tgarr-watchtower.client version 1.25 is too oldmeans the compose file predates 12 November 2026: download it again. If the message names another version, put the one your Docker accepts (docker versionshows it) in.envasTGARR_DOCKER_API=. - Sonarr's Test on the indexer fails. The address is wrong. On the NAS,
curl "http://localhost:8765/newznab/api?t=caps"should return XML. - A download stays on "downloading". A large file takes time, and Telegram slows large transfers (a
FloodWaitin the log is normal and handled by itself).docker logs --tail 50 tgarr-crawlershows the progress. - The file is there but Sonarr does not import it. Sonarr cannot read the path. See the paragraph on Sonarr and Radarr above.
QuestionsAsked often
Is tgarr in the CasaOS app store?
Not yet - an entry is planned. Until then tgarr is installed over SSH with two files and docker compose up -d, in /DATA/AppData/tgarr/app.
What does tgarr need on CasaOS?
CasaOS 0.4 or later (Docker Compose v2 comes with it), about 10 GB of free disk for the index and the search index, and room for what you download.
Can Sonarr and Radarr on the same CasaOS box use tgarr?
Yes, and that is the layout the guide recommends. Add tgarr as a Newznab indexer with the address its Dashboard shows (http://your-box:8765/newznab/) and as a SABnzbd download client with URL Base /sabnzbd. With tgarr's downloads folder mounted into Sonarr as /downloads, no remote path mapping is needed.
Do I need a Telegram account to install it?
Not to begin. The two Telegram values in .env may be left empty; tgarr then asks for them in the browser when they are first needed. The Internet Archive and your own files work with no account of any kind.
How does tgarr update on a NAS?
By itself. The compose file includes an updater that looks only at tgarr's own containers and checks for a new release every half hour. Setting TGARR_TAG in .env keeps it on one version.