Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on
But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of .NET, version of Prowlarr, download client and its version. If you are using Docker please run through Docker Guide first as that will solve common and frequent path/permissions issues. Otherwise please have a docker compose handy. How to Generate a Docker Compose Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files section to turn your logging up to trace, recreate the issue, pastebin the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.
The more we know, the easier it is to help you.
It is likely beneficial to also review the Indexer, Application, and Download Client Issues Common Problems.
If asked to provide the indexer response for development or debugging continue reading this blue section...otherwise continue to the steps below. For debugging indexer responses, it is likely helpful to go to
settings/development(hidden page) in Prowlarr and temporarily enable Enhanced Indexer Logging to log the Indexer's Response. It should not be kept on all the time
If you're asked for debug logs your logs will contain debug and if you're asked for trace logs your logs will contain trace. If the logs you are providing do not contain either then they are not the logs requested.
To provide good and useful logs for sharing:
Ensure a spammy task is NOT running such as an RSS refresh
Warnings:
Important Note:
When using 0bin, be sure to disable colorization and do not burn after reading.
Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use N++. You can use the Notepad++ "Find in Files" function to search old log files as needed.
Unix Only: Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use grep. For example if you want to find information about the movie/show/book/song/indexer "Shooter" you can run the following command grep -inr -C 100 -e 'Shooter' /path/to/logs/*.trace*.txt If your Appdata Directory is in your home folder then you'd run: grep -inr -C 100 -e 'Shooter' /home/$User/.config/logs/*.trace*.txt
* The flags have the following functions
* -i: ignore case
* -n: show line number
* -r: recursively check all files in the path
* -C: provide # of lines before and after the line it is found on
* -e: the pattern to search for
The log files are located in Prowlarr's Appdata Directory, inside the logs/ folder. You can also access the log files from the UI at System => Logs => Files.
Note: The Logs ("Events") Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.
The update log files are located in Prowlarr's Appdata Directory, inside the UpdateLogs/ folder.
The logs can be long and hard to read as part of a forum or Reddit post and they're spammy in Discord, so please use Pastebin, Hastebin, Gist, 0bin, or any other similar pastebin site. The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Do not forget to wait for spammy tasks like an RSS sync or library refresh to finish.
You can change the log level at Settings => General => Logging. Prowlarr does not need to restarted for the change to take effect. This change only affects the log files, not the logging database. The latest debug/trace log files are named prowlarr.debug.txt and prowlarr.trace.txt respectively.
If you're unable to access the UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.
<Config>
[...]
<LogLevel>debug</LogLevel>
[...]
</Config>
You can clear log files and the logs database directly from the UI, under System => Logs => Files and System => Logs => Delete (Trash Can Icon).
Prowlarr uses rolling log files limited to 1MB each. The current log file is always Prowlarr.txt, for the the other files Prowlarr.0.txt is the next newest (the higher the number the older it is). This log file contains fatal, error, warn, and info entries.
When Debug log level is enabled, additional prowlarr.debug.txt rolling log files will be present. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.
When Trace log level is enabled, additional prowlarr.trace.txt rolling log files will be present. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most, and sometimes less than a minute if you're doing something intensive.
We do everything we can to prevent issues when upgrading, but if they do occur this will walk you through the steps to take to recover your installation.
/tmp directory and deleted critical *Arr files during the upgrade thus causing both the upgrade and rollback to fail. In this case, simply reinstall in-place over the existing borked installation.14-2-4 18:56:49.5|Info|MigrationLogger|\*\*\* 36: update\_with\_quality\_converters migrating \*\*\*
14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items
While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"
Permissions issues are due to the application being unable to access the the relevant temporary folders and/or the app binary folder. Fix the permissions so the user/group the application runs as has the appropriate access.
Synology users may encounter this Synology bug Access to the path '/proc/{some number}/maps is denied
Synology users may also encounter being out of space in /tmp on certain NASes. You'll need to specify a different /tmp path for the app. See the SynoCommunity or other Synology support channels for help with this.
In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any pinned github issues), please swing by our discord. If there are others with the same issue, then rest assured we are working on it.
Please ensure you did not try to use a database from
nightlyon the stable version. Branch hopping is ill-advised.
Fix the permissions to ensure the user/group the application is running as can access (read and write) to both /tmp and the installation directory of the application.
For Synology users experiencing issues with /proc/###/maps stopping Sonarr or the other *Arr applications and updating should resolve this. This is an issue with the SynoCommunity package.
Grab the latest release from our website.
Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run Prowlarr as you normally would.
In your Prowlarr setup, you will need this line:
proxy_set_header Host $host;
If you have any different proxy_set_header you must replace it with the line above.
Note that logs indicating querying indexer ID 0: The 0 ID is a generic test endpoint that allows us to test if *Arr can call back and connect to Prowlarr without actually relying on an indexer working.
Below are some common causes
Cannot determine the frame size or a corrupted frame was received.
Prowlarr had a security issue connecting to the site.
This is typically caused by:
The request timed out
Prowlarr is getting no response from the client. See our General Network & Permissions Troubleshooting guide
This is typically caused by:
Refer to the first FAQ question for the *Arrs for how they work - searches are not automatically executed. For other troubleshooting, refer to the articles below.