I have bought my first proper home server and am setting up a full stack of media services on truenas scale after years of doing everything manually. In that regard I have set up jellyfin, sabnzbd and radarr, and the next step is to add jellyserr it seems. But then I stumble across prowlarr and cannot figure out if it is a contender to or a supplement to jellyserr. Can somebody tell me what the difference is, if I should use both if they are complementing each other or which you are using if they are competing?
They are two different programs. Prowlarr is an index manager and overserr/jellyserr are requesters.
Indexer pulls a listing of available files from as many indexing services as you add. 1337x, NZBgeek, etc.
Overserr is like a front end for your entire stack. You just tell it what you want media you want and it sends the requests to the stack to figure out.
Overserr talks to -> radar/sonarr talks to -> prowlarr talks to -> sabnzbd/qbit.
Jellyseerr is the front end to download movies, the thing that get shown to you or your users, then it uses radarr and sonnarr to get movies and, radarr and sonnar then get the movie using torrent providers in prowlarr, then they send the torrent to qbittorrent or another bittorrent client.
Also, Jellyseerr is awesome when all of this is working perfectly!
theyre not contenders, they all work in unisson! even tho you can skip using Jellyseerr and get your movies on sonarr or radarr, but their UI is crap and confusing tbh…
I have radarr working fine in combination with sabnzb (i am on usenet instead of torrenting). What does prowlarr do in between them?
The other person is wrong. Your Usenet indexers will work on prowlarr. The most important feature that Prowlarr has that gets overlooked is that it will sync your indexers into the other arr programs like radarr sonarr, lidarr, etc… automatically. You make a change on prowlarr it syncs to them all. It’s the ideal solution for managing indexers all in one place.
Thanks! So prowlarr is the only place my indexers should be configured. And sonarr and radarr should only be configured with downloaders?
If you are only using usenet then prowlarr will do nothing. Prowlarr aggregates torrent indexers and searches them for your request
Prowlarr and Jellyseerr are two tools you use together.
Prowlarr is an index manager, for Radarr and Sonarr. With Radarr and Sonarr, generally you’d have to provide individual indexes (in the case of torrents, trackers) for each individual instance of Radarr and Sonarr. With Prowlarr, you basically have a central database of trackers, organized by tags (like movies or TV shows), that will then feed that information to Radarr and Sonarr.
Jellyseerr is like the requesting interface. If you want to watch a show or movie, you place a request with Jellyseerr, that gets sent over to Radarr or Sonarr, and then either instance will then search for the content using the indexes provided by Prowlarr. Radarr or Sonarr will then begin the download, and then organize it within your media files.
I never heard of those tools, but I have a jellyfin server. By “support” for jellyfin, does that mean it has like a plugin or something to request media from within jellyfin?
I haven’t set up jellyserr yet, so I haven’t seen it in action yet, but if it works the way I understand it should, it is that when media is downloaded it is automatically updated into your jellyfin server.
See the reply by @zewm@zewm@lemmy.zip. Jellyserr is the gui where you search for the media. It then sends radarr/sonarr/… the request which works along prowlarr to download the usenet or torrent file and makes your usenet/torrent client download it. When the download is complete it is moved to the correct place, renamed by your rules etc and inserted into your media server.
Radarr is for movies, Sonarr is for shows, you have one for audiobooks, one for music, comics etc.
