About
……………github.com to read the latest published versions — nothing is sent, and only when you click or enable the daily check. Handy for bug reports: quote these three lines so we can tell if your defs or pathways are out of date.Account
Network
X-Forwarded-For for login rate-limiting (so one bad client can't lock everyone out through the proxy) and X-Forwarded-Proto to mark the session cookie Secure behind HTTPS. Leave off when directly exposed — these headers can be faked by clients.localhost always works and needs nothing here.
Add your domain or Tailscale name — comma-separated for more than one — and it applies straight away, no restart.
Set this before you need it: if you set Yata up on this machine but reach it by a domain when you're away, add the domain now, while you can still get to this page.
Names Yata wasn't told about are refused, which is what stops a web page you visit from re-pointing its own domain at your machine to read this dashboard.
Data
Theme
Tracker Names
Dashboard
css/all.min.css and webfonts/ into static/fontawesome/Private Mode
Pathways
Automatic Refresh
Profile Scraping
Configured Trackers
| Actions | ||||||
|---|---|---|---|---|---|---|
| Loading… | ||||||
API keys come from Prowlarr's stored indexer settings; trackers without one import with no key (add it via Edit).
Credentials come from Jackett's stored indexer settings — API keys and session cookies import where available, so scraping can work out of the box. Cookies expire eventually; refresh them via Edit if a scrape stops working.
Tracker Definitions
defs/ without restarting
-or- use the Cookie-Editor extension Export button → Header String Re-paste if profile stats stop working.
test_data.json — no real API calls made.
Integrations
Qui is a qBittorrent management UI. Configure its address and API key, then select which instances to show.
Read-only tokens let other apps — homelab dashboards like
Homepage or
Homarr, scripts, monitoring — read your
stats without your login. A token only unlocks the read-only endpoints (/api/summary, /api/history/series);
it can never change anything or see tracker credentials. Full details in the
API reference.
Alerts & Notifications
Send webhook notifications (Discord, Telegram, Gotify, or a generic JSON POST) when a rule's conditions are met — e.g. ratio drops below a threshold, a hit & run appears, unread mail or notifications arrive (updated by profile scrapes, so up to one scrape interval late), or a tracker event starts (freeleech, open registration, etc. — the banner text is passed through). Rules are checked every few minutes on the server, so alerts fire even with no browser open.
Logs
Live application log — useful for troubleshooting and for attaching to GitHub issues. Everything is captured to a rotating file on disk (…); the level buttons below only choose what's shown here.