Settings reference ​

Everything in Settings, by tab. The tabs, in order, are Overview, Library, Downloading, Sources, Metadata, Plugins (only shown once an installed plugin mounts a panel there), Sign-in and Notifications. Library, Sources and Plugins use a master–detail layout: a rail of panels on the left, one panel at a time on the right. Editing anything raises a save bar at the bottom of the page — nothing is written until you press Save changes — except library edits, which apply immediately.

Saved values live in settings.json in the data directory, next to the database — /data in Docker (see Where your data lives).

Plugins contribute settings of their own. Most land on the Plugins tab, but a plugin can also add a panel to Library, Sources, Sign-in or Notifications — so what you see depends on what you have installed.

Overview ​

No settings here, just the state of the install: health cards for sources, metadata, libraries, storage, downloading and notifications, and a Needs attention list. Every card and every warning is a link straight to the tab that fixes it.

Library ​

Three panels: Libraries, File organization and Maintenance.

Libraries ​

Named libraries — each one appears as its own entry in the sidebar. See Libraries. Changes here save as you make them.

File organization ​

How downloaded comics are named and filed. See Naming patterns.

Pattern changes affect new downloads. To apply them to files you already have, run Reorganize library on the Tools page.

Maintenance ​

Reader settings ​

With the reader plugin installed, three more toggles appear at the bottom of the Libraries panel:

Downloading ​

What happens when you add a series, and how downloads run.

Sources ​

The rail lists Usenet, Torrents, every download source you have installed, and — once two or more are enabled — Source priority. Each source panel starts with its own on/off switch. See Download sources.

Usenet ​

Torrents ​

After import, torrents are left seeding — manage ratio and removal in the client.

Other sources ​

Every source you install from the catalogue, and every source a plugin provides, gets its own rail entry with its own switch and fields (credentials, language preferences, and so on). A source that sits behind Cloudflare says so and uses the shared FlareSolverr URL from the Downloading tab rather than asking for one itself.

Source priority ​

Appears once two or more sources are enabled. When more than one source can serve an issue they are tried top to bottom, and the first with a match wins. Reorder with the arrows.

Metadata ​

Where series and issue data comes from, and how it is written into your files.

There is no field for pointing the app at a different metadata service. An old cvBaseUrl setting still exists in saved configuration but is deliberately ignored — stale or malformed values in it used to surface as puzzling auth failures. If you want to stay off the hosted service entirely, set Source to ComicVine and supply your own key.

Plugins ​

This tab appears once an installed plugin mounts a panel on it, and shows one rail entry per plugin — so its contents depend entirely on what you have installed. Each plugin's own page documents its settings; these are the ones other pages send you here for:

Not every plugin puts its settings here: download sources appear on Sources, notification channels on Notifications, sign-in providers on Sign-in, and the reader's preferences on Library.

Where each plugin's settings are documented ​

Plugins with more than a switch or two are written up on their own page rather than repeated here. This is the full index:

A few plugin settings aren't on this tab at all because they're schedules: the AirDC++ announce-bot watch is enabled and timed on System → Jobs, like every other job.

Sign-in ​

How people sign in. Password login always works for admins, whatever else is configured.

Install a sign-in provider (OIDC, for example) from the Plugins page and its configuration appears on this tab. See Signing in with an identity provider.

Notifications ​

Outbound channels come from the Notifications Hub plugin — one collapsible card per channel (Discord, Telegram, Pushover, ntfy, generic webhook), each with its own category filter and test button. Without the plugin the tab just points you at it. The in-app notification bell records every event regardless.

Not in Settings ​

A few things people look for here live elsewhere:

• Schedules. Every scheduled job — releases check, ComicVine match, RSS watch, new-release search, wanted backfill, zero-day pack, database backup — is configured on System → Jobs, with a cron expression, an enable toggle, its last-run result and a Run now button. See Automation.
• Accounts, roles and self-registration. The Users page owns all of it, including the Allow self-registration switch. See Users & access.
• Deployment options. A handful of things are set as environment variables where you run the app rather than in Settings, because they have to be known before the app starts. See Environment variables below.

Legacy keys from older versions (libraryDir, nzbClientUrl, hour-based schedule fields, per-source FlareSolverr URLs) are still read and migrated automatically — you never need to touch them.

Environment variables ​

These are set where the app runs — the environment: block in a Compose file, -e flags on docker run, or your shell when running from source. Nothing here appears in Settings, because it has to be known before the app starts.

The usual ones ​

Most installs set these four and nothing else. The first three are read by the container's startup script rather than the app itself, so they only apply to Docker.

The defaults are Unraid's nobody:users. On first start, or whenever the ids change, the container takes ownership of the data directory before dropping to that user.

Paths ​

The two path overrides exist mainly so a from-source install can put plugins somewhere other than the app folder. In Docker they are already correct.

Behind a reverse proxy ​

TRUST_PROXY is the one variable people most often need and most often get wrong. It decides whether the app believes the X-Forwarded-For header, which in turn decides what it thinks each client's address is.

Two things depend on getting this right. Rate limiting counts failed logins per client address, so with this unset behind a proxy every request looks like it comes from the proxy and one person's bad password locks out the household. And the app uses it to decide whether a request arrived over HTTPS, which controls whether the session cookie is marked secure.

Occasionally useful ​

Leave these alone ​

BACKISSUE_ALLOW_INTERNAL_FETCH, METADATA_BASE_OVERRIDE, BACKISSUE_BUILD_FILE, BUILD_CHANNEL, BUILD_SHA, LD_PRELOAD and MALLOC_ARENA_MAX are development, build and memory-tuning hooks. The build ones are stamped into the image and only make the app misreport its own version if you override them; the memory ones are set by the container for good reasons and overriding them can break image handling.

One deserves a specific warning. BACKISSUE_ALLOW_INTERNAL_FETCH disables the guard that stops download sites fetching private and internal addresses. Those URLs come from scraped pages and search results, so switching the guard off hands untrusted content a route into your own network.

There is no port variable ​

The app always listens on 8787. To serve it elsewhere, remap the port on the host rather than changing the app:

ports:
  - "9000:8787"   # reach it on 9000