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 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.
If you're linked here for support remember to get them the information from the actual trace log file, put the logs in a pastebin and show us context around what we need to see. 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.
- Do not simply provide the whole log file unless explictly asked.
- Do not upload the logs directly to discord as a file nor paste them as a wall of text unless explictly asked.
- When the relevant section is ~ 15 lines, it may be acceptable to paste in discord in a code block like this:
``` words here ```
- Do not attempt to get logs while a spammy task is running such as an RSS refresh.
- Do ensure Logging is set to Trace (or Debug if requested).
- Do ensure the logs you provide capture the issue
What you need to do is:
It is not suggested to use pastebin as their filters have a tendency to block the logs.
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:
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
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.
Debug logs contain normal log items, and trace logs contain debug log items, so if you're logging at a trace level, you only need to provide trace logs.
If you're unable to access the Prowlarr UI to set the logging level you can do so by editing
config.xml in the AppData directory by setting the LogLevel value to
Trace instead of
<Config> ... <LogLevel>debug</LogLevel> ... </Config>
You can clear log files and the logs database directly from the UI, under
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
When Debug log level is enabled, additional Prowlarr.debug.txt rolling log files will be present. This log files contains
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
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.
The best place to look when Prowlarr will not start after an update is your log files, before trying to start Prowlarr again, use Logging and Log Files to find them and increase the log level.
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"
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 posts), please create a post on our subreddit or swing by our discord. If there are others with the same issue, then rest assured we are working on it.
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.