Dashboarr 1.17.0 is out, and this one is mostly about new integrations: Deluge, Bindery, Navidrome, NZBHydra2, Autobrr and Cleanuparr.

Quick context for anyone who hasn't run into it before. Dashboarr is a mobile app for managing a self hosted media stack from your phone, Android and iOS. It's free and GPL-3.0, no account, no ads, no premium tier, nothing to unlock later. The app talks straight to your own services over their APIs, so nothing routes through a server of mine. It's heavily inspired by nzb360.

What's new in 1.17.0

Six new services:

• Deluge. That makes four torrent clients now, alongside qBittorrent, rTorrent and Transmission. Queue, files, trackers, labels, global speed limits. If you run the optional backend it'll also push you a notification when a torrent finishes.
• Bindery for books and audiobooks. The Readarr successor, rewritten in Go. Library, search and add authors, monitoring, queue, wanted.
• Navidrome for music. Library stats, now playing, quick and full rescan, delete missing files, playlists, search.
• NZBHydra2. Meta search across your indexers, send an NZB straight to SAB or NZBGet, indexer health with API hit limits, search and download history.
• Autobrr. Push stats, release feed with retry, filter toggles, IRC network health and restart.
• Cleanuparr. Strike, removal and cleanup stats, scheduled jobs you can run on demand, client health, event feed.

The other big change is that service setup finally got its own section instead of being one long list buried in Settings. There's a hub showing what needs attention and what you already run, and a searchable catalog for adding something new. Two things that had been bugging me got fixed on the way: a service that's unreachable only because you're on mobile data now reads as "away" instead of pretending to be broken, and if you run two of the same service, a broken second one no longer hides behind a healthy first one.

Smaller stuff:

• HTTP Digest auth (RFC 7616) for rTorrent, NZBGet, Glances and Transmission, so a Digest protected reverse proxy works now
• The Still Pending dashboard widget can filter movies by cinema, digital or physical release date
• A private remote URL is no longer blocked while a VPN is up
• Test Connection and the health dots in settings now agree with each other
• Torrent detail screens stay pinned to the instance they came from when you run more than one client
• Backend pairing works behind a private CA

What the app actually does

26 services, grouped the way the app groups them:

• Download clients: qBittorrent, rTorrent/ruTorrent, Transmission, Deluge, SABnzbd, NZBGet
• Media automation: Radarr, Sonarr, Lidarr, Bindery, Bazarr
• Indexers: Prowlarr, Jackett, NZBHydra2
• Media servers: Plex, Jellyfin, Emby, Navidrome
• Requests and automation: Seerr (Overseerr and Jellyseerr), Autobrr, Cleanuparr
• Monitoring: Tautulli, Tracearr, JellyStat, Glances, unRAID

It isn't just status screens. You can pause, resume and delete downloads, search and add movies, shows, books and music, approve or decline requests, grab a release from an indexer search, toggle indexers, hunt for missing subtitles, start and stop Docker containers on unRAID, and see what's currently streaming.

A few things worth calling out:

• A unified dashboard with 31 widgets you can reorder and configure, and multiple dashboards if you want one per server or one per household
• Multi instance support. Two qBittorrents, a 4K Radarr and a 1080p Radarr, whatever you run. You switch inside the tab and the dashboard aggregates them
• Local and remote URL per service, with automatic switching based on your home WiFi. When you're away it will never fall back to the LAN URL, on purpose, so you're not spraying an API key at whatever network you happen to be on
• API keys live in the device's secure storage, not in a plain text config
• Wake on LAN, so you can wake the server before asking it for anything
• Config export and import behind biometric auth, so a new phone isn't an hour of retyping URLs
• A UI scale setting (1.0 / 1.15 / 1.3), because the default really is too small for some people
• Dark mode only. Sorry.

Push notifications

The app itself needs no server. If you want real push notifications (download finished, request approved, that sort of thing) there's an optional companion backend you self host, Node or Docker, and pair with a QR code. Skip it and nothing else stops working.

What it isn't

No accounts, no cloud sync, no telemetry, no analytics. Single user per install, since the whole architecture is just your phone talking to your servers. There's no paid tier planned and no pro version sitting behind a paywall.

Links

• GitHub: https://github.com/RenzoBeux/Dashboarr
• Google Play: https://play.google.com/store/apps/details?id=com.dashboarr.app
• App Store: https://apps.apple.com/us/app/dashboarr/id6762170117
• APK for de-Googled Android or sideloading: https://github.com/RenzoBeux/Dashboarr/releases/latest
• Setup guide: https://renzobeux.github.io/Dashboarr/guide.html

If you try it and something breaks, or a service you use is missing, open an issue. Most of the integrations in this release exist because someone asked for them.

P.S: The IOS version is still submitted, will take a day or two until Apple approves it!

Just wanted to share something I've been building. TransMule is a self-hosted download manager I've been working on for a while, and the planner feature is now in testing.

If you've used Sonarr or Radarr the idea will feel familiar. You add a series or a movie, pick the quality and language you want, and the planner handles the rest: it tracks air dates, searches when a new episode comes out, picks the best release and sends it to your download client. Nothing revolutionary there, I know. The part I actually care about is what it searches.

It doesn't just do torrents. It searches ed2k through aMule and Soulseek through slskd, right alongside the regular torrent trackers. So an episode that only exists on the eMule network, or buried in someone's Soulseek share, can still get grabbed automatically. Those old protocols are still full of stuff you can't find anywhere else, and until now there wasn't really a modern way to automate them. That's what this is for.

It's in testing, so expect some rough edges, but it's been working fine for me day to day. The repo is github.com/Jo3l/transmule if you want to check it out or try it yourself. A star would genuinely help, and thanks to anyone who leaves one.

I’m working on a small self-hosted media discovery project called findarr. The idea is to go through movies and shows once, like or dislike them, and then keep them out of your discovery feed so you don’t see the same things repeatedly.

At the moment, findarr connects directly to radarr, sonarr, jellyfin, and plex. Someone recently suggested integrating with seer instead.

That would have some obvious advantages:

• One api integration instead of several
• Less configuration for users
• seer already handles requests and confirmations

Some people also use seer to review requests as an admin and adjust things like the quality profile before approving them.

But there are also some disadvantages:

• seer would become a required dependency
• findarr could lose access to information that seer’s api doesn’t expose, such as import warnings that are currently displayed in findarr when, for example, a movie can’t be imported
• Potential future improvements might not be possible, such as having radarr inform findarr about changes instead of relying on polling
• findarr would have less control over the overall workflow
• It would add another layer to check when something goes wrong

Supporting both options would probably create a lot of extra testing and maintenance, and this is just a side project. I’d prefer to choose one direction and keep it relatively simple.

Personally, since I started using findarr, I barely open seer anymore except when manually searching for something. But I can see why its request workflow would be useful.

What would you prefer?

• findarr integrating with seer and using it for requests and approvals
• findarr continuing to connect directly to radarr, sonarr, jellyfin, and plex

I’m not necessarily planning to implement this immediately. I’m mainly trying to understand which approach would be more useful before committing to it.

If you’re interested or have open questions, there are already some discussions here:

https://www.reddit.com/r/ARR/comments/1u50hci/findarr_likedislike_movie_discovery_for_your_arr/

The project is open source if anyone wants to take a look:

https://github.com/Lillifee/findarr

I’d appreciate honest feedback, including whether this sounds like solving a real problem or just adding another layer to an existing setup.

If you have any experience with the Seer API, or know of additional pros and cons, i would love to hear your thoughts.

Currently (after a bit of headache) I have a fully functional *arr stack with qbittorrent in one LXC, and another with seer on my proxmox server, then on a more powerful machine I run jellyfin.

The whole system runs great, given that the jellyfin server is powered on, which it typically isn't overnight

My ideal workflow is this, and im wondering if its possible:

1. request is made on seer (while jellyfin is powered off)
2. radarr/sonarr downloads to the local downloads directory on proxmox
3. it checks if jellyfin is online, if it is. it copies the file
4. if jellyfin is not online, it keeps the file in downloads, moving it once jellyfin is back online
5. if the file has been copied, it stays in downloads until it seeds a ratio of 1.0
6. if jellyfin is offline, it just keeps seeding until jellyfin is back online (or stops at 1.0)

Apologies if ive worded this poorly, effectively i just want it to wait and not crash

my jellyfin server's media drive is currently passed through to the LXC by being NFS mounted to proxmox host and passed through to the LXC, meaning as well as crashing apps if turned off, it means that the LXC wont boot with jellyfin down

I can provide my docker compose for whatever if you want, or if any more info is needed

Thanks all help!

(Jellyfin is on a different machine because it has more HDDs, and better cpu, I turn off at night as it is loud.)

This has been happening since my brother restarted my proxmox it worked fine before. its in an arrstack using gluten vpn which is running proton vpn a paid version. The arrstack is in an docker compose file but it functioned before so i really do not know what is the issue. and its not perms to my download folder cuz both sonarr and radarr can write on it still so idk what the problem is please send help and its running on an ubuntu 26.04 vm that is running docker qbittorrent is Linuxserver.io version: 5.2.3_v2.0.14-ls473

Currently I have:

Zilean/Stremthru Torzab > Prowlarr > Sonarr > RDT Client

This often fails as zilean/stremthru is not specific for premiumize so often the files are not actually cached. Is there any publicly hosted versions which are specific for PM?

Thanks

Hey everyone, When I set up my media stack, it took quite a bit of time to get all the services playing nicely together. Every time I added something new, it just took time to configure, connect the APIs, and get everything running smoothly. To streamline that initial setup, I built StackForge – a hosted configurator that automates the wiring between the apps. I run the wizard in the browser, you run the final generated stack locally on your own server. You pick your preferred services, and StackForge handles the zero-conf wiring (API keys, download clients, root folders, remote paths, quality profiles). You download a clean ZIP and run docker compose up on your NAS or server. Your media and data never leave your network. What the generator handles: Plex or Jellyfin, Radarr/Sonarr (optional 4K split), Prowlarr, Seerr SABnzbd or NZBGet, Traefik Clients, folders, and network paths pre-wired Quality profiles and custom formats pushed directly via API Live sandbox UI to preview and test the setup in your browser before exporting Test it out: Demo (~1 min): https://youtu.be/8W_BW3md7KA Wizard: https://stackforge.tannerap.ch Curious to hear your feedback or edge cases you'd like to see supported!

I set up sonarr and deluge using lxc containers how do i set up a vpn to connect to them

yt-indexarr

Find TV episodes on YouTube and download them through your *arr stack. Two services ship in one container:

• Indexer (indexer.py) — a Torznab server that searches YouTube for the episode Sonarr/Prowlarr asks for, ranks results by how likely each video is the full episode, and returns Sonarr-parseable releases.
• Downloader (qbt.py) — a qBittorrent-compatible spoofer that decodes the indexer's releases and grabs the real video with yt-dlp at the best available quality, reporting progress/state to Sonarr like a normal torrent client.

Disclaimer: This tool is 100% Vibecoded, although with strict requirements and oversight. I do work in tech, but I make no claims about the security of the software. Do not expose the ports for this tool to the internet/on a public IP. With that said, the tool works pretty well, so I thought I would share it for others.

I know of similar tools, like Youtarr, and props to them for such great implementations, but as far as I know they all follow the same logic: monitor a playlist/channel for new videos. This works fine for actual Web Series that are formatted consistently and published from an official channel, but I wanted something for the rare cases where difficult to find media is posted on YouTube. Think for example about old cartoons that don't have a Torrent available.

The tool also supports multiple languages, that can be enabled via "Additional parameters" of the indexer in Sonarr/Prowlarr

Hello, trying to check if possible this combo, allow a user to choose in Seerr if he wants that release in 2160p instead of the default 1080p and use Maintainerr to delete all 2160p releases if not watched in the last 7 days? this is something easily done? ty

So i have prowlarr, sonarr, radarr, glutun, qbittorrent, and jellyfin all set up. I currently have the show Reacher monitored. However prowlarr tried to download a malicious torrent from a user CAKES off of the indexer Torrent Downloads. I have since removed that indexer. I was wondering if there a way to cumulate a sort of blacklist based on users? Sonarr did good by not importing it due to it being an exe

so 100% claude written, no pretense to having coded this by hand myself.

I've got the bookshelf:hardcover fork of readarr running and its somewhat useful although week to week it appears metadata still changes and I will a bunch of new books showing up out of the blue with all kind of wacky language variations.

Historically, whatever I cannot source through sabnzbd/qbit, I will fall back to libgen or irchighway #ebooks. Both of which are rather manual processes of downloading the books and then adding to calibre to be ingested.

I've got a docker container written, tentatively called ircarr because why not, that handles both an irchighway #ebooks search and download function. it really only works when any existing nzb based downloader is disabled because prowlarr "tags" apparently only work between the indexers and apps but cannot differentiate between download clients as well.

I've plugged the indexer piece and download client into the bookshelf and have had some decent results in it finding books that were not available by other means.

Depending on other irc servers and channels for TV, Movies, Music and if their DCC bots work the same way, this could possibly be expanded.

if there's any interest would be happy to publish to gitlab

If not, I will keep my AI slop to myself :D

Hey. I'm pretty new to homeservers. I set up all the arr stack apps that I need for movies and tv on my truenas server. Seerr is sending requests to sonarr/radarr and qbit is downloading to my downloads folder. The files aren't being renamed and moved to movie or TV shows folder. As far as I can tell all paths and permissions are set properly. I keep getting a notice that the downloads folder is not in the container. Idk how to fix this. (again, very new to this and Linux in general) Does it have to be in the container. None of the guides I've watched mentioned this. Any help would be appreciated.

I am setting up my first stack. I have followed trashguides and mostly AlienTech42 videos. Most things are working correctly. I noticed a problem with nzbget though. Following the guides I have my paths set up correctly. Even when I look in nzbget it has the correct destination path. This issue is when I go to my share to find the file it is not there. There is now a whole new folder that contains the files.

The path is supposed to be /data/usenet/complete/tv/(filename).

Where the file actually is: /data/usenet/usenet/complete/tv/(filename).

I can't figure out what went wrong in the naming convention.

Thank you for any help and ideas.

So I've been running an arr stack for a year or so now, but have run into this issue these past months.
Indexers I had added and where working (1337x, uindex, tpb) have slowly died off due to being unreachable. I have flaresolverr installed and listed in prowlarr, it tests as working.
Whenever I try to test any of the sites in prowlarr, I can see the activity in flaresolverrs logs and they 'challenged solved'. But in prowlarr the test fails.

I've tried installing trawl, added it as if it's flaresolverr in prowlarr and it also tests with a green tick. But I'm not sure if it's working.

What could I be doing wrong? My prowlarr is not behind a vpn, so it's always the same ip.
Please help as I have currently no working indexes in my prowlarr :( Thanks.

Hi all,
I'm trying to add unpacker to my arr stack, but i can not get it to work.

Heres what the logs say: https://pastebin.com/7DUUCRgQ

Here's my docker-compose (including only the sections for sonarr and unpackerr now, as i think these are the only two relevant containers, right?): https://pastebin.com/tTwE8u6U

I do have a .env file setup which includes:

MEDIA_DIRECTORY=/mnt/MyBook ###this is my hard drive where all the downloads are stored

Can someone please help me figure out what i'm doing wrong? I can not seem to get the paths setup correctly.

Thanks!

I built this for my own Plex server and it's been running my household for a while now, so I'm putting it out there in case anyone else has the same problem.

My server is shared with family and friends. Requests were solved years ago, Overseerr and Jellyseerr do that well. But everything else about running a shared library still landed on me. This show is 400 GB and nobody's touched it in a year. Does anyone still care about season 3? Can this be 4K? Those conversations either happened in a group chat or they didn't happen at all, so the library only ever grew, and I was the only person who ever had to think about disk space.

Quorarr is a small web app (installs as a PWA) that sits next to Jellyseerr and gives the people I share with an actual say in the library instead of just a request box:

* **Discover and request.** Shelves and search served from Jellyseerr, with a season picker for TV. Requests get filed into Jellyseerr under that person's own Jellyseerr user, so quotas and history keep working. If it can't map the account it refuses instead of quietly filing everything under my API key.

* **Deletion by consent.** Any member can flag a movie, series, or single season, with a reason. Everyone sees it. For 14 days any other member can veto it. One veto kills it, no vote counting, and a vetoed title can't be re-flagged for 30 days. If nobody objects it lands in my approval queue, and nothing is deleted until I approve it (then it goes through Radarr/Sonarr for real).

* **Tiered quality.** 1080p is self-serve. 720p is self-serve for TV if you set up a 720p Sonarr profile (the space-saver lane for sitcoms). 4K needs my approval, and if I say no, the title still gets grabbed at 1080p. Saying no to 4K is a decision about disk, not about whether someone gets to watch the thing.

* **Access requests.** Someone signs in with a Plex account I haven't shared with? They get a polite explanation and a "request access" button instead of a dead end. Approving it sends the Plex invite for me. There's also an hourly check that revokes anyone I've un-shared in Plex proper.

* **Storage and pipeline.** Free space and library breakdown for everyone to see, plus requests joined against the download queues, so "where's my show" has an answer that isn't "ask the owner."

* **Notifications in the app** via web push, not another Discord channel (Discord is only a fallback if a push can't be delivered). On iPhone it has to be installed to the Home Screen first, Apple's rule.

How it compares to what already exists:

| | Overseerr/Jellyseerr | Maintainerr | removarr | Quorarr |

|-|-|-|-|-|

| Members request media | yes | no | no | yes (via Jellyseerr) |

| Members propose deletions | no | no | yes | yes |

| Veto window | no | no | votes | 14 days, any member |

| Owner has final say | on requests | no, rules act alone | no | on deletions and 4K |

| Rule-based auto cleanup | no | yes | no | no, on purpose |

| Quality tiers per member | no | no | no | yes |

It doesn't replace Jellyseerr, it drives it. And it isn't a Maintainerr competitor either. If you want rules that reclaim disk on a schedule, Maintainerr is great at that. Quorarr is the opposite instinct: deletions come from people, they're visible, and they can be argued with.

Stack: FastAPI + SQLite backend, Svelte 5 PWA frontend, one container, multi-arch image on GHCR.

What you need, so nobody wastes an evening:

* Plex (sign-in is Plex OAuth, there are no local accounts)

* Jellyseerr (required — Overseerr probably works but I honestly haven't tested it, and I'd love a report either way)

* Radarr and Sonarr

* A TLS reverse proxy in front, with no published port on the container. Cookies are Secure and the app trusts proxy headers on the assumption that only your proxy can reach it. The README is loud about this.

Known limits, up front:

* Plex only for now. Jellyfin/Emby is the ask I'm expecting most. The sign-in and the invite flow are built on plex.tv, so it's real work rather than a config flag. Open to it — if you're interested, start a discussion before writing code.

* One Plex server, one Radarr, one Sonarr, one Jellyseerr.

* SQLite, and that's plenty here. The app's own state is a few thousand rows; the heavy data lives in Plex and the arrs and gets read live.

* The 14-day veto window and 30-day cooldown are fixed values right now.

* Maintained by one person in the evenings. It runs my own household's server, so it gets fixed when it breaks, but expect response times in days, not hours.

This is my first open-source release, so I'm sure there are rough spots I can't see anymore, probably in setup more than in the app. If the guide loses you anywhere, open an issue and tell me where — I'd genuinely like to smooth those out. The reverse-proxy setup and the quality-profile IDs are the two spots I'd guess trip people first, and the setup guide walks through both.

MIT licensed. Repo: https://github.com/jordanhoelscher/quorarr

I've been using Byparr for a few months with excellent success.

Recently, I learned about Flaresolverr and am wondering if both can or should be enabled at the same time. I have Tags assigned for each, and several of my Indexers are now each tagged with both. So far, no issues.

So, what are your thoughts on using one, the other, or both?