Add Indexer(+) =>
The tags must match & Cloudflare must be detected for Flaresolverr to be used. A Flaresolverr proxy is disabled if no tags are used.
Saveagain to trigger a force save
Saveagain to trigger a force save
Query successful, but no results in the configured categories were returned from your indexer. This may be an issue with the indexer or your indexer category settings.
With Full Sync enabled, if any of the above change between the *Arr App and Prowlarr then the Indexer will be Synced and Updated in *Arr
This will not install the bits from that branch immediately, it will happen during the next update.
master - - (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. On GitHub, this is the
master branch. Prowlarr does not yet have a stable release.
develop - - (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first after nightly. It can be considered semi-stable, but is still
On GitHub, this is a snapshot of the
developbranch at a specific point in time.
nightly- - (Alpha/Unstable): This is the bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases. This branch is only recommended for advanced users. Issues and self investigation are expected in this branch. Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update. This version is updated immediately.
Warning: You may not be able to go back to
developafter switching to this branch. On GitHub, this is the
:nightlyto the end of your container tag depending on who makes your builds.
|hotio||no stable release yet||
|LinuxServer.io||no stable release yet||
nightly, but then update the Docker container itself (possibly downgrading to an older version).
nightlyfor your given build.
codesign --force --deep -s - Prowlarr.app
That is either due to a corrupt download (so try again), or security issues answered just above this.
To request a feature for Prowlarr, first search on GitHub to ensure no similar request exists, then click here to add your request.
Error creating log databaseindicate issues with logs.db
Error creating main databaseindicate issues with prowlarr.db
.recoveror you wish a more GUI (i.e. Windows) friendly way then follow our instructions on this wiki.
direct_ioas SQLite uses mmap which isn’t supported by
direct_ioas explained in the mergerFS docs here
Restoring to an OS that uses different paths will not work (Windows to Linux, Linux to Windows, Windows to OS X or OS X to Windows), moving between OS X and Linux may work, since both use paths containing
\that Windows uses, but is not supported. You'll need to manually edit all paths in the database.
Re-install Prowlarr (if applicable / not already installed)
Find the location of the AppData directory for Prowlarr
Delete the contents of the AppData directory (Including the .db-wal/.db-journal files if they exist)
Restore from your backup
As long as the paths are the same, everything will pick up where it left off
Restore for Synology NAS
CAUTION: Restoring on a Synology requires knowledge of Linux and Root SSH access to the Synology Device.
On some installations, the user is different than the below commands:
chown -R sc-Prowlarr:Prowlarr *
Execute the following commands:
rm -r /usr/local/Prowlarr/var/.config/Prowlarr/Prowlarr.db cp -f /tmp/Prowlarr_backup/* /usr/local/Prowlarr/var/.config/Prowlarr/
Update permissions on the files:
cd /usr/local/Prowlarr/var/.config/Prowlarr/ chown -R Prowlarr:users * chmod -R 0644 *
If you can only reach your web interface at
http://127.0.0.1:9696, you need to run Prowlarr as Administrator at least once, maybe even always.
Some sites cannot be logged into automatically and require you to login manually then give the cookies to Prowlarr to work. Please see this article for details.
Prowlarr was unable to read your config file on start-up as it became corrupted somehow. In order to get Prowlarr back online, you will need to delete
.xml in your AppData Folder, once deleted start Prowlarr and it will start on the default port (9696), you should now re-configure any settings you configured on the General Settings page.
Your download client stopped working and you're getting an error like
Localhost is an invalid certificate?
Prowlarr validates SSL certificates. If there is no SSL certificate set in the download client, or you're using a self-signed https certificate without the CA certificate added to your local certificate store, then Prowlarr will refuse to connect. Free properly signed certificates are available from let's encrypt.
If your download client and Prowlarr are on the same machine there is no reason to use HTTPS, so the easiest solution is to disable SSL for the connection. Most would agree it's not required on a local network either. It is possible to disable certificate validation in advanced settings if you want to keep an insecure SSL setup.
To disable authentication (to reset your username or password) you will need need to edit
config.xml which will be inside the Prowlarr Appdata Directory
Settings: Generalin the UI and set your username and password
Unless you're in a repressive country like China, Australia or South Africa, your torrent client is typically the only thing that needs to be behind a VPN. Because the VPN endpoint is shared by many users, you can and will experience rate limiting, DDOS protection, and ip bans from various services each software uses.
In other words, putting the *Arrs (Lidarr, Prowlarr, Radarr, Readarr, and Sonarr) behind a VPN can and will make the applications unusable in some cases due to the services not being accessible. To be clear it is not a matter if VPNs will cause issues with the *Arrs, but when: image providers will block you and cloudflare is in front of most of *arr servers (updates, metadata, etc.) and liable to block you too.
In addition, some private trackers ban for browsing from a VPN, which is how Prowlarr works. In some cases (i.e. certain UK ISPs) it may be needed to use a VPN for public trackers, in which case you should then be putting only Prowlarr behind the VPN. However, you should not do that if you have private trackers without checking their rules first. Many private trackers will ban you for using or accessing them (i.e. using Prowlarr) via a VPN.
Depending on your OS, there are multiple possible ways.
Generalon some OS'es, there is a checkbox to launch the browser on startup.
/nobrowser(Windows) to the arguments.
No. This would not be a good thing to do, and this functionality will not be added. It is much better to choose your indexers wisely, pay attention to the stats to remove indexers that are too slow or not producing grabs. Proper pruning and maintenance of your indexers will result in much better results overall, and quicker results on searches from your apps.