Linux
Linux repository hosting provided by
This works on any system with apt
or yum
. If your system does not use APT or YUM, download a binary from the Releases page and install it.
Important
On Linux, Notifiarr runs as user:group
of notifiarr:notifiarr
.
-
Install the Go Lift package repo and Notifiarr with this command:
curl -s https://golift.io/repo.sh | sudo bash -s - notifiarr
-
After install, edit the config, set your apikey, and restart the service:
sudo nano /etc/notifiarr/notifiarr.conf sudo systemctl restart notifiarr
Info
Arch Linux
- This one is special; hope you know what you're doing.
- Build a package with
makepkg
using theaur
source
Info
FreeBSD
- Download a
txz
package from the Releases page. - Install it, edit config, start it.
- On FreeBSD, Notifiarr runs as
user:group
ofnotifiarr:notifiarr
.
Example of the above in shell form:
wget -qO- https://raw.githubusercontent.com/Notifiarr/notifiarr/main/userscripts/install.sh | sudo bash
vi /usr/local/etc/notifiarr/notifiarr.conf
service notifiarr start
Info
TrueNAS Scale
TrueNAS
Please be aware none of us (Devs, Suppprt, etc.) use this but hopefully for those who do this is helpful.
- Consider moving away from TrueNAS Scale, and more specifically you must move away from TrueCharts for Notifiarr as Notifiarr v0.7.1 is broken / unsupported and TrueCharts will not upgrade the chart.
- The next TrueNAS Scale OS release will no longer support TrueCharts after their next OS release in 3 months (~10/2024)
For additional information:
- Please see some commentary and screenshots on the Notifiarr Discord
- Refer to TrueNAS Forums as to why TrueCharts Team are no longer updating their apps
- Be weary of asking for TrueCharts support in the TrueNAS Discord. Per Reddit: Users have been banned
- No current TrueNAS Scale users have been able to to write documentation for Notifiarr.
- Heavy's Guide is depreciated and will eventually be removed. It may stop working or be out of date at any time.
macOS
macOS App
Note
This is the recommend installation method for macOS.
- Download the signed
dmg
file from the Releases page. - When you open it for the first time it will create a config file and log file:
~/.notifiarr/notifiarr.conf
~/.notifiarr/notifiarr.log
- Edit the config file and reload or restart the app from the menu bar.
Info
Homebrew
Homebrew users
Homebrew is not recommend, and may be discontinued in the future.
- Install Notifiarr
- Edit config file at
/usr/local/etc/notifiarr/notifiarr.conf
- Start it.
The above in shell form:
brew install golift/mugs/notifiarr
vi /usr/local/etc/notifiarr/notifiarr.conf
brew services start notifiarr
Windows
Info
Suggested location and structure based on expierence with permissions
Desired Outcome
C:\ProgramData\notifiarr\notifiarr.amd64.exe
- The ApplicationC:\ProgramData\notifiarr\notifiarr.conf
- The config file. Should only be used to configure the apikey and enable the webui.C:\ProgramData\notifiarr\logs
- Folder for log files
Create the folders
- Open C:\ProgramData and create a folder
notifiarr
- Create a new folder named
logs
, so you now haveC:\ProgramData\notifiarr\logs
- When you add the log paths in the client UI (later steps), make sure you point them to a file such as:
C:\ProgramData\notifiarr\logs\app.log
C:\ProgramData\notifiarr\logs\debug.log
C:\ProgramData\notifiarr\logs\http.log
If this is a new install
- Download
notifiarr.amd64.exe.zip
from the Releases page - Save it in
C:\ProgramData\notifiarr
- Open the folder that was created from extracting and copy the
.exe
+ example.conf
files up one directory so it is located at:C:\ProgramData\notifiarr\notifiarr.amd64.exe
C:\ProgramData\notifiarr\notifiarr.conf.example
- You can now delete the
.zip
file that was downloaded and the folder that was extracted - Rename
notifiarr.conf.example
tonotifiarr.conf
If this is an existing install being "fixed"
- Stop the client
- Copy the existing
.exe
toC:\ProgramData\notifiarr\notifiarr.amd64.exe
- Copy the existing conf file to
C:\ProgramData\notifiarr\notifiarr.conf
- If the
C:\users\<your home folder>\.notifiarr
folder exists, delete it
New and existing installs
-
At this point, the structure should look like the Desired Outcome mentioned above.
-
Right click on the
.exe
and create a shortcut- Windows 11 users:
- Right click on the shortcut and pick properties
- Change the target path to
C:\Windows\System32\conhost.exe C:\ProgramData\notifiarr\notifiarr.amd64.exe
which will minimize the console to the tray when it is ran
- Windows 11 users:
- Windows logo key + R, type
shell:startup
, then select OK. This opens the Startup folder. - Copy and paste the newly created shortcut from its current location to the opened Startup folder.
- Double click on the shortcut and the client is now running
- If this is the first time you have ran it:
- Option A: Look at the notifiarr.log (or app.log) and you will see a the credentials in the log
- Option B: Right click on the notifiarr icon and pick Logs -> View and get the login credentials from there
- Option C: Open the notifiarr.conf and look at the top for
ui_password
to get the credentials
Info
Synology
- Run the below command while ssh'd in to the NAS. It will run the Syno Install Script located on the Notifiarr Repository
curl -sSL https://raw.githubusercontent.com/Notifiarr/notifiarr/main/userscripts/install-synology.sh | sudo bash
Info
Docker
This project builds automatically in Docker Cloud and creates ready-to-use multi-architecture images. The latest
tag is always a tagged release in GitHub.
Compose
A sample docker compose file may be found in the Github repo here.
Unraid Users
You must configure a Notifiarr API Key in the Unraid Template. If you wish to use Plex then you'll also need to set the Plex Token and Plex URL in the template as well.
Docker Users
Note that Docker Environmental Variables - and thus the Unraid Template - override the Config file.
Docker Config File
- Copy the example config file from Notifiarr Client repo.
- Then grab the image from docker hub and run it.
- You must enable
privileged
to usesmartctl
(monitor_drives
) and/orMegaCli
(monitor_raid
). - Map the
/var/run/utmp
volume if you want to count users. - Mount any volumes you want to report storage space for. Where does not matter, "where" is the "name". e.g.
/mnt/nas/data:/synonas
Warning
You MUST set a static hostname Each client is identified by hostname.
docker pull golift/notifiarr
docker run --name notifiarr -h notifiarr --restart unless-stopped --privileged -p 5454:5454 -v /path/to/notifiarrconfig/:/config -v /var/run/utmp:/var/run/utmp -v /etc/machine-id:/etc/machine-id golift/notifiarr
docker logs notifiarr
Docker Environment Variables
See below for more information about which environment variables are available.
docker pull golift/notifiarr
docker run --hostname $(hostname) -d --privileged \
-v /var/run/utmp:/var/run/utmp \
-e "DN_API_KEY=abcdef-12345-bcfead-43312-bbbaaa-123" \
-e "DN_SONARR_0_URL=http://localhost:8989" \
-e "DN_SONARR_0_API_KEY=kjsdkasjdaksdj" \
golift/notifiarr
docker logs <container id from docker run>
Home Assistant OS
Home Assistant OS Users
Please be aware none of us (Devs, Support, etc.) use this but hopefully for those who do this is helpful.
Home Assistant Addon, the person to ask for help is @ZanY
on the Notifiarr discord (if they are no longer a member, try their Github)
Proxmox
Proxmox Users
Please be aware none of us (Devs, Support, etc.) use this but hopefully for those who do this is helpful.
- Proxmox Helper script provided by the community
UltraCC Seedbox
UltraCC Seedbox Users
Please be aware none of us (Devs, Support, etc.) use this but hopefully for those who do this is helpful.
- SSH into your Ultra Seedbox
- On your landing directory type
mkdir notifiarr
- Type
cd notifiarr
- On Github find the latest release asset labelled notifiarr.amd64.linux.gz, right click on that and click copy link.
- Back on your terminal type
wget '<paste link>'
- Type
gzip -d notifiarr.*
- Type
mv notifiarr.* notifiarr
- Type
chmod +x notifiarr
- In the notifiarr folder create notifiarr.conf from this: Github page
- Type
cd /home/$USER/.config/systemd/user
- Type
nano notifiarr.service
- Paste the below
# Systemd service unit for notifiarr.
[Unit]
Description=notifiarr - Official chat integration client for Notifiarr.com
[Service]
ExecStart=/home/$USER/notifiarr/notifiarr \$DAEMON_OPTS
Restart=always
RestartSec=10
Type=simple
WorkingDirectory=/home/$USER/notifiarr
Environment=DN_LOG_FILE/home/$USER/notifiarr/app.log
Environment=DN_HTTP_LOG=/home/$USER/notifiarr/http.log
Environment=DN_DEBUG_LOG=/home/$USR/notifiarr/debug.log
Environment=DN_SERVICES_LOG_FILE=/home/$USER/notifiarr/services.log
Environment=DN_QUIET=true
[Install]
WantedBy=default.target
- Type
systemctl --user enable notifiarr
- Type
systemctl --user start notifiarr
- Type
systemctl --user status notifiarr
to check if there are any errors. - On your browser go to http://[ultraseedbox url]:5454
- Log into your Notifarr client and change the base url to /notifiarr and save changes
- Go back to your ssh console
- Type
cd /home/$USER/.apps/nginx/proxy.d
- Type
nano notifiarr.conf
- Paste the below
location /notifiarr {
# <put proxy auth directives here> Optional:
# proxy_set_header X-WebAuth-User $auth_user;
proxy_set_header X-Forwarded-For $remote_addr;
set $notifiarr http://127.0.0.1:5454;
proxy_pass $notifiarr$request_uri;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_set_header Host $host;
}
# Notifiarr Client
location /notifiarr/api {
deny all; # remove this line if you really want to expose the API.
proxy_set_header X-Forwarded-For $remote_addr;
set $notifiarr http://127.0.0.1:5454;
proxy_pass $notifiarr$request_uri;
}
- Type
systemctl --user restart nginx
- Now you should be able to browse to https://[ultraseedbox url]/notifiarr