finish jellyfin entry, made some tweaks, fixes to qbittorrent entry

2 files changed, 63 insertions, 437 deletions

diff --git a/src/blog/temp/jellyfin_server_with_sonarr_radarr.md b/src/blog/a/jellyfin_server_with_sonarr_radarr.md
index 60251a7..5d5cc15 100644
--- a/src/blog/temp/jellyfin_server_with_sonarr_radarr.md
+++ b/src/blog/a/jellyfin_server_with_sonarr_radarr.md
@@ -1,20 +1,18 @@
-title: Set up a media server with Jellyfin, Sonarr and Radarr
+title: Set up a media server with Jellyfin with Sonarr and Radarr
 author: David Luévano
 lang: en
-summary: How to set up a media server with Jellyfin, Sonarr and Radarr, on Arch. With qBitTorrent, Jackett, flaresolverr and Bazarr, too.
+summary: How to set up a media server with Jellyfin with Sonarr and Radarr, on Arch. With Bazarr, too.
 tags: server
 	tools
 	code
 	tutorial
 	english
 
-Riding on my excitement of having a good internet connection and having setup my *home server* now it's time to self host a media server for movies, series and anime. I'll be exposing my stuff on a subdomain only so I can access it while out of home and for SSL certificates (not required), but shouldn't be necessary and instead you can use a VPN ([how to set up](https://blog.luevano.xyz/a/vpn_server_with_openvpn.html)). For your reference, whenever I say "Starr apps" (\*arr apps) I mean the family of apps such as Sonarr, Radarr, Readarr, Lidarr, etc..
-
-Most of my config is based on the [TRaSH-Guides](https://trash-guides.info/) (will be mentioned as "TRaSH" going forward). Specially get familiar with the [TRaSH: Native folder structure](https://trash-guides.info/Hardlinks/How-to-setup-for/Native/) and with the [TRaSH: Hardlinks and instant moves](https://trash-guides.info/Hardlinks/Hardlinks-and-Instant-Moves/). Will also use the default configurations based on the respective documentation for each Starr application and service, except when stated otherwise.
+Second part of my self hosted media server. This is a direct continuation of [Set up qBitTorrent with Jackett for use with Starr apps](https://blog.luevano.xyz/a/torrenting_with_qbittorrent.html), which will be mentioned as "first part" going forward. Sonarr, Radarr, Bazarr (Starr apps) and Jellyfin setups will be described in this part. Same introduction applies to this entry, regarding the use of documentation and configuration.
 
 Everything here is performed in ==arch btw== and all commands should be run as root unless stated otherwise.
 
-==Also kindly note that I do not condone the use of BitTorrent for illegal activities. I take no responsibility for what you do when setting up anything shown here. It is for you to check your local laws before using automated downloaders such as Sonarr and Radarr.==
+==Kindly note that I do not condone the use of BitTorrent for illegal activities. I take no responsibility for what you do when setting up anything shown here. It is for you to check your local laws before using automated downloaders such as Sonarr and Radarr.==
 
 # Table of contents
 
@@ -22,379 +20,13 @@ Everything here is performed in ==arch btw== and all commands should be run as r
 
 # Prerequisites
 
-The specific programs are mostly recommendations, if you're familiar with something else or want to change things around, feel free to do so but everything will be written with them in mind.
-
-If you want to expose to a (sub)domain, then similar to my early [tutorial](https://blog.luevano.xyz/tag/@tutorial.html) entries (specially the [website](https://blog.luevano.xyz/a/website_with_nginx.html) for the reverse proxy plus certificates):
-
-- `nginx` for the reverse proxy.
-- `certbot` for the SSL certificates.
-- `ufw` for the firewall.
-- `yay` to install AUR packages.
-    - I mentioned how to install and use it on my previous entry: [Manga server with Komga: yay](https://blog.luevano.xyz/a/manga_server_with_komga.html#yay).
-- An **A** (and/or **AAAA**) or a **CNAME** for `jellyfin`.
-    - Optionally, another one for all automation software (Jackett, Starr apps, etc.). You can use one subdomain per service, but I'll put them all under `isos` in the examples shown.
-
-## Directory structure
-
-Basically following [TRaSH: Native folder structure](https://trash-guides.info/Hardlinks/How-to-setup-for/Native/) except for the directory permissions part, I'll do the same as with my [Komga setup guide](https://blog.luevano.xyz/a/manga_server_with_komga#set-default-directory-permissions.html) to stablish default group permissions.
-
-
-The desired behaviour is: set `servarr` as group ownership, set write access to group and whenever a new directory/file is created, inherit these permission settings. `servarr` is going to be a service user and I'll use the root of a mounted drive at `/mnt/a`.
-
-1. Create a service user called `servarr` (it could just be a group, too):
-
-```sh
-useradd -r -s /usr/bin/nologin -M -c "Servarr applications" servarr
-```
-
-2. Create the `torrents` directory and set default permissions:
-
-```sh
-cd /mnt/a # change this according to your setup
-mkdir torrents
-chown servarr:servarr torrents
-chmod g+w torrents
-chmod g+s torrents
-setfacl -d -m g::rwx torrents
-setfacl -d -m o::rx torrents
-```
-
-3. Check that the permissions are set correctly (`getfacl torrents`)
-
-```
-# file: torrents/
-# owner: servarr
-# group: servarr
-# flags: -s-
-user::rwx
-group::rwx
-other::r-x
-default:user::rwx
-default:group::rwx
-default:other::r-x
-```
-
-4. Create the subdirectories you want with any user (I'll be using `servarr` personally):
-
-```sh
-mkdir torrents/{tv,movies,anime}
-chown -R servarr: torrents
-```
-
-5. Finally repeat steps 2 - 4 for the `media` directory.
-
-The final directory structure should be the following:
-
-```
-root_dir
-├── torrents
-│   ├── movies
-│   ├── music
-│   └── tv
-└── media
-    ├── movies
-    ├── music
-    └── tv
-```
-
-Where `root_dir` is `/mnt/a` in my case. This is going to be the reference for the following applications set up.
-
-Later, add the necessary users to the `servarr` group if they need write access, by executing:
-
-```sh
-gpasswd -a <USER> servarr
-```
-
-# Jackett
-
-[Jackett](https://github.com/Jackett/Jackett) is a "proxy server" (or "middle-ware") that translates queries from apps (such as the Starr apps in this case) into tracker-specific http queries. Note that there is an alternative called [Prowlarr](https://github.com/Prowlarr/Prowlarr) that is better integrated with most if not all Starr apps, requiring less maintenance; I'll still be sticking with Jackett, though.
-
-Install from the AUR with `yay`:
-
-```sh
-yay -S jackett
-```
-
-I'll be using the default `9117` port, but change accordingly if you decide on another one.
-
-## Reverse proxy
-
-I'm going to have most of the services under the same subdomain, with different subdirectories. Create the config file `isos.conf` at the usual `sites-available/enabled` path for `nginx`:
-
-```nginx
-server {
-	listen 80;
-    server_name isos.yourdomain.com;
-
-    location /jack { # you can change this to jackett or anything you'd like, but it has to match the jackett config on the next steps
-        proxy_pass http://localhost:9117; # change the port according to what you want
-
-        proxy_set_header X-Real-IP $remote_addr;
-        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-        proxy_set_header X-Forwarded-Proto $scheme;
-        proxy_set_header X-Forwarded-Host $http_host;
-        proxy_redirect off;
-    }
-}
-```
-
-This is the basic reverse proxy config as shown in [Jackett: Running Jackett behind a reverse proxy](https://github.com/Jackett/Jackett#running-jackett-behind-a-reverse-proxy). The rest of the services will be added under different `location` block on their respective steps.
-
-### SSL certificate
-
-Create/extend the certificate by running:
-
-```sh
-certbot --nginx
-```
-
-That will automatically detect the new subdomain config and create/extend your existing certificate(s). Restart the `nginx` service for changes to take effect:
-
-```sh
-systemctl restart nginx.service
-```
-
-## Start using Jackett
-
-You can now `start`/`enable` the `jackett.service`:
-
-```sh
-systemctl enable jackett.service
-systemctl start jackett.service
-```
-
-It will autocreate the default configuration under `/var/lib/jackett/ServerConfig.json`, which we need to edit at least to change the `BasePathOverride` to match what we used in the `nginx` config:
-
-```json
-{
-	"Port": 9117,
-	"SomeOtherConfigs": "some_other_values",
-	"BasePathOverride": "/jack",
-	"MoreConfigs": "more_values",
-}
-```
-
-Also modify the `Port` if you changed it. Restart the `jackett` service:
-
-```sh
-systemctl restart jackett.service
-```
-
-It should now be available at `https://isos.yourdomain.com/jack`. Add an admin password right away by scroll down and until the first config setting; don't forget to click on "Set Password". You can change any other config you want from the Web UI, too (you'll need to click on "Apply server settings").
-
-### Indexers
-
-For Jackett, an indexer is just a configured tracker for some of the commonly known torrent sites. Jackett comes with a lot of pre-configured public and private indexers which usually have multiple URLs (mirrors) per indexer, useful when the main torrent site is down. Some indexers come with extra features/configuration depending on what the site specializes on.
-
-To add an indexer click on the "+ Add Indexer" at the top of the Web UI and look for indexers you want, then click on the "+" icon on the far-most right for each indexer or select the ones you want (clicking on the checkbox on the far-most left of the indexer) and scroll all the way to the bottom to click on "Add Selected". They then will show as a list with some available actions such as "Copy RSS Feed", "Copy Torznab Feed", "Copy Potato Feed", a button to search, configure, delete and test the indexer, as shown below:
-
-![Jacket: configured indexers](${SURL}/images/b/jack/jack_configured_indexers.png "Jackett: configured indexers")
-
-You can manually test the indexers by doing a basic search to see if they return anything, either by searching on each individual indexer by clicking on the magnifying glass icon on the right of the indexer or clicking on "Manual Search" button which is next to the "+ Add Indexer" button at the top right.
-
-Explore each indexer's configuration in case there is stuff you might want to change.
-
-## FlareSolverr
-
-[FlareSolverr](https://github.com/FlareSolverr/FlareSolverr) is used to bypass *certain* protection that some sites have. This is not 100% necessary and only needed for some trackers sometimes.
-
-You could install from the AUR with `yay`:
-
-```sh
-yay -S flaresolverr
-```
-
-But at the time of writing, the package wont work for the following reasons:
+Same prerequisites as with the [First part: Prerequisites](https://blog.luevano.xyz/a/torrenting_with_qbittorrent.html#prerequisites) plus:
 
-- The `python-selenium` package that it requires doesn't build (actually it just doesn't pass the tests).
-- The `python-selenium` package is a higher version than the required by `flaresolverr`, and it's a breaking change version (they don't follow semantic versioning), so even if you are able to install `python-selenium` (by just removing the checks) it will still fail due to this check.
+- An **A** (and/or **AAAA**) or a **CNAME** for `jellyfin`. Only if you want to expose Jellyfin to a subdomain.
 
-### Manual installation
+The [First part: Directory structure](https://blog.luevano.xyz/a/torrenting_with_qbittorrent.html#directory-structure) is the same here. The `servarr` user and group should be available, too.
 
-For now the best next thing is to manually set it up using a python virtual environment. I'll be taking some elements from the AUR package. Only package requirements are `chromium` and `xorg-server-xvfb`, needed for the `selenium` webdriver and a virtual X server.
-
-Install dependencies via pacman:
-
-```sh
-pacman -S chromium xorg-server-xvfb
-```
-
-Create a new service user called `flaresolverr` ([flaresolverr.sysusers](https://aur.archlinux.org/cgit/aur.git/tree/flaresolverr.sysusers?h=flaresolverr)):
-
-```sh
-useradd -r -s /usr/bin/nologin -c "FlareSolverr" -d "/opt/flaresolverr" flaresolverr
-```
-
-Clone the [FlareSolverr](https://github.com/FlareSolverr/FlareSolverr) git repo in `/opt` and get inside it:
-
-```sh
-cd /opt
-git clone git@github.com:FlareSolverr/FlareSolverr.git
-mv FlareSolverr/ flaresolverr
-cd flaresolverr
-```
-
-Create a python environment called `.venv`, activate it and install the requirements:
-
-```sh
-python -m venv .venv
-source .venv/bin/activate
-pip install --upgrade pip
-pip install -r requirements.txt
-```
-
-Finally just change the ownership of the `/opt/flaresolverr` directory:
-
-```sh
-chown -R flaresolverr:flaresolverr /opt/flaresolverr/
-```
-
-#### Creating a systemd service
-
-You could just execute `python src/flaresolverr.py` while in the python virtual environment, but we want it as a service. Create a systemd service file `flaresolverr.service` ([flaresolverr.service](https://aur.archlinux.org/cgit/aur.git/tree/flaresolverr.service?h=flaresolverr) with few modifications) in `/etc/systemd/system`:
-
-```ini
-[Unit]
-Description=FlareSolverr
-After=network.target
-
-[Service]
-SyslogIdentifier=flaresolverr
-Restart=always
-RestartSec=5
-Type=simple
-User=flaresolverr
-Group=flaresolverr
-Environment="LOG_LEVEL=info"
-Environment="CAPTCHA_SOLVER=none"
-WorkingDirectory=/opt/flaresolverr
-ExecStart=/opt/flaresolverr/.venv/bin/python /opt/flaresolverr/src/flaresolverr.py # note the venv python and that it uses the "src" directory for the git repo
-TimeoutStopSec=30
-
-[Install]
-WantedBy=multi-user.target
-```
-
-We can now `start`/`enable` the `flaresolverr.service`:
-
-```sh
-systemctl enable flaresolverr.service
-systemctl start flaresolverr.service
-```
-
-You can check that the service started correctly by checking the logs:
-
-```sh
-journalctl -fxeu flaresolverr
-```
-
-It should show "Test successful" and "Serving on http://0.0.0.0:8191" (which is the default). Jackett will need to be configured if FlareSolverr is served on anything different than the default.
-
-==Note that since this was a manual setup, if `python` gets updated it will probably break the virtual environment (just re-do that part). If FlareSolverr gets updated, you might need to stash the changes (because of the service file) and do a git pull (probably install the requirements again, too). Until the AUR packages are fixed, at least.==
-
-# qBitTorrent
-
-[qBitTorrent](https://wiki.archlinux.org/title/QBittorrent) is a fast, stable and light BitTorrent client that comes with many features and in my opinion it's a really user friendly client and my personal choice for years now. But you can choose whatever client you want, there are more lightweight alternatives such as [Transmission](https://wiki.archlinux.org/title/transmission).
-
-Install the headless `qbittorrent` package ("nox" as in "no X server"):
-
-```sh
-pacman -S qbittorrent-nox
-```
-
-By default the package doesn't install any (service) user, but it is recommended to have one so we can run the service under it. Create the user, I'll call it `qbittorrent` and leave it with the default homedir (`/home`):
-
-```sh
-useradd -r -m qbittorrent
-```
-
-==Add the `qbittorrent` user to the `servarr` group:==
-
-```sh
-gpasswd -a qbittorrent servarr
-```
-
-Decide a port number you're going to run the service on for the next steps, the default is `8080` but I'll use `30000`; it doesn't matter much, as long as it matches for all the config.
-
-## Reverse proxy
-
-Add the following `location` block into the `isos.conf` with whatever subdirectory name you want, I'll call it `qbt`:
-
-```nginx
-location /qbt/ {
-    proxy_pass http://localhost:30000/; # change port to whatever number you want
-    proxy_http_version 1.1;
-
-    proxy_set_header Host $host;
-    proxy_set_header X-Forwarded-Host $http_host;
-    proxy_set_header X-Forwarded-For $remote_addr;
-
-    proxy_cookie_path / "/; Secure";
-    proxy_read_timeout 600s;
-    proxy_send_timeout 600s;
-}
-```
-
-This is taken from [qBitTorrent: Nginx reverse proxy for Web UI](https://github.com/qbittorrent/qBittorrent/wiki/NGINX-Reverse-Proxy-for-Web-UI). Restart the `nginx` service for the changes to take effect:
-
-```sh
-systemctl restart nginx.service
-```
-
-## Start using qBitTorrent
-
-You can now `start`/`enable` the `qbittorrent-nox@.service` using the service account created (`qbittorrent`):
-
-```sh
-systemctl enable `qbittorrent-nox@qbittorrent.service
-systemctl start `qbittorrent-nox@qbittorrent.service
-```
-
-This will start `qbittorrent` using default config. We need to change the port (in my case to `30000`) and set `qbittorrent` to restart on exit (the Web UI has a close button). I guess this can be done before enabling/starting the service, but either way let's create a "drop-in" file by "editing" the service:
-
-```sh
-systemctl edit `qbittorrent-nox@qbittorrent.service
-```
-
-Which will bring up a file editing mode containing the service unit and a space where we can add/override anything, add:
-
-```ini
-[Service]
-Environment="QBT_WEBUI_PORT=30000" # or whatever port number you want
-Restart=on-success
-RestartSec=5s
-```
-
-When saving and exiting from the file it will create the override config. Restart the service for changes to take effect (it might ask to also reload the systemd deamon or something like that):
-
-```sh
-systemctl restart `qbittorrent-nox@qbittorrent.service
-```
-
-You can now head to `https://isos.yourdomain.com/qbt/` and login with user `admin` and password `adminadmin` (by default). Change the default password right away by going to *Tools -> Options -> Web UI -> Authentication*. The Web UI is basically the same as the normal desktop UI so if you've used it it will feel familiar. From here you can threat it as a normal torrent client and even start using for other stuff other than the specified here.
-
-### Configuration
-
-It should be usable already but we can go further and fine tune it, specially to some kind of "convention" as shown in [TRaSH: qBitTorrent basic setup](https://trash-guides.info/Downloaders/qBittorrent/Basic-Setup/) and subsequent `qbittorrent` guides.
-
-I use all the suggested settings, where the only "changes" are for personal paths, ports, and in general connection settings that depend on my setup. The only super important setting I noticed that can affect our setup (meaning what is described in this entry) is the *Web UI -> Authentication* for the "Bypass authentication for clients on localhost". This will be an issue because the reverse proxy is accessing `qbittorrent` via the localhost, so this will make the service open to the world, experiment at your own risk.
-
-Finally, add categories by following [TRaSH: qBitTorrent how to add categories](https://trash-guides.info/Downloaders/qBittorrent/How-to-add-categories/). I added 3: `tv`, `movies` and `anime`.
-
-### Trackers
-
-Often some of the trackers that come with torrents are dead or just don't work. You have the option to add extra trackers to torrents either by:
-
-- Automatically add a predefined list on new torrents: configure at *Tools -> Options -> BitTorrent*, enable the last option "Automatically add these trackers to new downloads" then add the list of trackers. This should only be done on public torrents as private ones might ban you or something.
-- Manually add a list of trackers to individual torrents: configure by selecting a torrent, clicking on *Trackers* on the bottom of the Web UI, right clicking on an empty space and selecting "Add trackers..." then add the list of trackers.
-
-On both options, the list of trackers need to have at least one new line in between each new tracker. You can find trackers from the following sources:
-
-- [List of stable trackers](https://newtrackon.com/list)
-- [ngosang/trackerslist](https://github.com/ngosang/trackerslist)
-    - It also mentions [Third party tools](https://github.com/ngosang/trackerslist#third-party-tools) to automate this process.
-
-Both sources maintain an updated list of trackers. You also might need to enable an advanced option so all the new trackers are contacted ([Only first tracker contacted](https://github.com/qbittorrent/qBittorrent/issues/7882)): configure at *Tools -> Options -> Advanced -> libtorrent Section* and enable both "Always announce to all tiers" and "Always announce to all trackers in a tier".
+==It is assumed that the first part was followed.==
 
 # Radarr
 
@@ -412,15 +44,15 @@ yay -S radarr
 gpasswd -a radarr servarr
 ```
 
-The default port that Radarr uses is `7878` for http (the one we need for our reverse proxy).
+The default port that Radarr uses is `7878` for http (the one you need for the reverse proxy).
 
 ## Reverse proxy
 
 Add the following `location` blocks into the `isos.conf` with whatever subdirectory name you want, I'll leave it as `radarr`:
 
 ```nginx
-location /radarr {
-    proxy_pass http://localhost:7878; # change port if needed, this is the default
+location /radarr/ {
+    proxy_pass http://127.0.0.1:7878/radarr/; # change port if needed
     proxy_http_version 1.1;
 
     proxy_set_header Host $host;
@@ -435,7 +67,7 @@ location /radarr {
 # Allow the API External Access via NGINX
 location /radarr/api {
     auth_basic off;
-    proxy_pass http://localhost:7878; # change port if needed, this is the default
+    proxy_pass http://127.0.0.1:7878/radarr/api; # change port if needed
 }
 ```
 
@@ -454,7 +86,7 @@ systemctl enable radarr.service
 systemctl start radarr.service
 ```
 
-This will start the service and create the default configs under `/var/lib/radarr`. We need to change the `URLBase` as we're running the reverse proxy under a subdirectory (`/radarr`). Edit `/var/lib/radarr/config.xml`:
+This will start the service and create the default configs under `/var/lib/radarr`. You need to change the `URLBase` as the reverse proxy is under a subdirectory (`/radarr`). Edit `/var/lib/radarr/config.xml`:
 
 ```xml
 ...
@@ -468,7 +100,7 @@ Then restart the `radarr` service:
 systemctl restart radarr.service
 ```
 
-Now `https://isos.yourdomain.com/radarr` is accessible. Again go straight to secure the instance by adding authentication under *Settings -> General -> Security*. I added the "Forms" option, just fill in the username and password then click on save changes on the top left of the page. You can restart the service again and check that it asks for login credentials.
+Now `https://isos.yourdomain.com/radarr` is accessible. ==Secure the instance right away== by adding authentication under *Settings -> General -> Security*. I added the "Forms" option, just fill in the username and password then click on save changes on the top left of the page. You can restart the service again and check that it asks for login credentials.
 
 Note that if you want to have an anime movies library, it is recommended to run a second instance of Radarr for this as shown in [Radarr: Linux multiple instances](https://wiki.servarr.com/radarr/installation#linux-multiple-instances) and follow [TRaSH: How to setup quality profiles anime](https://trash-guides.info/Radarr/radarr-setup-quality-profiles-anime/) if an anime instance is what you want.
 
@@ -481,13 +113,13 @@ Anything that is not mentioned in either guide or that is specific to how I'm se
 #### Media Management
 
 - **File Management**:
-    - *Propers and Repacks*: set it to "Do Not Prefer" and instead we'll use the [Repack/Proper](https://trash-guides.info/Radarr/Radarr-collection-of-custom-formats/#repackproper) [custom format by TRaSH](https://trash-guides.info/Radarr/Radarr-collection-of-custom-formats).
+    - *Propers and Repacks*: set it to "Do Not Prefer" and instead you'll use the [Repack/Proper](https://trash-guides.info/Radarr/Radarr-collection-of-custom-formats/#repackproper) [custom format by TRaSH](https://trash-guides.info/Radarr/Radarr-collection-of-custom-formats).
 
 #### Quality
 
 This is personal preference and it dictates your preferred file sizes. You can follow [TRaSH: Quality settings](https://trash-guides.info/Radarr/Radarr-Quality-Settings-File-Size/) to maximize the quality of the downloaded content and restrict low quality stuff.
 
-Personally, I think TRaSH's quality settings are a bit elitist and first world-y. I'm fine with whatever, and the tracker I'm using has the quality I want anyways. I did, however, set it to a minimum of `0` and maximum of `400` for the qualities shown in TRaSH's guide. Configuring anything below `720p` shouldn't be necessary anyways.
+Personally, I think TRaSH's quality settings are a bit elitist and first world-y. I'm fine with whatever and the tracker I'm using has the quality I want anyways. I did, however, set it to a minimum of `0` and maximum of `400` for the qualities shown in TRaSH's guide. Configuring anything below `720p` shouldn't be necessary anyways.
 
 #### Custom Formats
 
@@ -507,12 +139,12 @@ Pretty straight forward, just click on the giant "+" button and click on the qBi
 
 - Name: can be anything, just an identifier.
 - Enable: enable it.
-- Host: use `localhost`. For some reason I can't make it work with the reverse proxied qBitTorrent.
+- Host: use `127.0.0.1`. For some reason I can't make it work with the reverse proxied qBitTorrent.
 - Port: the port number you chose, `30000` in my case.
-- Url Base: leave blank as even though we have it exposed under `/qbt`, the `localhost` service itself is not.
+- Url Base: leave blank as even though you have it exposed under `/qbt`, the service itself is not.
 - Username: the Web UI username, `admin` by default.
 - Password: the Web UI username, `adminadmin` by default (you should've changed it if you have the service exposed).
-- Category: `movies`. Not sure if this can be set on a per indexer basis, but for now I'm using it like this. If I need another category I think I'll have to "add another download client" (which would be the same just with different category).
+- Category: `movies`.
 
 Everything else can be left as default, but maybe change *Completed Download Handling* if you'd like. Same goes for the general *Failed Download Handling* download clients' option.
 
@@ -520,12 +152,12 @@ Everything else can be left as default, but maybe change *Completed Download Han
 
 Also easy to set up, also just click on the giant "+" button and click on the *custom* Torznab option (you can also use the *preset -> Jackett* Torznab option). Then configure:
 
-- Name: can be anything, just an identifier. I like to do "Jackett - indexer_name".
-- URL: `http://localhost:9117/api/v2.0/indexers/YOURINDEXER/results/torznab/`, where `YOURINDEXER` is what Jackett exposes. Can be looked at if you hover on the indexer's "Copy Torznab Feed" button on the Jackett Web UI, examples are `yts` and `thepiratebay`. Again, for some reason I can't directly use the reverse proxied Jackett.
+- Name: can be anything, just an identifier. I like to do "Jackett - INDEXER", where "INDEXER" is just an identifier.
+- URL: `http://127.0.0.1:9117/jack/api/v2.0/indexers/YOURINDEXER/results/torznab/`, where `YOURINDEXER` is specific to each indexer (`yts`, `nyaasi`, etc.). Can be directly copied from the indexer's "Copy Torznab Feed" button on the Jackett Web UI.
 - API Path: `/api`, leave as is.
-- API Key: this can be found at the top right corner in Jackett's Web UI. Copy/paste it.
+- API Key: this can be found at the top right corner in Jackett's Web UI.
 - Categories: which categories to use when searching, these are generic categories until you test/add the indexer. After you add the indexer you can come back and select your prefered categories (like just toggling the movies categories).
-- Tags: I like to add a tag for the "indexer_name" like `yts` or `tpb`. This is useful so I can control which indexers to use when adding new movies.
+- Tags: I like to add a tag for the indexer name like `yts` or `nyaa`. This is useful to control which indexers to use when adding new movies.
 
 Everything else on default. *Download Client* can also be set, which can be useful to keep different categories per indexer or something similar. *Seed Ratio* and *Seed Time* can also be set and are used to manage when to stop the torrent, this can also be set globally on the qBitTorrent Web UI, this is a personal setting.
 
@@ -538,20 +170,20 @@ I personally use:
 - Monitor: Movie Only.
 - Minimum Availability: Released.
 - Quiality Profile: "HD Bluray + WEB", the one configured in this entry.
-- Tags: the "indexer_name" I want to use to download the movie, usually just `yts` (remember this is a "LQ" so if you have that custom format set it might not download anything) as mentioned in [Indexers](#indexers-1). If you don't specify a tag it will use all indexers as far as I know.
+- Tags: the indexer name I want to use to download the movie, usually just `yts` for me (remember this is a "LQ" release group, so if you have that custom format disable it) as mentioned in [Indexers](#indexers). If you don't specify a tag it will only use indexers that don't have a tag set.
 - Start search for missing movie: toggled on. Immediatly start searching for the movie and start the download.
 
 Once you click on "Add Movie" it will add it to the *Movies* section and start searching and selecting the best torrent it finds, according to the "filters" (quality settings, profile and indexer(s)).
 
 When it selects a torrent it sends it to qBitTorrent and you can even go ahead and monitor it over there. Else you can also monitor at *Activity -> Queue*.
 
-After the movie is downloaded and processed by Radarr, it will create the appropriate hardlinks to the `media/movies` directory, as set in [Directory structure](#directory-structure).
+After the movie is downloaded and processed by Radarr, it will create the appropriate hardlinks to the `media/movies` directory, as set in [First part: Directory structure](https://blog.luevano.xyz/a/torrenting_with_qbittorrent.html#directory-structure).
 
 Optionally, you can add subtitles using [Bazarr](#bazarr).
 
 # Sonarr
 
-[Sonarr](https://sonarr.tv/) is a TV series collection manager that can be used to download series via torrents. As mentioned in [Radarr](#radarr). Most of the install process, configuration and whatnot is going to be basically the same as with Radarr.
+[Sonarr](https://sonarr.tv/) is a TV series collection manager that can be used to download series via torrents. Most of the install process, configuration and whatnot is going to be basically the same as with Radarr.
 
 Install from the AUR with `yay`:
 
@@ -565,17 +197,17 @@ yay -S sonarr
 gpasswd -a sonarr servarr
 ```
 
-The default port that Radarr uses is `8989` for http (the one we need for our reverse proxy).
+The default port that Radarr uses is `8989` for http (the one you need for the reverse proxy).
 
 ## Reverse proxy
 
-Basically the same as with [Radarr: Reverse proxy](#reverse-proxy-2), ==except that the `proxy_pass` (needs `/sonarr`) and the `proxy_set_header` (needs `$proxy_host` instead of `$host`) are different.==
+Basically the same as with [Radarr: Reverse proxy](#reverse-proxy), ==except that the `proxy_set_header` changes from `$proxy_host` to `$host`.==
 
 Add the following `location` blocks into the `isos.conf`, I'll leave it as `sonarr`:
 
 ```nginx
-location /sonarr {
-    proxy_pass http://localhost:8989/sonarr; # change port if needed
+location /sonarr/ {
+    proxy_pass http://127.0.0.1:8989/sonarr/; # change port if needed
     proxy_http_version 1.1;
 
     proxy_set_header Host $proxy_host; # this differs from the radarr reverse proxy
@@ -590,7 +222,7 @@ location /sonarr {
 # Allow the API External Access via NGINX
 location /sonarr/api {
     auth_basic off;
-    proxy_pass http://localhost:8989; # change port if needed
+    proxy_pass http://127.0.0.1:8989/sonarr/api; # change port if needed
 }
 ```
 
@@ -609,7 +241,7 @@ systemctl enable sonarr.service
 systemctl start sonarr.service
 ```
 
-This will start the service and create the default configs under `/var/lib/sonarr`. We need to change the `URLBase` as we're running the reverse proxy under a subdirectory (`/sonarr`). Edit `/var/lib/sonarr/config.xml`:
+This will start the service and create the default configs under `/var/lib/sonarr`. You need to change the `URLBase` as the reverse proxy is under a subdirectory (`/sonarr`). Edit `/var/lib/sonarr/config.xml`:
 
 ```xml
 ...
@@ -623,7 +255,7 @@ Then restart the `sonarr` service:
 systemctl restart sonarr.service
 ```
 
-Now `https://isos.yourdomain.com/sonarr` is accessible. Again go straight to secure the instance by adding authentication under *Settings -> General -> Security*. I added the "Forms" option, just fill in the username and password then click on save changes on the top left of the page. You can restart the service again and check that it asks for login credentials.
+Now `https://isos.yourdomain.com/sonarr` is accessible. ==Secure the instance right away== by adding authentication under *Settings -> General -> Security*. I added the "Forms" option, just fill in the username and password then click on save changes on the top left of the page. You can restart the service again and check that it asks for login credentials.
 
 Similar to [Radarr](#radarr) if you want to have an anime library, it is recommended to run a second instance of Sonarr for this as shown in [Sonarr: Linux multiple instances](https://wiki.servarr.com/sonarr/installation#linux-multiple-instances) and follow [TRaSH: Release profile regex (anime)](https://trash-guides.info/Sonarr/Sonarr-Release-Profile-RegEx-Anime/) and the [TRaSH: Anime recommended naming scheme](https://trash-guides.info/Sonarr/Sonarr-recommended-naming-scheme/#anime-episode-format) if an anime instance is what you want.
 
@@ -636,7 +268,7 @@ Anything that is not mentioned in either guide or that is specific to how I'm se
 #### Media Management
 
 - **File Management**:
-    - *Propers and Repacks*: set it to "Do Not Prefer" and instead we'll use the [Propers and Repacks](https://trash-guides.info/Sonarr/Sonarr-Release-Profile-RegEx/#propers-and-repacks) release profile and fill with [P2P Groups + Repack/Proper](https://trash-guides.info/Sonarr/Sonarr-Release-Profile-RegEx/#p2p-groups-repackproper).
+    - *Propers and Repacks*: set it to "Do Not Prefer" and instead you'll use the [Propers and Repacks](https://trash-guides.info/Sonarr/Sonarr-Release-Profile-RegEx/#propers-and-repacks) release profile and fill with [P2P Groups + Repack/Proper](https://trash-guides.info/Sonarr/Sonarr-Release-Profile-RegEx/#p2p-groups-repackproper).
 
 #### Quality
 
@@ -652,7 +284,7 @@ For me it ended up looking like this:
 
 ![Sonarr: Release profiles](${SURL}/images/b/sonarr/sonarr_release_profiles.png "Sonarr: Release profiles")
 
-But yours can differ as is mostly personal preference. For the "Quality profile" I'll be using the default "HD-1080p" most of the time, but I also created a "HD + WEB (720/1080)" which works best for some.
+But yours can differ as its mostly personal preference. For the "Quality profile" I'll be using the default "HD-1080p" most of the time, but I also created a "HD + WEB (720/1080)" which works best for some.
 
 #### Download clients
 
@@ -660,9 +292,9 @@ Exactly the same as with [Radarr: Download clients](#download-clients) only chan
 
 - Name: can be anything, just an identifier.
 - Enable: enable it.
-- Host: use `localhost`.
+- Host: use `127.0.0.1`.
 - Port: the port number you chose, `30000` in my case.
-- Url Base: leave blank as even though we have it exposed under `/qbt`, the `localhost` service itself is not.
+- Url Base: leave blank as even though you have it exposed under `/qbt`, the service itself is not.
 - Username: the Web UI username, `admin` by default.
 - Password: the Web UI username, `adminadmin` by default (you should've changed it if you have the service exposed).
 - Category: `tv`.
@@ -671,20 +303,20 @@ Everything else can be left as default, but maybe change *Completed Download Han
 
 #### Indexers
 
-Also exactly the same as with [Radarr: Indexers](#indexers-1), click on the giant "+" button and click on the *custom* Torznab option (this doesn't have the Jackett preset). Then configure:
+Also exactly the same as with [Radarr: Indexers](#indexers), click on the giant "+" button and click on the *custom* Torznab option (this doesn't have the Jackett preset). Then configure:
 
-- Name: can be anything, just an identifier. I like to do "Jackett - indexer_name".
-- URL: `http://localhost:9117/api/v2.0/indexers/YOURINDEXER/results/torznab/`, where `YOURINDEXER` is what Jackett exposes. Can be looked at if you hover on the indexer's "Copy Torznab Feed" button on the Jackett Web UI, examples are `eztv` and `thepiratebay`. Again, for some reason I can't directly use the reverse proxied Jackett.
+- Name: can be anything, just an identifier. I like to do "Jackett - INDEXER", where "INDEXER" is just an identifier.
+- URL: `http://127.0.0.1:9117/jack/api/v2.0/indexers/YOURINDEXER/results/torznab/`, where `YOURINDEXER` is specific to each indexer (`eztv`, `nyaasi`, etc.). Can be directly copied from the indexer's "Copy Torznab Feed" button on the Jackett Web UI.
 - API Path: `/api`, leave as is.
-- API Key: this can be found at the top right corner in Jackett's Web UI. Copy/paste it.
-- Categories: which categories to use when searching, these are generic categories until you test/add the indexer. After you add the indexer you can come back and select your prefered categories (like just toggling the movies categories).
-- Tags: I like to add a tag for the "indexer_name" like `yts` or `tpb`. This is useful so I can control which indexers to use when adding new movies.
+- API Key: this can be found at the top right corner in Jackett's Web UI.
+- Categories: which categories to use when searching, these are generic categories until you test/add the indexer. After you add the indexer you can come back and select your prefered categories (like just toggling the TV categories).
+- Tags: I like to add a tag for the indexer name like `eztv` or `nyaa`. This is useful to control which indexers to use when adding new series.
 
 Everything else on default. *Download Client* can also be set, which can be useful to keep different categories per indexer or something similar. *Seed Ratio* and *Seed Time* can also be set and are used to manage when to stop the torrent, this can also be set globally on the qBitTorrent Web UI, this is a personal setting.
 
 ### Download content
 
-Almost the same as with [Radarr: Download content](#download-content), but I've been personally selecting the torrents I want to download for each season/episode so far, as the indexers I'm using are all over the place and I like consistencies. Will update if I find a better near 100% automation process, but I'm fine with this anyways as I always monitor that everything is going fine.
+Almost the same as with [Radarr: Download content](#download-content), but I've been personally selecting the torrents I want to download for each season/episode so far, as the indexers I'm using are all over the place and I like consistencies. Will update if I find a (near) 100% automation process, but I'm fine with this anyways as I always monitor that everything is going fine.
 
 Add by going to *Series -> Add New*. Basically just follow the [Sonarr: Library add new](https://wiki.servarr.com/sonarr/library#add-new) guide. Adding series needs a bit more options that movies in Radarr, but it's straight forward.
 
@@ -710,7 +342,7 @@ Then it will bring a window with the search results, where it shows the indexer
 
 ![Sonarr: Interactive search results](${SURL}/images/b/sonarr/sonarr_interactive_search_results.png "Sonarr: Interactive search results")
 
-After the movie is downloaded and processed by Sonarr, it will create the appropriate hardlinks to the `media/tv` directory, as set in [Directory structure](#directory-structure).
+After the movie is downloaded and processed by Sonarr, it will create the appropriate hardlinks to the `media/tv` directory, as set in [Directory structure](https://blog.luevano.xyz/a/torrenting_with_qbittorrent.html#directory-structure).
 
 Optionally, you can add subtitles using [Bazarr](#bazarr).
 
@@ -732,11 +364,11 @@ I'm installing the pre-built binary instead of building it as I was getting a lo
 gpasswd -a jellyfin servarr
 ```
 
-You can already `start`/`enable` the `jellyfin.service` which will start at `http://localhost:8096/` by default where you need to complete the initial set up. But let's create the reverse proxy first then start everything and finish the set up.
+You can already `start`/`enable` the `jellyfin.service` which will start at `http://127.0.0.1:8096/` by default where you need to complete the initial set up. But let's create the reverse proxy first then start everything and finish the set up.
 
 ## Reverse proxy
 
-I'm going to have my `jellyfin` instance under a subdomain with an `nginx` reverse proxy as shown in the [Arch wiki](https://wiki.archlinux.org/title/Jellyfin#Nginx_reverse_proxy). For that, create a `jellyfin.conf` at the usual `sites-available/enabled` path for `nginx`:
+I'm going to have my `jellyfin` instance under a subdomain with an `nginx` reverse proxy as shown in the [Arch wiki](https://wiki.archlinux.org/title/Jellyfin#Nginx_reverse_proxy). For that, create a `jellyfin.conf` at the usual `sites-<available/enabled>` path for `nginx`:
 
 ```nginx
 server {
@@ -828,13 +460,13 @@ Then navigate to `https://jellyfin.yourdomain.com` and either continue with the
 
 The initial setup wizard makes you create an user (will be the admin for now) and at least one library, though these can be done later. For more check [Jellyfin: Quick start](https://jellyfin.org/docs/general/quick-start/).
 
-Remember to use the configured directory as mentioned in [Directory structure](#directory-structure). Any other configuration (like adding users or libraries) can be done at the dashboard: click on the 3 horizontal lines on the top left of the Web UI then navigate to *Administration -> Dashboard*. I didn't configure much other than adding a couple of users for me and friends, I wouldn't recommend using the admin account to watch (personal preference).
+Remember to use the configured directory as mentioned in [Directory structure](https://blog.luevano.xyz/a/torrenting_with_qbittorrent.html#directory-structure). Any other configuration (like adding users or libraries) can be done at the dashboard: click on the 3 horizontal lines on the top left of the Web UI then navigate to *Administration -> Dashboard*. I didn't configure much other than adding a couple of users for me and friends, I wouldn't recommend using the admin account to watch (personal preference).
 
 Once there is at least one library it will show at *Home* along with the latest movies (if any) similar to the following (don't judge, these are just the latest I added due to friend's requests):
 
 ![Jellyfin: Home libraries](${SURL}/images/b/jellyfin/jellyfin_home_libraries.png "Jellyfin: Home libraries")
 
-And inside the "Movies" library you can see the whole catalog where you can filter or just scroll as well as seeing *Suggestions* (I think this starts getting populated afte a while) and *Genres*:
+And inside the "Movies" library you can see the whole catalog where you can filter or just scroll as well as seeing *Suggestions* (I think this starts getting populated after a while) and *Genres*:
 
 ![Jellyfin: Library catalog options](${SURL}/images/b/jellyfin/jellyfin_library_catalog_options.png "Jellyfin: Library catalog options")
 
@@ -915,11 +547,11 @@ yay -S bazarr
 gpasswd -a bazarr servarr
 ```
 
-The default port that Bazarr uses is `6767` for http (the one we need for our reverse proxy), and it has pre-configured the default ports for Radarr and Sonarr.
+The default port that Bazarr uses is `6767` for http (the one you need for the reverse proxy), and it has pre-configured the default ports for Radarr and Sonarr.
 
 ## Reverse proxy
 
-Basically the same as with [Radarr: Reverse proxy](#reverse-proxy-2) and [Sonarr: Reverse proxy](#reverse-proxy-3), ==except that the `proxy_pass` (needs `/bazarr`) is different.==
+Basically the same as with [Radarr: Reverse proxy](#reverse-proxy) and [Sonarr: Reverse proxy](#reverse-proxy-1).
 
 Add the following setting in the `server` block of the `isos.conf`:
 
@@ -936,11 +568,11 @@ server {
 }
 ```
 
-Then add the following `location` blocks in the `isos.conf`, where I'll keep it as `/bazarr`:
+Then add the following `location` blocks in the `isos.conf`, where I'll keep it as `/bazarr/`:
 
 ```nginx
-location /bazarr {
-    proxy_pass http://localhost:6767/bazarr; # change port if needed
+location /bazarr/ {
+    proxy_pass http://127.0.0.1:6767/bazarr/; # change port if needed
     proxy_http_version 1.1;
 
     proxy_set_header X-Real-IP $remote_addr;
@@ -955,7 +587,7 @@ location /bazarr {
 # Allow the Bazarr API through if you enable Auth on the block above
 location /bazarr/api {
     auth_request off;
-    proxy_pass http://localhost:6767/bazarr/api;
+    proxy_pass http://127.0.0.1:6767/bazarr/api;
 }
 ```
 
@@ -974,7 +606,7 @@ systemctl start bazarr.service
 systemctl enable bazarr.service
 ```
 
-This will start the service and create the default configs under `/var/lib/bazarr`. We need to change the `base_url` for the necessary services as we're running them under a reverse proxy and under subdirectories. Edit `/var/lib/bazarr/config/config.ini`:
+This will start the service and create the default configs under `/var/lib/bazarr`. You need to change the `base_url` for the necessary services as they're running under a reverse proxy and under subdirectories. Edit `/var/lib/bazarr/config/config.ini`:
 
 ```ini
 [general]
@@ -996,7 +628,7 @@ Then restart the `bazarr` service:
 systemctl restart bazarr.service
 ```
 
-Now `https://isos.yourdomain.com/bazarr` is accessible. Again go straight to secure the instance by adding authentication under *Settings -> General -> Security*. I added the "Forms" option, just fill in the username and password then click on save changes on the top left of the page. You can restart the service again and check that it asks for login credentials. I also disabled *Settings -> General -> Updates -> Automatic*.
+Now `https://isos.yourdomain.com/bazarr` is accessible. ==Secure the instance right away== by adding authentication under *Settings -> General -> Security*. I added the "Forms" option, just fill in the username and password then click on save changes on the top left of the page. You can restart the service again and check that it asks for login credentials. I also disabled *Settings -> General -> Updates -> Automatic*.
 
 ### Configuration
 
@@ -1026,11 +658,3 @@ I've tested this setup for the following languages (with all default settings as
 I tried with "Latin American Spanish" but they're hard to find, those two work pretty good.
 
 None of these require an [Anti-Captcha](https://anti-captcha.com/) account (which is a paid service), but I created one anyways in case I need it. Though you need to add credits to it (pretty cheap though) if you ever use it.
-
-# WIP
-
-- Description on qbittorrent listening port, openning with ufw, specify at the beginning or on the config part
-- Change all reverse proxy and configs for 127.0.0.1 instead of localhost
-- Change jackett config for the 127.0.0.1 ip
-- Change the reverse proxy's api location parts
-- Flaresolverr now works with -bin, needs to install xorg-server-xvfb
\ No newline at end of file
diff --git a/src/blog/a/torrenting_with_qbittorrent.md b/src/blog/a/torrenting_with_qbittorrent.md
index c3a0b82..9e0da20 100644
--- a/src/blog/a/torrenting_with_qbittorrent.md
+++ b/src/blog/a/torrenting_with_qbittorrent.md
@@ -16,7 +16,7 @@ Most of my config is based on the [TRaSH-Guides](https://trash-guides.info/) (wi
 
 Everything here is performed in ==arch btw== and all commands should be run as root unless stated otherwise.
 
-==Also kindly note that I do not condone the use of torrenting for illegal activities. I take no responsibility for what you do when setting up anything shown here. It is for you to check your local laws before using automated downloaders such as Sonarr and Radarr.==
+==Kindly note that I do not condone the use of torrenting for illegal activities. I take no responsibility for what you do when setting up anything shown here. It is for you to check your local laws before using automated downloaders such as Sonarr and Radarr.==
 
 # Table of contents
 
@@ -36,7 +36,7 @@ If you want to expose to a (sub)domain, then similar to my early [tutorial](http
 - An **A** (and/or **AAAA**) or a **CNAME** for `isos` (or whatever you want to call it).
     - For automation software (qBitTorrent, Jackett, Starr apps, etc.). One subdomain per service can be used instead.
 
-==Note: I'm using the explicit `127.0.0.1` ip instead of `localhost` in the reverse proxies/services config as `localhost` resolves to `ipv6` sometimes which is not configured on my server correctly.== If you have it configured you can use localhost without any issue.
+==Note: I'm using the explicit `127.0.0.1` ip instead of `localhost` in the reverse proxies/services config as `localhost` resolves to `ipv6` sometimes which is not configured on my server correctly.== If you have it configured you can use `localhost` without any issue.
 
 ## Directory structure
 
@@ -183,7 +183,9 @@ Also modify the `Port` if you changed it. Restart the `jackett` service:
 systemctl restart jackett.service
 ```
 
-It should now be available at `https://isos.yourdomain.com/jack`. ==Add an admin password right away== by scroll down and until the first config setting; don't forget to click on "Set Password". Change any other config you want from the Web UI, too (you'll need to click on "Apply server settings").
+It should now be available at `https://isos.yourdomain.com/jack`. ==Add an admin password right away== by scroll down and until the first config setting; don't forget to click on "Set Password". Change any other config you want from the Web UI, too (you'll need to click on the blue "Apply server settings" button).
+
+Note that you need to set the "Base URL override" to `http://127.0.0.1:9117` (or whatever port you used) so that the "Copy Torznab Feed" button works for each indexer.
 
 ### Indexers
 
@@ -228,7 +230,7 @@ Verify that the service started correctly by checking the logs:
 journalctl -fxeu flaresolverr
 ```
 
-It should show "Test successful" and "Serving on http://0.0.0.0:8191" (which is the default). Jackett will need to be configured if FlareSolverr is served on anything different than the default. This doesn't need to be exposed or anything, it's just an internal API that Jackett (or anything you want) will use.
+It should show "Test successful" and "Serving on http://0.0.0.0:8191" (which is the default). Jackett now needs to be configured by adding `http://127.0.0.1:8191` almost at the end in the "FlareSolverr API URL" field, then click on the blue "Apply server settings" button at the beginning of the config section. This doesn't need to be exposed or anything, it's just an internal API that Jackett (or anything you want) will use.
 
 # qBitTorrent