Where Does Notifiarr Store Its Config?
Notifiarr reads notifiarr.conf for its API key and *arr connections. Docker mounts it at /config; Linux packages use /etc/notifiarr.
Last updated
Notifiarr configures through notifiarr.conf: the API key from Notifiarr.com plus URLs and keys for Sonarr, Radarr, Plex, and snapshot monitoring. Docker mounts a host folder at /config and the app writes a fresh config there on first run, after which the WebUI asks for the API key. Package installs on Linux use /etc/notifiarr/notifiarr.conf with logs under /var/log/notifiarr.
Two operational details bite newcomers. The client needs a stable hostname or every recreate looks like a new machine. Privileged mode plus /var/run/utmp and /etc/machine-id mounts enable user and drive monitoring; without them those features silently report nothing. Env variables override file values, which helps for secrets in compose.
Where Notifiarr stores this, by platform
/config/notifiarr.conf (Docker)
API key plus *arr and snapshot blocks. Fresh mounts get a generated file; add the key through the WebUI, then set a local password under Trust Profile. Keep hostname static across recreates.
/etc/notifiarr/notifiarr.conf
Same file via the Linux package, created with the install. Logs go to /var/log/notifiarr. Edit with sudo and restart the service. Package installs run as the notifiarr user.
Frequently asked questions
how do i migrate notifiarr to a new server
Copy notifiarr.conf and mount it at the same container path on the new host, keeping the static hostname. The API key binds the client to your Notifiarr.com account, so protect the file and re-enter the key through the WebUI if it prompts.
why does notifiarr show duplicate clients
Set a static hostname (docker run -h or compose hostname:). Each client identifies by hostname, and a random one on every recreate registers endless duplicate clients in your account.
Notice an outdated path? Let us know.