Prowlarr Install

[Skyler]

I'm looking to replace my Jackett install with Prowlarr, but I'm not finding any install guides on this forum or online. Has anyone installed Prowlarr on Truenas yet?

 

[Jailer]

Found this on github. Haven't tried it but it looks pretty simple.

https://github.com/Thefrank/freebsd-port-sooners/blob/main/Prowlarr_Installation_TrueNAS_GUI.md

 

[Skyler]

Worked perfectly. Thanks!

For anyone else following these instructions, once Prowlarr is installed it'll be available at *JailIP*:9696. The instructions didn't make it clear on how to access Prowlarr once it was installed. Had to do some digging to find the port info.

 

[FrankNAS]

So I should add the port number to the guide? :)

 

[Skyler]

So I should add the port number to the guide? :)

Lol! Great work on the guide. One other item I noticed is that I wasn't able to auto-update Prowlarr until I moved the config directory to a different location. I do this anyways will all of my plugins, so not a big deal. I followed this guide years ago to move all of the config directories to a separate App dataset.

Now if I could just figure out how to migrate Radarr to the .NET Core version... Still stuck on mono

 

[HitmanThe47]

Thanks Guys...

This

https://github.com/Thefrank/freebsd-port-sooners/blob/main/Prowlarr_Installation_TrueNAS_GUI.md

and

"I followed this guide years ago to move all of the config directories to a separate App dataset."

Worked like a charm...

 

[FrankNAS]

Now if I could just figure out how to migrate Radarr to the .NET Core version... Still stuck on mono

My guide for Radarr does not cover migrating because I HIGHLY suggest a new jail but you can just remove mono and/or Radarr and install my package. Radarr will migrate the DB.

 

[gt2416]

Used your guide for sonarr/ radarr and prowlarr, works beautifully. Love prowlarr compared to jackett which always seems to have issues for me.
One note, after installing prowlarr I had to move my data directory manually so that I could use the inbuilt updater. Loving it, thanks for the hard work.

 

[FrankNAS]

hrm. more than one person has stated that they have to move out or change the data dir. I will check to see why `install` is not correctly setting permissions.

edit:
does `%%DATADIR%%/data` not work as a default?
@gt2416 / @Skyler did you change this location via `sysrc` or did you edit the rc file?

 

[gt2416]

I changed it using sysrc. Its not a permissions issue, its that the datadir is in the same directory as the app dir. This prevents prowlarr from auto updating, to I moved the data dir somewhere else and it worked.

 

[FrankNAS]

I updated the prowlarr package to put the data/logs/config into a different place

 

[Grinas]

Prowlarr was something i looked into recently after hearing about it but decided against it due to lack of support and lack of indexers compared to jackett.

For those that tried it what do you like about it and what are the pros and cons of it vs jackett?

------UPDATE------
here is what i found when i tested today.

1. Can only add 1 indexer at a time with Jackett i can add as many as i want.
2. Not possible to edit or add your own indexers like with jackett.
3. Lacking in online documentation and guides compared to jackett.
4. seems to be for users of the arr apps like sonarr and radarr than generic like jackett. I have custom applications that use jackett and it does not appear to be possible from what i can see to use them with prowlarr.
5. Overly complex UI compared to Jackett with things that should not be needed.
6. I dont really see any benifits of prowlarr over Jackett but there may be if you are an arr app user.

instructions to install from command line

Code:

# add boot=1 for autostart, if you want it to have a static IP remove dhcp=1 and add ip4_addr="vnet0|X.X.X.X/24"
iocage create -n pr -r 12.2-RELEASE vnet=1 dhcp=1 allow_mlock=1 allow_raw_sockets=1
# go to jail -f to start if not already started
iocage console pr -f
# create user
pw user add prowlarr -c prowlarr -u 349 -d /nonexistent -s /usr/bin/nologin
# download prowlarr package
fetch https://github.com/Thefrank/freebsd-port-sooners/releases/download/20211015/prowlarrdotnet-0.1.1.978.pkg
# install prowlarr
pkg install prowlarrdotnet-0.1.1.978.pkg
# enable it to autostart in jail
sysrc prowlarrdotnet_enable=TRUE
# start prowlarr
service prowlarrdotnet start



#### For debugging ####
# if you have issues tail this log file and restart prowlarr
tail -f /var/db/prowlarrdotnet/logs/prowlarr.txt
service prowlarrdotnet stop
# start prowlarr not as a service. make sure to stop it as a service first.
/usr/local/prowlarrdotnet/Prowlarr --data=/usr/prowlarrdotnet/ --nobrowser

 

[bakerboy448]

1. Can only add 1 indexer at a time with Jackett i can add as many as i want.

Correct. but [a feature requests exist](https://github.com/Prowlarr/Prowlarr/issues/407); you can also do it via the API

1. Not possible to edit or add your own indexers like with jackett.

Not sure where or what gave you that impression. [Custom YML is supported](https://wiki.servarr.com/prowlarr/indexers#adding-a-custom-yml-definition)

1. Lacking in online documentation and guides compared to jackett.

Where did you look? Did you look at the [wiki](https://wiki.servarr.com/prowlarr/)? It doesn't appear so based on your comment. We have significantly more documentation than Jackett.
Third party guides are maintained and created by the community - be the change you wish to see.
Prowlarr does of course have a quickstart guide on the wiki.

1. seems to be for users of the arr apps like sonarr and radarr than generic like jackett. I have custom applications that use jackett and it does not appear to be possible from what i can see to use them with prowlarr.

Again, not sure where or what gave you that impression. Prowlarr provides a newznab or torznab endpoint for every indexer. This is the same that Jackett does (with Prowlarr supporting usenet as well) [This is also on the wiki](https://wiki.servarr.com/prowlarr/indexers#viewing-an-indexer-id-or-url)

1. Overly complex UI compared to Jackett with things that should not be needed.

Prowlarr is not trying to be Jackett, so that's just an opinion there.

1. I dont really see any benifits of prowlarr over Jackett but there may be if you are an arr app user.

Faster, stats, usenet support, has an actual dev team behind it (Jackett has no devs only 2 or 3 `contributors` who do what they can)

 

[Grinas]

Thank you for your response.

Correct. but [a feature requests exist](https://github.com/Prowlarr/Prowlarr/issues/407); you can also do it via the API

a feature requests does not mean it will ever be implemented.

Not sure where or what gave you that impression. [Custom YML is supported](https://wiki.servarr.com/prowlarr/indexers#adding-a-custom-yml-definition)

As you can see from that link at the time of my initial comment that page did not exist hence why me or anyone who was looking would think that you can not create your own indexers. As you can also see some of that documentation is wrong. As its missing jail installation. FYI for a jail installation you have to create Custom dir in this path /usr/local/prowlarrdotnet/Definitions/ and then add your .yml there.

Where did you look? Did you look at the [wiki](https://wiki.servarr.com/prowlarr/)? It doesn't appear so based on your comment. We have significantly more documentation than Jackett.

Every where. Jackett has documentation for installation on FreeBSD considering this thread was created to help people install prowlarr suggests that your mistaken about prowlarr having better docs than jackett. Please note i am also including third party docs such as blogs, tutorials etc.. in this. Also at the time of my comment ye did not have documentation for custom indexer while jackett did. These are just a few things i searched for. The was many more things i was searching for documentation on that i could not find and had to figure out. If you have custom use cases for jackett/prowlarr you will find far more information regarding jackett than you will with prowlarr. This is more than likely due to jackett being around a lot longer. Im sure in time prowlarr will have documentation on par with jackett.

Third party guides are maintained and created by the community - be the change you wish to see.
Prowlarr does of course have a quickstart guide on the wiki.

This quickstart guides are more targeted at arr users. For jackett there is a lot more documentation for people using custom application/use cases and if its not in the documentation then you will be able to find it on blogs, reddit etc.. Again im sure this will change in time.

Again, not sure where or what gave you that impression. Prowlarr provides a newznab or torznab endpoint for every indexer. This is the same that Jackett does (with Prowlarr supporting usenet as well) [This is also on the wiki](https://wiki.servarr.com/prowlarr/indexers#viewing-an-indexer-id-or-url)

I dont think that docs is anywhere on par with what jackett have or what you can find on jackett. Again there was a reason this thread was created. There is step by step in jackett on how to get torznab, rss feeds etc...

Prowlarr is not trying to be Jackett, so that's just an opinion there.

I understand that I am just making a point that in my opinion it is overly complex for what it does and it seems to be targeted at arr users. If you use arr apps then great go for Prowlarr. If you need something that can integrate with other solutions like qbittorrent, custom app etc.. then you will find far more info on jackett.

Faster, stats, usenet support, has an actual dev team behind it (Jackett has no devs only 2 or 3 `contributors` who do what they can)

I tested a search of 70+ torrent indexers(which took forever to enable with Prowlarr) with both jackett and prowlarr and found little to no speed difference. Im talking max a second or 2. I have no need for usenet or stats. I can generate stats using the logs very easily.

In regards to dev team. Any feature or bugs i found were resolved pretty quickly with jackett so im not sure your point is valid.


Considering you created an account on here to just respond back to my post it would seem pretty clear that your view is NOT impartial. In my post i have provided an impartial view of the prowlarr and all the facts i said were correct at the time. Just to be clear here i am not bashing prowlarr or jackett. I just gave a fair view of why i prefer jackett. Things could change and i could prefer it in the future. Also currently all those points in my post except #2 are still valid.

If you want to provide the benefits of Prowlarr vs Jackett then please create a new thread doing so instead of commenting on a thread about installing it.

 

[FrankNAS]

Well, this thread war was fun. Prowlarr is now on the official ports tree: https://www.freshports.org/net-p2p/prowlarr/

If you are unhappy with Prowlarr there is always Jackett and NZBHydra2 as two good alternatives

 

[gt2416]

Ohh niiiice

 

[fredotask]

Hello all and thank you for this guide @FrankNAS

My Prowlarr installation seems to be OK, Prowlarr is running on my TrueNas but no accessible via <jail IP>:9696
Got an ERR_CONNECTION_REFUSED in my navigator.

I've installed it with the following commands :
iocage create --name prowlarr --release 12.2-RELEASE dhcp=1 boot=1 iocage exec prowlarr mkdir /mnt/config iocage fstab --add prowlarr /mnt/datapool/apps/prowlarr /mnt/config nullfs rw 0 0 iocage exec prowlarr sed -i '' 's/quarterly/latest/g' /etc/pkg/FreeBSD.conf iocage exec prowlarr "pkg update && pkg upgrade" iocage exec prowlarr pkg install prowlarr iocage exec prowlarr sysrc prowlarr_enable=YES iocage exec prowlarr sysrc prowlarr_data_dir=/mnt/config iocage exec prowlarr service prowlarr start

Prowlarr user/group exist and others *arr services are working well.
Is it something wrong here ?

 

[FrankNAS]

forgot mlock for jail?

 

[fredotask]

forgot mlock for jail?

Eurêka !
It works now, thank you.

 

[CarlB]

Installed using the guide, but the UI gives me the following error.

Code:

Updating will not be possible to prevent deleting AppData on Update

Version: 0.1.10.1375
.NET: Yes (6.0.0)
DB Migration: 14
Database: Sqlite 3.37.2
AppData directory: /usr/local/share/prowlarr
Startup directory: /usr/local/share/prowlarr
Mode: Console

EDIT: Made a separate directory for the app in /config. Updates are working now.

Code:

iocage exec prowlarr mkdir /config
iocage fstab -a sonarr /mnt/vol0/FreeNAS/apps/sonarr /config nullfs rw 0 0
iocage exec prowlarr sysrc prowlarr_data_dir="/config"