1
0
Fork 0
mirror of https://github.com/Jackett/Jackett synced 2025-01-03 13:46:10 +00:00

Updated Troubleshooting (markdown)

garfield69 2021-04-02 20:07:08 +13:00
parent 852e6af2d0
commit 5417bded88

@ -60,11 +60,11 @@ Possible reasons:
- The Web Site is not responding, or is going too slow (perhaps due to a current DDoS attack) and it is taking too long to respond within the default allocated wait time (Use you browser to access the site and time how long it takes to do a torrent search. If it exceeds 30 seconds then Jackett will most likely not be able to use the site).
- Your VPN or Proxy is broken or disconnected your session (Access the site via a Browser on the same machine that is running Jackett, and through the same VPN or proxy as Jackett, and if it does not work then sort out your VPN / proxy problem).
- The site is being blocked by an ISP provider. Use a Browser on the same machine that is running Jackett, access the Site using the same address as the Indexer's config **SiteLink** and confirm that this is the case. Try using any of the **Alternate** Site Links in the indexer config and see if they work for you. Another possible solution you can try is to stop using the DNS provided by your ISP and switch to one of the public ones from Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). An alternate approach is to use a VPN or proxy.
- The site is using an Anti-DDoS protection challenge that Jackett cannot solve (usually you can check this with your browser, and if you see a challenge then there is little Jackett can do about it).
- The site is using an Anti-DDoS protection challenge that Jackett cannot solve (usually you can check this with your browser, and if you see a challenge then take a look [here](https://github.com/Jackett/Jackett/wiki/Troubleshooting#error-connecting-to-flaresolverr-server) and see if a FlareSolverr server can help).
- Your computer's firewall or Anti-Malware software or Router is blocking Jacket from accessing the WAN or the Port (access your security app, check the logs and add the required exception rule to allow access).
- The Docker version of Jackett is unable to access your Network (sometimes fetching the latest docker image will resolve this issue).
- The Docker version of Jackett is unable to access your Network. Do all the other Jackett Indexer fail with the same problem? (Sometimes fetching the latest docker image will resolve this issue).
- The web site is filtering out non-local IP addresses. Some site such a Zelka for example, block non-Bulgarian IP addresses. Use a VPN where you can specify a server using an IP will pass the Web sites filter.
- Plenty more reasons tbp
- Plenty more reasons TBP.
If all the above does not apply to you, then the next thing to do is to provide an **enhanced** log so that the Jackett team can investigate.
See [[How to provide a Jackett Enhanced log for a ticket|https://github.com/Jackett/Jackett/wiki/Troubleshooting/#how-to-provide-a-jackett-enhanced-log-for-a-ticket]]