mirror of
https://github.com/Jackett/Jackett
synced 2025-01-03 05:36:44 +00:00
Updated Troubleshooting (markdown)
parent
281d90147a
commit
e4957b1280
1 changed files with 18 additions and 7 deletions
|
@ -299,14 +299,25 @@ If that does not get it working, then
|
|||
- if you are out of date then upgrade
|
||||
|
||||
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. 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.
|
||||
- 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
|
||||
- Use a VPN service or a proxy server.
|
||||
- try https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation
|
||||
- or DNS over TLS https://fedoramagazine.org/use-dns-over-tls/.
|
||||
- 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 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 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 by shutting down your docker image and starting it up afresh).
|
||||
- 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 filter.
|
||||
- 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 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 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 by shutting down your docker image and starting it up afresh.
|
||||
- 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 filter.
|
||||
- One final possibility is that the web site has changed their login page. See below for what to do next.
|
||||
|
||||
If you still have this issue afterwards, then the next thing to do is to provide an **enhanced** log so that the Jackett team can investigate.
|
||||
|
|
Loading…
Reference in a new issue