mirror of
https://github.com/Jackett/Jackett
synced 2025-01-03 05:36:44 +00:00
Updated Troubleshooting (markdown)
garfield69
parent
874cddaaa6
commit
e245ecd7e4
1 changed files with 6 additions and 6 deletions
|
|
@ -61,7 +61,7 @@ Cancelled tasks errors happen when Jackett gives up waiting for a response from
|
|||
Unfortunately, these are tricky to diagnose.
|
||||
Possible reasons:
|
||||
- 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.
|
||||
- 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does).
|
||||
- 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
|
||||
|
|
@ -109,7 +109,7 @@ 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.
|
||||
- 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does).
|
||||
- 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
|
||||
|
|
@ -119,7 +119,7 @@ Usually caused by one of the following:
|
|||
- 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.
|
||||
- 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does).
|
||||
- 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.
|
||||
|
||||
|
|
@ -164,7 +164,7 @@ Possible reasons:
|
|||
- Have you enabled freeleech only in the indexer config? It may be that the site does not have any freeleech torrents to show. Or the site may have enabled a global freeleech mode, but the search page does not show this info.
|
||||
- Try turning off the freeleech option and see if you get results.
|
||||
- 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.
|
||||
- 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does).
|
||||
- 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
|
||||
|
|
@ -212,7 +212,7 @@ Check this by using the [Uptime](https://www.uptrends.com/tools/uptime) web site
|
|||
- In the event there is only the one domain, then raise a Ticket and let us know.
|
||||
|
||||
If however, more than one indexer is reporting this error, then the next most likely explanation is that you are having some kind of issue with reaching your DNS provider, or perhaps your ISP provider is blocking your access to these sites.
|
||||
- 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.
|
||||
- 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does).
|
||||
- A 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
|
||||
- Use a VPN service or a proxy server.
|
||||
|
|
@ -301,7 +301,7 @@ If that does not get it working, then
|
|||
|
||||
If none of the above has helped, then its time to look at some of these possible reasons:
|
||||
- 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.
|
||||
- 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does).
|
||||
- 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
|
||||
|
|
|
|||
Loading…
Reference in a new issue