mirror of https://github.com/Jackett/Jackett
Updated Troubleshooting (markdown)
garfield69
parent
44ca5b273c
commit
9579f3cc97
|
|
@ -55,9 +55,15 @@ See [[How to provide a Jackett Enhanced log for a ticket|https://github.com/Jack
|
|||
[[Click here|https://github.com/Jackett/Jackett/wiki/Troubleshooting#a-connection-attempt-failed]]
|
||||
## A connection attempt failed.
|
||||
|
||||
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.
|
||||
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 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:
|
||||
```
|
||||
|
|
@ -69,14 +75,8 @@ 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 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 it 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 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 service where you can specify a server using an IP that will pass the Web site's 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]]
|
||||
|
|
@ -122,7 +122,7 @@ If you have FlareSolverr installed and are receiving this message, check that th
|
|||
|
||||
To test (on native) access the FlareSolverr API URL in a browser, and you should see something similar to:
|
||||
```JSON
|
||||
{"msg":"FlareSolverr is ready!","version":"v2.2.1","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:98.0) Gecko/20100101 Firefox/98.0"}
|
||||
{"msg": "FlareSolverr is ready!", "version": "3.3.6", "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"}
|
||||
```
|
||||
|
||||
For those using internal Docker container IPs (e.g. http://172.17.0.2:8191) or the container name (e.g. http://flaresolverr:8191) you can **curl** this address using the Jackett container's console.
|
||||
|
|
@ -158,7 +158,7 @@ This error occurs because in most cases FlareSolverr cannot solve these kinds of
|
|||
This is caused by the Web Site changing their address, due to any number or reasons, such as:
|
||||
- they have let their domain registration expire
|
||||
- they got suspended by their domain registrar and have moved to another
|
||||
- they are trying to circumvent an DNS block
|
||||
- they are trying to circumvent a DNS block
|
||||
- they are trying to avoid a DDoS attack
|
||||
- they have upgraded to a new server at another location
|
||||
- your guess is as good as mine
|
||||
|
|
@ -216,8 +216,7 @@ For all other cases, access the Web Site with your browser and check that:
|
|||
- That your credentials are correct (prove it by logging into your account at the site)
|
||||
- That you have a good ratio (some site prevent you accessing the torrents search page, or just disable the download links)
|
||||
- That there are no outstanding alerts, notices or unread PM (some site prevent access to the torrent search page until you have cleared these events)
|
||||
- If you have changed your password recently, make sure to logout of the Site. (Some sites do not save the password until
|
||||
you logout).
|
||||
- If you have changed your password recently, make sure to logout of the Site. (Some sites do not save the password until you logout).
|
||||
|
||||
If you cannot find issues with your account at the Web site, then
|
||||
- Access your Jackett dashboard, use the trashbin icon to remove your indexer config, add a fresh one from the add-indexer page, and re-enter any credentials (even if they appear pre-filled) and click OKAY.
|
||||
|
|
@ -233,8 +232,8 @@ If none of the above has helped, then its time to look at some of these possible
|
|||
- 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).
|
||||
- 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 service where you can specify a server using an IP that will pass the Web site's 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 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.
|
||||
|
|
@ -256,6 +255,7 @@ See [[How to Provide HTML source|https://github.com/Jackett/Jackett/wiki/Trouble
|
|||
Some Web Sites use a login page that includes a Captcha challenge, or other prove-you-are-human check.
|
||||
On a regular basis, determined by the Site (may be daily, weekly, monthly, whatever) the Site will expire the session cookie that Jackett saved when you used that Indexer's config Login credentials to login.
|
||||
So now you have to edit that Indexer's config again and fill in the new Capcha challenge to login anew.
|
||||
Note that if the captcha image is not present in the config, then this may indicate that the login page was not retrieved by Jackett successfully, due to some network error. Use your browser to check that you can access the login page for the site.
|
||||
|
||||
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.
|
||||
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]]
|
||||
|
|
@ -280,7 +280,7 @@ This is a genuine error at the Web site. They are having issues with their serve
|
|||
There is nothing that Jackett can do about it.
|
||||
You can:
|
||||
- Try again later.
|
||||
- Use your Jackett dashboard to edit that indexer's config, and see if the indexer supports any alternate SiteLinks. Some links are proxy/mirror sites, and assuming that they too are working and are not blocked by your ISP they may work for you.
|
||||
- Use your Jackett dashboard to edit that indexer's config, and see if the indexer supports any alternate SiteLinks. Some links are proxy/mirror sites, and assuming that they too are working and are not being blocked by your ISP, they may work for you.
|
||||
|
||||
[[Return to Index|https://github.com/Jackett/Jackett/wiki/TroubleShooting/#index]]
|
||||
***
|
||||
|
|
@ -304,6 +304,9 @@ Ensure FlareSolverr and Jackett are on the same device, as the cookies may rely
|
|||
|
||||
If both services are on the same network and proxy is disabled, then another possibility is for (semi-)Private web site which have a new login page. This in combination with a Cloudflare check might return a cookie error. Use your browser to look at the login page and if it appears different than before then report this in the ticket so the team can check it out.
|
||||
|
||||
Another possibility is that the site is offline, such as when a domain has expired and the site's service provider presents a domain-for-sale page.
|
||||
Use your browser to check that the site is still online.
|
||||
|
||||
If none of the above applies, then please open a new issue in FlareSolverr [here](https://github.com/FlareSolverr/FlareSolverr/issues/new/choose). Include the affected web site the indexer was using.
|
||||
|
||||
[[Return to Index|https://github.com/Jackett/Jackett/wiki/TroubleShooting/#index]]
|
||||
|
|
@ -376,7 +379,7 @@ Try following these instructions (using a Chrome Browser) for getting the cookie
|
|||
Notes:
|
||||
- Be sure to use the Browser from the same machine that is running Jackett, as cookies will rarely work from other platforms.
|
||||
- On the login page for the Web site do not tick any options that restrict your session to one IP address, or logout after a short time. If there is a Remember me option, use it.
|
||||
- Make sure that before fetching the cookie you can access the Site's torrent search page, as anything the site does to prevent this (alerts, unread notices or unread PM, or a low ratio warning) will stop Jackett from having a successful test after using the cookie.
|
||||
- Make sure that before fetching the cookie you can access the Site's torrent search page, as anything the site does to prevent this (alerts, unread notices or unread PM, or a low ratio warning) will stop Jackett from having a successful test when using the cookie.
|
||||
- if you are using a Docker container, some users appear to have success using the cookie from a Firefox browser !?!
|
||||
- Another Docker user had success by setting up chrome as a service container, see https://hub.docker.com/r/browserless/chrome
|
||||
or a firefox container,see https://registry.hub.docker.com/r/linuxserver/firefox/
|
||||
|
|
|
|||
Loading…
Reference in New Issue