Jekyll2026-07-08T11:01:47+00:00https://pirateflix.sangu.be/feed.xmlPirateFlixBuild your own automated home media server with Docker. PirateFlix wires up Jellyfin, Radarr, Sonarr, Prowlarr and more into one copy-paste HTPC setup. Wouter Van SchandevijlWatchtower: The Self-Updating Fleet2026-07-06T00:00:00+00:002026-07-06T00:00:00+00:00https://pirateflix.sangu.be/blog/watchtowerTwelve containers on :latest means twelve things quietly going stale. Watchtower watches for new images, pulls them, and recreates the container on your schedule. It’s the laziest possible update strategy.

The Setup

Watchtower rides in the same compose.yml as the rest of the fleet.

watchtower:
  image: containrrr/watchtower
  container_name: watchtower
  restart: ${RESTART_POLICY}
  environment:
    - TZ=${TZ}
    - WATCHTOWER_CLEANUP=true
    - WATCHTOWER_LABEL_ENABLE=true
    - 'WATCHTOWER_SCHEDULE=${WATCHTOWER_SCHEDULE}'
  volumes:
    - /var/run/docker.sock:/var/run/docker.sock

Handing a container /var/run/docker.sock is effectively giving it root on the host — it can start, stop and recreate anything. That’s the deal with Watchtower.

Gated Upgrades

By default Watchtower updates every container on the host. The fix is label-gating with WATCHTOWER_LABEL_ENABLE=true and Watchtower only touches containers wearing the opt-in label:

labels:
  - 'com.centurylinklabs.watchtower.enable=true'

Every service in the compose file carries that line, so a stray container on the same host won’t get a surprise upgrade.

Scheduling and cleanup

WATCHTOWER_SCHEDULE takes a 6-field cron (the leading field is seconds — a Watchtower quirk, not standard cron). Pick a quiet hour so a recreate never lands mid-stream:

# At 04:00 every day
WATCHTOWER_SCHEDULE=0 0 4 * * *

# Every 4th of the month at 05:00
WATCHTOWER_SCHEDULE=0 0 5 4 * *

WATCHTOWER_CLEANUP=true bins the old image after a successful update.

Notifications

An update you don’t hear about is an update you can’t correlate with “why did Prowlarr break last Tuesday”. Watchtower can ping you whenever it recreates something. The full .env-example has the notification block — left blank in the compose walkthrough — ready for Slack or e-mail:

environment:
  # Slack (or any shoutrrr URL: discord://, telegram://, ...)
  - WATCHTOWER_NOTIFICATIONS=slack
  - WATCHTOWER_NOTIFICATION_SLACK_HOOK_URL=
  - WATCHTOWER_NOTIFICATION_SLACK_IDENTIFIER=Watchtower

  # or email
  - WATCHTOWER_NOTIFICATIONS=email
  - WATCHTOWER_NOTIFICATION_EMAIL_FROM=
  - WATCHTOWER_NOTIFICATION_EMAIL_TO=
  - WATCHTOWER_NOTIFICATION_EMAIL_SERVER=
  - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=
  - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER=
  - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD=

The Danger

Watchtower is the lazy option, not the safe one. :latest is a moving target, and “pull whatever’s newest and recreate” will, eventually, pull a release that changes a config format, drops a setting, or just plain breaks — and it’ll do it at 4am while you’re asleep, with no “are you sure”.

That’s a fine bargain for a home media stack: if Sonarr is down for a morning, nobody files a ticket. It’s a terrible bargain for anything you actually depend on. So the real decision is per-fleet:

  • Low-stakes, high-churn (the *arr apps, dashboards) → let Watchtower keep them fresh. The whole point is to never think about it.

  • Load-bearing or stateful (databases, your reverse proxy) → don’t label but update on your own terms:

    docker compose pull && docker compose up -d

Alternative

If auto-recreate makes you nervous consider Renovate / Dependabot — the grown-up option where you pin tags and update with an automatically created pull request.

Conclusion

Auto-updates are a convenience, not a safety feature. Know which of your containers can afford a bad morning, and handle the rest manually. 🏴‍☠️

]]>Wouter Van SchandevijlGetting Past Cloudflare: FlareSolverr & Byparr2026-07-05T00:00:00+00:002026-07-05T00:00:00+00:00https://pirateflix.sangu.be/blog/flaresolverr-byparrSome indexers put themselves behind Cloudflare’s anti-bot wall. Point Prowlarr at one and instead of results you get a challenge page.

FlareSolverr helps you get past it.

What FlareSolverr Does

When Prowlarr hits a protected indexer, it lets FlareSolverr’s solve the Cloudflare (and DDoS-GUARD) challenges and gets back the HTML and cookies so that Prowlarr can sail through on the next requests.

flaresolverr:
  image: ghcr.io/flaresolverr/flaresolverr
  container_name: flaresolverr
  environment:
    - LOG_LEVEL=info
    - TZ=${TZ}
  ports:
    - 8191:8191

Wiring It Into Prowlarr

FlareSolverr is added as an indexer proxy, and Prowlarr uses tags to decide which indexers route through it:

  1. Settings → Indexers → Indexer Proxies → + → FlareSolverr.
  2. Host: http://flaresolverr:8191 (container name works if they share a Docker network; otherwise IP:port).
  3. Tags: add a tag, e.g. flaresolverr. Save.
  4. On each indexer that hides behind Cloudflare, add the same flaresolverr tag.

The Byparr Alternative

For a long stretch FlareSolverr development stalled while Cloudflare’s challenges kept evolving, and so alternatives spawned. It has picked up releases again in 2026, so it’s not dead — but the alternatives stuck around, and they’re handy when a stubborn indexer won’t crack.

The best of them is Byparr. The selling point: it speaks the exact same /v1 API on the same port 8191, so it’s a genuine drop-in. Under the hood it swaps Chrome for Camoufox (a Firefox-based anti-detection browser) served by a FastAPI app, which tends to do better against newer fingerprinting.

ThePhaseless/Byparr : Drop-in FlareSolverr alternative built on Camoufox

byparr:
  image: ghcr.io/thephaseless/byparr
  container_name: byparr
  ports:
    - 8191:8191
  # I needed the following on my Proxmox LXC / OCI
  # to avoid a camoufox multiprocessing error
  # shm_size: 512mb

Because the API is identical, migrating is a one-line change: leave the FlareSolverr proxy in Prowlarr exactly as it is and just point its Host at Byparr instead. No re-tagging, no re-configuring the indexers.

Conclusion

Reach for FlareSolverr first — it’s the default, it’s well-supported by Prowlarr, and it’s active again. Keep Byparr in your back pocket for the one indexer that FlareSolverr can’t get past: switching is a one-liner change.

]]>Wouter Van SchandevijlGoodbye Ombi, Hello Jellyseerr, ugh.. I mean Seerr2026-07-05T00:00:00+00:002026-07-05T00:00:00+00:00https://pirateflix.sangu.be/blog/goodbye-ombiThe original setup used Ombi as the request box: the friendly search-and-click front door you hand to family so nobody makes you explain Sonarr’s quality profiles over Sunday dinner. Type a title, click request, and it lands in Sonarr/Radarr.

Ombi still does that. But it hasn’t kept up…

Why Leave Ombi

Ombi isn’t dead — it still ships the occasional bug-fix release. But development has slowed to a trickle: there are no formal stable releases anymore (everything’s tagged pre-release), and the team has openly been short on maintainer time. More to the point for a Jellyfin house: Ombi treats Jellyfin as a second-class citizen next to its Plex/Emby roots, and its UI feels its age next to what the Overseerr family is doing.

Enter Jellyseerr — a fork of Overseerr created specifically to add Jellyfin and Emby support (Overseerr itself is Plex-only). For a Jellyfin setup that’s the whole ballgame:

  • Native Jellyfin login — it authenticates against Jellyfin and imports your users straight from the server, so you don’t recreate accounts.
  • Modern, discovery-first UI — the slick Overseerr interface, trending rows and all.
  • Sonarr/Radarr fulfillment built in, plus proper request and issue management.

Deploying Jellyseerr

Jellyseerr is refreshingly self-contained — SQLite by default, so no external database to babysit (Postgres is optional via DB_TYPE=postgres if you outgrow it).

jellyseerr:
  image: fallenbagel/jellyseerr
  container_name: jellyseerr
  environment:
    - TZ=${TZ}
    - LOG_LEVEL=info
  volumes:
    - ${CONFIG_PATH}/jellyseerr:/app/config
  ports:
    - 5055:5055
  restart: unless-stopped

Plot Twist: It’s Called Seerr Now

Here’s the homelab special. Right around the time this swap went in, the Jellyseerr and Overseerr projects merged into a single successor: Seerr (announced February 2026). Both Jellyseerr and Overseerr were sunset a few months later — so I effectively migrated to Jellyseerr about a week after it stopped being a thing. Classic.

seerr-team/seerr : The merged successor to Overseerr and Jellyseerr

Nothing broke — the fallenbagel/jellyseerr image still runs — but if you’re doing this today, skip straight to Seerr. It’s the same lineage (Overseerr’s features + Jellyseerr’s Jellyfin/Emby support in one codebase), it’s the one still getting updates, and Seerr ships a built-in auto-migration from Overseerr/Jellyseerr, so moving over later is painless.

The Seerr Migration

The new compose.yaml

seerr:
  image: ghcr.io/seerr-team/seerr
  container_name: seerr
  user: "${PUID}:${PGID}"
  init: true
  environment:
    - TZ=${TZ}
    - LOG_LEVEL=info
  volumes:
    - ${CONFIG_PATH}/seerr:/app/config
  ports:
    - 5055:5055
  restart: unless-stopped

Data migration from Jellyseerr/Overseerr is pretty seamless:

CONFIG_PATH=/volume1/Media/config
mkdir "$CONFIG_PATH/seerr"
cp -a "$CONFIG_PATH/jellyseerr/." "$CONFIG_PATH/seerr/"
docker-compose up -d seerr

Conclusion

Ombi was a good front door for years. But on a Jellyfin box, the request app that logs in with Jellyfin, imports your Jellyfin users, and is actually being developed wins easily. Just aim for Seerr rather than Jellyseerr — save yourself the extra hop I took.

]]>Wouter Van SchandevijlGoodbye Transmission, Hello qBittorrent2026-07-05T00:00:00+00:002026-07-05T00:00:00+00:00https://pirateflix.sangu.be/blog/goodbye-transmissionWay back in the original setup I went with Transmission and picked the familiar transmission-web-control UI because it looks like a regular desktop client. That served me well for years.

Then one day it just… stopped.

The v4 Troubles

On 2023-02-08 Transmission v4.0.0 happened, they rewrote the entire UI and it didn’t ship with my transmission-web-control anymore.

Because this whole thing is supposed to save you time, I took the easy way out:

transmission:
  image: linuxserver/transmission:version-3.00-r8

Which served me well enough for these last 3 years.

The Homelab Trigger

As I was seriously upgrading my homelab, it was time to also have a look at my beloved Pirateflix to see what happened in the world of *arr.

Bringing back my UI

It turned out to be pretty easy to get my good ol’ web-control back:

transmission:
  image: linuxserver/transmission
  environment:
    - DOCKER_MODS=linuxserver/mods:transmission-transmission-web-control

The UI Competition

A quick look at the other UIs…

docker-compose.yml — spin up all four UIs side by side 
x-transmission: &base
  image: lscr.io/linuxserver/transmission:latest
  environment: &env
    PUID: 1000
    PGID: 1000

services:
  floodui:
    <<: *base
    container_name: tr-floodui
    environment:
      <<: *env
      DOCKER_MODS: linuxserver/mods:transmission-floodui
    ports:
      - 9101:9091

  webcontrol:
    <<: *base
    container_name: tr-webcontrol
    environment:
      <<: *env
      DOCKER_MODS: linuxserver/mods:transmission-transmission-web-control
    ports:
      - 9102:9091

  transmissionic:
    <<: *base
    container_name: tr-transmissionic
    environment:
      <<: *env
      DOCKER_MODS: linuxserver/mods:transmission-transmissionic
    ports:
      - 9103:9091

  trguing:
    <<: *base
    container_name: tr-trguing
    environment:
      <<: *env
      DOCKER_MODS: linuxserver/mods:transmission-trguing
    ports:
      - 9104:9091

Four contenders, same daemon underneath. Here’s what they look like:

Flood for Transmission
Flood for Transmission
Transmission Web Control
Transmission Web Control
Transmissionic
Transmissionic
TrguiNG
TrguiNG

And where each one lives — with how much love it’s still getting:

  UI Stars Source Commits Last Notes
Flood for Transmission johman10/flood-for-transmission 286 6 months ago  
Transmission Web Control ronggang/transmission-web-control 558 last year Archived 2025/6
Transmissionic 6c65726f79/Transmissionic 2985 3 years ago  
TrguiNG openscopeproject/TrguiNG 481 2 weeks ago  

Leaving Transmission

I’ve had issues with web-control in the past but now it seemed, it was also abandoned as a project… And then it turned out that the integration between qBittorrent and the *arr family is better compared to Transmission.

  • Categories & tags: qBittorrent’s categories map each to a save path and line up exactly with the “category” field the *arr apps use.
  • Built-in search
  • Sequential download: download first & last pieces first
  • Built-in RSS auto-downloader with filter rules.

Migrating to qBittorrent

qbittorrent/qBittorrent : qBittorrent BitTorrent client

The linuxserver/qbittorrent service that replaced it:

qbittorrent:
  image: lscr.io/linuxserver/qbittorrent
  environment:
    - PUID=${PUID}
    - PGID=${PGID}
    - TZ=${TZ}
    - WEBUI_PORT=${QBITTORRENT_PORT}
  volumes:
    - ${CONFIG_PATH}/qbittorrent:/config
    - ${DATA_PATH}:/data
  ports:
    - ${QBITTORRENT_PORT}:${QBITTORRENT_PORT}
    - 6881:6881
    - 6881:6881/udp

You’ll probably have to point to the correct paths in:
Options > Downloads > Saving Management > Default Save Path:

The First-Login Gotcha

The admin password is printed to the docker logs at startup.

docker logs qbittorrent | grep -i password

Set a real password immediately, or a fresh temporary one is regenerated on every restart.
Options > WebUI > Authentication

Repointing the *arrs

Last step, in Sonarr, Radarr, Prowlarr, … under Settings → Download Clients: drop the Transmission client and add a qBittorrent one (host, WEBUI_PORT, credentials), set a Category (ex: radarr, sonarr, …).

Inside qBittorrent on the left menu, right click the CATEGORIES > All > Add Category; or, if the categories you entered already exist, right click them and “Edit Category…”

In Options > Downloads > Saving Management > Default Torrent Management Mode: Automatic

And now you have a separate folder for each… Nice & clean!

Conclusion

If you’re setting up fresh: skip the detour and start on qBittorrent. The *arr integration alone is worth it. The qBittorrent UI is also more colorful than my old web-control, so I’m definitely staying ;)

]]>Wouter Van SchandevijlRecyclarr: The Quality Upgrade I Said No To2026-07-05T00:00:00+00:002026-07-05T00:00:00+00:00https://pirateflix.sangu.be/blog/recyclarrEvery so often you find a tool that’s obviously well-made, solves a real problem, and is beloved by people who clearly know more than you — and you still walk away. Recyclarr is mine.

What It Does

Recyclarr automates the release grabbing process. It configures your custom formats and quality profiles, much better than you ever can. If you do not want to spend time configuring all that, and keeping it up to date, Recyclarr might be exactly what you need!

It will configure years of best practices and fine-tuning from the TRaSH Guides for you, automatically.

recyclarr:
  image: ghcr.io/recyclarr/recyclarr:latest
  container_name: recyclarr
  user: ${PUID}:${PGID}
  environment:
    - TZ=${TZ}
    - CRON_SCHEDULE=${RECYCLARR_CRON}
  volumes:
    - ${CONFIG_PATH}/recyclarr:/config
  restart: ${RESTART_POLICY}

One-shot instead of cron? Just docker compose run --rm recyclarr sync.

Why I Said No

I fall firmly on the quantity over quality side. Fill the terabytes, watch the thing, move on. Recyclarr and the TRaSH guides point towards 4k releases or something, with 14GB movies as pretty much the bare minimum. I’m typically aiming for a 2GB release, which, for me, is just good enough.

A side effect of me being so picky on “bad quality” is that it is often more difficult for me to find a release…

When You Should Use It

This is a “me” problem, not a Recyclarr problem. If any of this is you, go for it — it’ll save you real time:

  • You care about specific encodes — HDR/Dolby Vision done right, lossless audio, trusted release groups.
  • Storage is plentiful and you’d rather re-grab an upgrade than settle.
  • You’ve been hand-maintaining custom formats and are tired of it.

For that person Recyclarr is a no-brainer: the TRaSH Guides are the accumulated taste of thousands of hoarders, and Recyclarr pipes it into your setup automatically.

Conclusion

Recyclarr isn’t going in my stack — not because it’s bad, but because it’s good at something I don’t want.

]]>Wouter Van SchandevijlJellyfin on LG Smart TV2022-10-29T00:00:00+00:002022-10-29T00:00:00+00:00https://pirateflix.sangu.be/blog/lg-smart-tvIf you have a Smart TV with webOS 6+, do not follow these instructions but install it from the official LG Content Store instead!

TL&DR

Following these steps should get you up & running in no time.

  • PC: Create a Developer Account
  • TV: Install “Developer Mode” from the LG Content Store
    • Turn on Developer Mode and Key Server
    • (1): Write down the Passphrase
  • TV (2): All Settings > Network > Wi-Fi Connection > Advanced Wi-Fi Settings > IP Address
  • PC: Start Device Manager for webOS
    • Add Device: Use TV IP Address and Passphrase from steps (1) and (2)
    • Apps > Install > Available > Jellyfin
    • Launch and 🎉
  • PC: Remedy 50h Developer Mode timeout

Installation

Follow the instructions from the TL&DR ;)
If that’s too cryptic, you can find step by step instructions in the official docs. They also cover configuring your CLI or IDE.

Developer Mode

After installing “Developer Mode” from the LG Content Store:

Developer Mode Settings

Device Manager for webOS

webosbrew/dev-manager-desktop : Device/DevMode Manager for webOS TV

Many ways to install Jellyfin, this Desktop UI makes it particularly easy. Check the official docs for screenshots on installation.

Note that you can leave the settings in “Add Device” not mentioned in the TL&DR as is:

  • Port Number: 9992
  • SSH Username: prisoner
  • Authentication Method: Official Dev Mode

The others:

  • Host Address: The IP is hidden under “Advanced Wi-Fi Settings” on your TV.
  • Passphrase: The one displayed in the “Developer Mode” app you downloaded in the LG Content Store

Manual ipk

If you don’t want to install it from the “Available” tab:

Automated Refresh

You basically do not want to turn on Developer Mode again every 50 hours…

A few ways of remedying this:

Device Manager for webOS

Again to the rescue!!

Info > Dev Mode > Renew Automatically…

It offers two possibilities:

RootMyTV

Open the TV browser and surf to RootMy.Tv…
This automatically extends Developer Mode, plus you can now install stuff from the unofficial webOS Homebrew Project.

RootMyTV/RootMyTV.github.io : RootMyTV is a user-friendly exploit for rooting/jailbreaking LG webOS smart TVs.

webosbrew/webos-homebrew-channel : Unofficial webOS TV homebrew store and root-related tooling

Other

]]>Wouter Van SchandevijlMake Radarr/Sonarr UI Obsolete with integrations (Part 2)2022-10-02T00:00:00+00:002022-10-02T00:00:00+00:00https://pirateflix.sangu.be/blog/lists-part2Lists are great for integrating with your IMDB Watchlist and for following automated lists.
While lists can be filtered on Genre, Year(s) etc, which filters are available depends on the source (ex: IMDB vs TMDB) but is typically rather limited.

Let’s have a look at some projects that can help with populating Sonarr/Radarr in a manual or automated way.

Containers

Seerr

Seerr Logo

seerr-team/seerr : Request management and media discovery for Plex, Jellyfin and Emby

Seerr is where things are headed: the Overseerr and Jellyseerr teams merged into one project with a single shared codebase.

sct/overseerr : Request management and media discovery tool for the Plex ecosystem

Fallenbagel/jellyseerr : Fork of Overseerr for jellyfin support

Checkout the UI

SuggestArr

giuseppe99barchetta/SuggestArr : Reads your Jellyfin/Plex/Emby watch history and auto-requests similar titles into Seerr.

Seerr is the request box; SuggestArr is what fills it for you. It reads your Jellyfin watch history and automatically requests similar titles into Seerr, which hands them off to Sonarr/Radarr. Nobody has to search for anything — the library just refills itself in the background. Quantity-over-quality as a running container, which is rather the whole point around here.

Discord

activexray/Doplarr : An *arr request bot for Discord

activexray/doplarr_rs : Rust rewrite of Doplarr

autobrr

autobrr Logo

autobrr/autobrr : Modern download automation: monitors IRC announce channels and RSS feeds in real time and grabs releases matching your filters.

The spiritual successor to autodl-irssi and FlexGet for the race-to-download crowd: instead of following lists, autobrr watches tracker announce channels live and instantly grabs anything matching your filters, straight into qBittorrent/Sonarr/Radarr. Also handles cross-seeding.

Deprecated

JagandeepBrar/LunaSea : Self-hosted software controller built using Flutter

l3uddz/traktarr : Script to add new series & movies to Sonarr/Radarr based on Trakt lists.

petio-team/petio : Petio Request, Discover, Review (for Plex)

Ombi

Ombi Logo

Ombi-app/Ombi : Want a Movie or TV Show on Plex/Emby/Jellyfin? Use Ombi!

Ombi was already mentioned in earlier articles as something that you’d give to your spouse so s/he can easily request or directly download stuff without having to know about the complexities of Sonarr/Radarr.

But Ombi can be great for yourself as well, it has an easy-to-use interface for discovering new things which you can then send directly to Radarr/Sonarr.

Checkout the live demo

]]>Wouter Van SchandevijlMake Radarr/Sonarr UI Obsolete with Lists2022-09-28T00:00:00+00:002022-09-28T00:00:00+00:00https://pirateflix.sangu.be/blog/listsConnect Radarr/Sonarr to IMDB, TrakTV and other lists so you basically never have to open their UI ever again. You add that crazy movie to your IMDB watchlist and Radarr picks it up!

Initial Setup

Setting up Radarr/Sonarr et al is quite easy and fast with a docker-compose but after that.. The configuring begins. It takes some time to setup Heimdall, Sonarr, Radarr, connect the indexers and download clients etc.

After that you need some additional configuration with Profiles and Quality: it takes some tinkering before it starts downloading files that exactly match your quality and file size requirements.

Once all that is setup to your hearts content though, you only really need to access Radarr/Sonarr when there is something new you want to follow or download.

Or is it?

Configuring Lists

Go to Settings > (Import) Lists

Worth noting:
Perhaps you want to follow a list but not everything. This is of course possible. Filter entries in the lists based on their Rating, Genres, Year(s), or just a hard max limit.

Advanced Lists Options:
List Update Interval: Radarr/Sonarr will only check every x hours for changes on your lists
Clean Library Level: if you follow “IMDB Popular Movies” together with this setting, you will always only have 100 movies on your hard disk. Use this if you have limited storage capacity!

Autoconfigured

Follow these lists with just a few clicks:

  • IMDB
  • Trakt.tv
    • TrakTV Popular, Trending, Anticipated
    • TopWatched: By Week/Month/Year/All Time
    • Recommended: By Week/…
    • A Specific User or List
  • TMDB
    • A specific User, List, Person, Company, Collection or Keyword
    • Popular, Theaters, Upcoming, Top
  • StevenLu: An algorithmic list of movies that look popular by a numeric heuristic.
  • Plex Watchlist
  • more…

Your IMDB Watchlist

Add at: Settings > Lists > IMDb Lists > Custom

After creating your IMDB account, go to your watchlist and click Edit:

IMDB - Edit your watchlist

Once on the edit screen:

  • Note the lsXXXXXXXX number in the URI – this is the List/User ID you need to add in Radarr
  • Click on the Settings button and make your list publicly available so Radarr can reach it

IMDB - Edit your watchlist

Then once in IMDB, click on the top left corner of a movie poster to have it added to Radarr!

IMDB - Watchlist

Trakt.tv Directors

User origin14 on Trakt.tv manually maintains a list of movies made by famous directors.

Add a Trakt List with Username: origin14 and List name one of the following:

]]>Wouter Van SchandevijlSo… What ARE these Arr’s doing?2022-09-27T00:00:00+00:002022-09-27T00:00:00+00:00https://pirateflix.sangu.be/blog/notificationsWhen a new Futurama episode comes out after a 10 year hiatus, how can the Arr-family help you not miss this major event?

Connections

Pretty simple, connect Sonarr, Radarr etc to your favourite application!

Many options are provided out of the box like Twitter, Discord, Slack, Telegram, Email, Synology, Plex, …

If your “thing” is not supported, there is also the option for executing a custom script or using a WebHook.

There are multiple triggers for sending a notification. The most useful is probably:

On Import - {Formerly Known as On Download} Be notified when episodes/movies are successfully imported.

Slack

One of the predefined Connections. The only thing you really need to configure is the Slack WebHook.
Which looks like this:

https://hooks.slack.com/services/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

Follow their official instructions:

  • Create An App
  • Features > Incoming Webhooks
    • Activate Incoming Webhooks
    • Add New Webhook to Workspace
    • Copy the url!

Activating Slack Webhook

What can you expect:

Something like this:
For movies you often even get a poster picture etc!

Slack Webhook example

Tip: Instead of a plain incoming webhook, you can wire the notifications through a proper Slack app/bot (with a xoxb- bot token) for richer, better-looking messages like you get with the Discord integration.

Discord

  • Setup your own Discord server
  • Add your pirate text channel
  • Open your server Settings
  • Server Settings > Integrations
    • Create Webhook
    • Pick a cool icon etc
    • Copy Webhook URL
    • Save Changes

What can you expect:

A much better integration compared to Slack for sure!

Discord Webhook example

Players

To connect with Jellyfin add an Emby connection.
For Plex there is a dedicated option available.

Notifiarr

Notifiarr/notifiarr : Connect your *arr stack to Discord (and more) via Notifiarr.com

If you want a whole Dashboard…

]]>Wouter Van SchandevijlGoodbye Jackett, Long Live Prowlarr!!2022-09-25T00:00:00+00:002022-09-25T00:00:00+00:00https://pirateflix.sangu.be/blog/goodbye-jackettAll welcome the newest member of the Arr-family: Prowlarr.

It basically does the exact same thing as Jackett but with these differences:

  • Automatic sync of indexers with Sonarr, Radarr, Readarr, …
  • Manual Search: Transforms magnet links into torrents so that they can be sent to Transmission
  • Uses the same layout & UI as the other Arr products

Prowlarr/Prowlarr : Indexer manager/proxy built on the popular *arr .net/reactjs base stack

Jackett/Jackett : API Support for your favorite torrent trackers

Automatic Sync

This is basically the big win for Prowlarr over Jackett. In both applications you select all public indexers (or private ones if you have credentials;) but once you were done with this in Jackett, you still needed to configure all of them in Sonarr, Radarr, … etc. A lot of copy pasting.

This is no longer the case for Prowlarr: Using the API keys, the indexers are added to Sonarr, Radarr, … automatically.

Transmission Integration

Sometimes you wanted to download something else entirely; or Sonarr/Radarr had trouble finding exactly what you want. Manual searches in Jackett were problematic in combination with Transmission: you’d get a magnet link that could not just be dropped to the Transmission black hole, it doesn’t pick it up. You’d have to revert to downloading locally or to manually importing it in Transmission.

With Prowlarr, this manual work is a thing of the past.

Same UI

Prowlarr uses the same UI (and offers the same configuration options!!) we’re used to from the other Arr-products. It also offers some additional functionality over Jackett like some cool graphs and stuff.

Conclusion

If you are already all setup with Jackett there is not much reason to make the switch really.
For new setups or if you’re starting to tinker with the indexers, you want to look at Prowlarr instead.

]]>Wouter Van Schandevijl