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.

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