mirror of
https://github.com/Jackett/Jackett
synced 2024-12-22 07:43:13 +00:00
Updated Troubleshooting (markdown)
garfield69
parent
b051b6158f
commit
3a64e72cde
1 changed files with 21 additions and 9 deletions
|
|
@ -60,14 +60,22 @@ See [[How to provide a Jackett Enhanced log for a ticket|https://github.com/Jack
|
|||
Cancelled tasks errors happen when Jackett gives up waiting for a response from a http GET when there is no reply within the default time limit (usually around 100 seconds).
|
||||
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. 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.
|
||||
- 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 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 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 [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.
|
||||
- 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 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 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 Web Site is not responding, or is going too slow (perhaps due to a current DDoS attack) and is taking too long to respond within the default allocated wait time (use your 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).
|
||||
- For Docker users, there can be clashes between docker containers using different IP4/IP6 defaults.
|
||||
To ensure all your docker images use the same IPv you could try disabling IP6 on all by adding:
|
||||
- To ensure all your docker images use the same IPv you could try disabling IP6 on all by adding:
|
||||
```
|
||||
sysctls:
|
||||
- net.ipv6.conf.all.disable_ipv6=1
|
||||
|
|
@ -77,8 +85,11 @@ to your Docker compose file, or:
|
|||
--sysctl net.ipv6.conf.all.disable_ipv6=1 \
|
||||
```
|
||||
to the Docker run command (depending on which you're using), see if that makes a difference.
|
||||
- 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), or shutting down the docker image and starting up a fresh one.
|
||||
- The web site is filtering out non-local IP addresses. Some site such a Zelka for example, used to block non-Bulgarian IP addresses. Use a VPN service where you can specify a server using an IP that will pass the Web site's IP filter.
|
||||
- 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
|
||||
- or shutting down the docker image and starting up a fresh one.
|
||||
- The web site is filtering out non-local IP addresses.
|
||||
- Some site such a Zelka for example, used to block non-Bulgarian IP addresses. Use a VPN service where you can specify a server using an IP that will pass the Web site's IP filter.
|
||||
|
||||
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]]
|
||||
|
|
@ -144,7 +155,8 @@ Possible reasons:
|
|||
- 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 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 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 Web Site is not responding, or is going too slow (perhaps due to a current DDoS attack) and is taking too long to respond within the default allocated wait time (use your 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).
|
||||
- The Web Site is not responding, or is going too slow (perhaps due to a current DDoS attack) and is taking too long to respond within the default allocated wait time
|
||||
- Use your 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.
|
||||
- For Docker users, there can be clashes between docker containers using different IP4/IP6 defaults.
|
||||
To ensure all your docker images use the same IPv you could try disabling IP6 on all by adding:
|
||||
```
|
||||
|
|
|
|||
Loading…
Reference in a new issue