Repository navigation
FAQ
🏠 Home › FAQ
Short answers to common questions. For anything not here, see Troubleshooting.
A self-hosted web app that keeps a Plex library tidy: point it at Radarr, Sonarr, Lidarr and Plex, and it renames posters, finds duplicates, applies borders, searches for upgrades, cleans orphaned files, and more. See Home.
CHUB is a fork of DAPS: the DAPS modules plus plex_maintenance and asset_renamerr, a new UI with live status, duplicate review, and tighter security. See Credits.
Your config.yml carries over: CHUB converts a DAPS config on first load and keeps the original as config.yml.legacy-<timestamp>.yml (details). Check the paths resolve inside the new container. Nothing else carries over — match state, applied-poster history and hashes are rebuilt on the first runs. DAPS can keep running alongside during the switch.
Not directly. It's built for a LAN or VPN. It has a login (keep it on) and rate limiting, but isn't hardened against a determined attacker. For remote access, put it behind a reverse proxy with TLS and a second auth layer (Authelia, Authentik, Cloudflare Access).
See Troubleshooting → Reset the admin password.
See the First-Run walkthrough.
Yes. Modules pick libraries per Plex instance: plex_scope in poster_renamerr, asset_renamerr and unmatched_assets, and library_mappings in nestarr. List both instances (e.g. radarr and radarr4k) as a Quality Instance Group on Settings → General so shared titles aren't flagged as duplicates.
Yes: upgradinatorr (album searches, all three modes), renameinatorr, labelarr, nestarr, unmatched_assets, and poster_renamerr for artist and album art.
Dashboard → New run, or Run now on the module's row or settings page.
Click the module's Running button on the Dashboard. Most stop within seconds; see Troubleshooting → Cancel doesn't stop a module for the exceptions.
Everything is in the folder mounted at /config:
-
config.yml— settings, including the login -
chub.db— database (jobs, media, poster index, edit history) -
logs/— per-module log files -
backups/— backup zips (unlessgeneral.backup_dirpoints elsewhere)
Posters and media stay on their own mounts.
-
UI: Settings → System → Backups & database → Back up downloads a zip of
config.ymland achub.dbdump and keeps a copy in the backups folder. Automatic config backups there makes one a day. - Files: stop the container, copy the config folder, start it.
docker compose pull
docker compose up -dDatabase and config changes apply on startup. Pin a vX.Y.Z tag if you'd rather update by hand (Image tags).
Yes — configure only what you run.
No separate key. Inbound webhooks use general.webhook_secret (Webhooks). Scripts log in with POST /api/auth/login and send the returned token (REST API).
No. Kometa manages Plex metadata and collections; CHUB manages poster files and media chores. CHUB can apply posters itself (apply_method: plex) or feed Kometa's asset folder. See Kometa Integration.
No. poster_renamerr matches against your *arr's metadata from its API, not your folder names. To improve matching, fix the poster files' names. See Modules → poster_renamerr.
Yes — switch it off on Settings → Modules. It's then skipped by the scheduler, can't be run by hand, and its webhook jobs are skipped. (A module with no schedule just doesn't run on its own.)
CHUB runs as PUID/PGID (default 99/100, as on Unraid; most Linux hosts want 1000/1000). It fixes ownership inside /config at startup; other mounts must already be writable. Rootless with user: works too. See Installation.
See the Developer Guide.
Next: Credits · Related: Troubleshooting, Modules