mirror
/
Jackett
mirror of https://github.com/Jackett/Jackett
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Troubleshooting (markdown)

garfield69 2023-07-17 17:42:39 +12:00
parent 0973388f02
commit 6fea8db5f1
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Troubleshooting.md

@ -417,7 +417,7 @@ Since this filtering occurs after results are fetched, it is always possible tha
## How to provide a Jackett Enhanced log for a ticket
1. Scroll down to the bottom of the Jackett Dashboard, *tick* the *Enhanced logging* checkbox, and *untick* the *Cache enabled* checkbox
2. Scroll up a bit and *click* on the *Apply server settings* button (enhanced logs will include `Debug` entries, including the HTML of any response, not just `Info` and `Warn` - after applying the settings make sure that the *Enhanced logging* checkbox is still ticked; if it isn't try again)
3. Perform the test with the relevant indexer (avoid using any other indexers to prevent log clutter)
3. Perform the test with the relevant indexer (*avoid using any other indexers to prevent log clutter*)
4. Find the *log.txt* file (linux: `~/.config/Jackett/`, windows: `%ProgramData%\Jackett`, Docker: check your `App config/log directory:` message at the start of your log, usually points to `/config/Jackett`)
5. While Jackett will attempt to redact the log for your privacy and security, edit it with a plain text editor, redacting any personal details, username, password, passkey, hashes, IP address etc. that may have escaped the security filter.
6. Save, then drag-drop the text file into the body of the ticket for us to take a look at.