mirror of https://github.com/Jackett/Jackett
Updated Troubleshooting (markdown)
ilike2burnthing
parent
b09886643f
commit
13d9f9c968
|
|
@ -64,7 +64,7 @@ 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 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).
|
||||
- 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.
|
||||
|
||||
|
|
@ -109,14 +109,14 @@ Until Cloudflare lift the blacklist, you could try one or more of the following:
|
|||
- If your indexer config uses the cookie method for access to the Web site, then refresh your cookie (edit the config from your dashboard, and if it requires a cookie then follow the instructions in the config to fetch your new cookie)
|
||||
- Use one of the alternate domains (edit the config from your dashboard, any alternate domain links are listed there, click one to load it into the sitelink box)
|
||||
- Find a mirror site or proxy site (note this only works for true mirrors or faithful proxies, so do not be surprised if the indexer cannot use them as the HTML that these sites may be using may not be identical to the original)
|
||||
- Use a proxy/vpn to get a different IP address that is not blacklisted (if you cannot find any servers on your current proxy/VPN that work then consider trying a different proxy/VPN, but note that some Web site have this protection enabled for all IP addresses, MejorTorrent is one such site)
|
||||
- Use a proxy/VPN to get a different IP address that is not blacklisted (if you cannot find any servers on your current proxy/VPN that work then consider trying a different proxy/VPN, but note that some Web site have this protection enabled for all IP addresses, MejorTorrent is one such site)
|
||||
- Wait for the blacklist to be revoked (blacklists do not normally last for ever, usually they are lifted within a fortnight or a month at most, however some site do have this protection enabled permanently for all IP addresses)
|
||||
- Use your browser to access the site instead of Jackett
|
||||
2. If you are **not** on the latest version of Jackett then **upgrade** to see if additional alternate domains are available.
|
||||
|
||||
If none of the above helps you bypass the issue, then we are sorry, but there is nothing more the Jackett team can do for you.
|
||||
|
||||
It is currently not possible to solve the new cloudflare challenge with the existing automation library in Jackett.
|
||||
It is currently not possible to solve the new Cloudflare challenge with the existing automation library in Jackett.
|
||||
An experimental solution is being trailed with [#9029](https://github.com/Jackett/Jackett/issues/9029) (involving a headless browser proxy server) for users with the knowledge and skills to implement it, and not available for all platforms and unlikely to be published in its current form.
|
||||
For the rest of us, you will just have to do without the Jackett indexer for this web site until they drop that DDoS protection.
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ To test (on native) access the FlareSolverr API URL in a browser, and you should
|
|||
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.
|
||||
Note that when using Docker, _127.0.0.1_ and _localhost_ will not work for the FlareSolverr API URL in Jackett.
|
||||
|
||||
Also, FlareSolverr is not a cure-all for all of Cloudflare's challenges. There is currently no solution for the HCaptcha challenge.
|
||||
Also, FlareSolverr is not a cure-all for all of Cloudflare's challenges. There is currently no solution for the hCaptcha challenge.
|
||||
|
||||
[[Return to Index|https://github.com/Jackett/Jackett/wiki/TroubleShooting/#index]]
|
||||
***
|
||||
|
|
@ -168,14 +168,7 @@ If however, more than one indexer is reporting this error, then the next most li
|
|||
|
||||
A Jackett indexer attempted to access a web site that is protected by an image captcha challenge.
|
||||
|
||||
This error occurs because in most cases FlareSolverr cannot solve these kinds of challenges.
|
||||
Review the FlareSolverr documentation to configure a captcha resolution service. Please do not report this issue on Jackett.
|
||||
|
||||
Install and configure a [Captcha Solver](https://github.com/FlareSolverr/FlareSolverr#captcha-solvers), or wait for the site to drop their captcha challenge.
|
||||
|
||||
If you are using hcaptcha-solver, this may not currently work, see issue [#31](https://github.com/FlareSolverr/FlareSolverr/issues/31)
|
||||
|
||||
Support for other captcha solvers will be added in future, see issue [#24](https://github.com/FlareSolverr/FlareSolverr/issues/24)
|
||||
This error occurs because in most cases FlareSolverr cannot solve these kinds of challenges. Currently [Captcha Solvers](https://github.com/FlareSolverr/FlareSolverr#captcha-solvers) do not work. For updates, follow issues [#31](https://github.com/FlareSolverr/FlareSolverr/issues/31) and [#24](https://github.com/FlareSolverr/FlareSolverr/issues/24)
|
||||
|
||||
[[Return to Index|https://github.com/Jackett/Jackett/wiki/TroubleShooting/#index]]
|
||||
***
|
||||
|
|
@ -245,7 +238,7 @@ For all other cases, access the Web Site with your browser and check that:
|
|||
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 reenter any credentials (even if they appear pre-filled) and click OKAY.
|
||||
- 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.
|
||||
|
||||
If that does not get it working, then
|
||||
- access your Jackett Dashboard, scroll to the bottom for the Jackett version and compare it to the version [here](https://github.com/Jackett/Jackett/releases/latest)
|
||||
|
|
@ -379,7 +372,7 @@ Try following these instructions (using a Chrome Browser) for getting the cookie
|
|||
1. Login to the Web Site with your browser using the **Site Link** address you have chosen to use from the Jackett indexer config
|
||||
2. Open the **DevTools** panel by pressing **F12**
|
||||
3. Select the **Network** tab
|
||||
4. Click on the **Doc** button (Chrome Browser) or **HTML** button (FireFox Browser)
|
||||
4. Click on the **Doc** button (Chrome Browser) or **HTML** button (Firefox Browser)
|
||||
5. Refresh the page by pressing **F5**
|
||||
6. Click on the first row entry
|
||||
7. Select the **Headers** tab on the right panel
|
||||
|
|
@ -393,7 +386,7 @@ 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.
|
||||
- if you are using a Docker container, some users appear to have success using the cookie from a firefox browser !?!
|
||||
- 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
|
||||
- If you are running Jackett on a headless server (such as a SeedBox) then if you have SSH access to the SeedBox you can try to configure a SSH tunnel.
|
||||
**This is tricky to configure** but in simple words, it will open a port in the SeedBox and you can use that port as a proxy server. Take a look at [this (English)](https://www.systutorials.com/proxy-using-ssh-tunnel/) or [this (Spanish)](https://www.redeszone.net/tutoriales/servidores/ssh-tunneling/)
|
||||
|
|
|
|||
Loading…
Reference in New Issue