Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sailing:nzbget [2023/12/05 18:17] – willy | sailing:nzbget [2024/02/27 12:35] (current) – removed willy | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Prev to: [[sailing: | ||
- | Next to: [[sailing: | ||
- | ---- | ||
- | |||
- | ====== NzbGet ====== | ||
- | |||
- | [[https:// | ||
- | |||
- | ===== Installation ===== | ||
- | |||
- | NzbGet has an ebuild for Gentoo, so installing it it's a simple emerge: | ||
- | <code bash> | ||
- | > emerge -v nzbget | ||
- | </ | ||
- | |||
- | As usual move the home folder to **/ | ||
- | <code bash> | ||
- | > usermod -m -d / | ||
- | </ | ||
- | |||
- | and add the //nzbget// user to the media group: | ||
- | <code bash> | ||
- | > usermod -a -G media nzbget | ||
- | </ | ||
- | |||
- | One last required step is to ensure that the other tools can access the nzbget folder (to reach the download folders inside), so: | ||
- | <code bash> | ||
- | > chgrp media / | ||
- | </ | ||
- | |||
- | To be more consistent, and to prevent future overwrite onupgrade, you should move the default configuration file for //nzbgetd// to the nzbget home folder too: | ||
- | <code bash> | ||
- | > mv / | ||
- | </ | ||
- | |||
- | You need to do some fine tuning to the **/ | ||
- | < | ||
- | # Which user to run nzbget as | ||
- | NZBGET_USER=" | ||
- | NZBGET_GROUP=" | ||
- | # Location of config file | ||
- | NZBGET_CONFIGFILE="/ | ||
- | </ | ||
- | |||
- | Note that you have: | ||
- | * replaced the default group for the daemon to //media// | ||
- | * specified the new location for the configuration file | ||
- | |||
- | ==== Reverse-Proxy configuration ==== | ||
- | |||
- | Before you proceed, you should make NzbGet web accessible via the reverse-proxy, | ||
- | |||
- | Add this file to / | ||
- | <file txt nzbget.conf> | ||
- | # NZB Get | ||
- | location ~ ^/ | ||
- | rewrite / | ||
- | proxy_pass http:// | ||
- | proxy_set_header Host $host; | ||
- | proxy_set_header X-Real-IP $remote_addr; | ||
- | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; | ||
- | } | ||
- | location ~ ^/nzbget$ { | ||
- | return 302 $scheme:// | ||
- | } | ||
- | </ | ||
- | |||
- | Add this to your / | ||
- | < | ||
- | include " | ||
- | </ | ||
- | |||
- | and restart nginx: | ||
- | <code bash> | ||
- | > / | ||
- | </ | ||
- | |||
- | === Startup === | ||
- | |||
- | Now, setup the daemon to start at boot, and start it now: | ||
- | <code bash> | ||
- | > rc-update add nzbget default | ||
- | > / | ||
- | </ | ||
- | |||
- | ===== Integration ===== | ||
- | |||
- | Every download client needs to be integrated in your other tools. Unfortunately, | ||
- | |||
- | Every *Arr's tool has the same // | ||
- | |||
- | Prowlarr is a special case: you only need to define the downloader IF you plan to search from the Prowlarr web GUI, otherwise it's not needed. And no, Prowlarr will **not** synchronize your downloader to the other *Arr' | ||
- | |||
- | |||
- | ===== Usage ===== | ||
- | |||
- | Head to [[http:// | ||
- | |||
- | You will need to add here your Usenet access providers under // | ||
- | |||
- | You should now head to the Media Server installation, | ||
- | |||
- | ---- | ||
- | Next to: [[sailing: | ||
- | |||
- | Prev to: [[sailing: |