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

Updated Troubleshooting (markdown)

garfield69 2024-02-25 05:41:26 +13:00
parent fb46c15e51
commit 70060b7ff3
1 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Troubleshooting.md

@ -106,10 +106,19 @@ See [[How to provide a Jackett Enhanced log for a ticket|https://github.com/Jack
This type of error is almost always a problem outside of Jackett's control.
Usually caused by one of the following:
- 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 [Cloudflare](https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1) (1.1.1.1 and 1.0.0.1) or [Google](https://developers.google.com/speed/public-dns/docs/using) (8.8.8.8 and 8.8.4.4) or [Quad9](https://www.quad9.net/) (9.9.9.9 and 149.112.112.112).
- If your ISP is still able to trap your DNS lookups when using a public DNS then try https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation or DNS over TLS https://fedoramagazine.org/use-dns-over-tls/. An alternate approach is to use a VPN service or a proxy server.
- One of the following: Firewall, anti-malware, Ad-blocker, Accountability app. Review your security app and add the required rule to allow Jackett access to the WAN, and/or the port and/or the site's address, whichever is relevant.
- The site is broken, their server is terminating the connection due to some internal error. 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. Edit the indexer config and see if there is any alternate SiteLinks you can try instead. If there are none, then there is nothing you can do about this but wait for the provider to fix.
- 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 [Cloudflare](https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1) (1.1.1.1 and 1.0.0.1) or [Google](https://developers.google.com/speed/public-dns/docs/using) (8.8.8.8 and 8.8.4.4) or [Quad9](https://www.quad9.net/) (9.9.9.9 and 149.112.112.112).
- If your ISP is still able to trap your DNS lookups when using a public DNS then
- try https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation or DNS over TLS https://fedoramagazine.org/use-dns-over-tls/.
- An alternate approach is to use a VPN service or a proxy server.
- One of the following: Firewall, anti-malware, Ad-blocker, Accountability app.
- Review your security app and add the required rule to allow Jackett access to the WAN, and/or the port and/or the site's address, whichever is relevant.
- The site is broken, their server is terminating the connection due to some internal error.
- 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.
- Edit the indexer config and see if there is any alternate SiteLinks you can try instead.
- If there are none, then there is nothing you can do about this but wait for the provider to fix.
In the rare event none of the above applies, 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]]