mirror of
https://github.com/Jackett/Jackett
synced 2025-01-03 05:36:44 +00:00
Updated Troubleshooting (markdown)
parent
7dea7e7ad2
commit
0f408286c3
1 changed files with 3 additions and 3 deletions
|
@ -91,7 +91,7 @@ to the Docker run command (depending on which you're using), see if that makes a
|
|||
- 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.
|
||||
- Some site such a Zamunda and Zelka for example, occasionally 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]]
|
||||
|
@ -193,7 +193,7 @@ to the Docker run command (depending on which you're using), see if that makes a
|
|||
- 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.
|
||||
- The web site is filtering out non-local IP addresses. Some site such a Zamunda and Zelka for example, occasionally 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.
|
||||
- It may be that the site has altered their torrent search page results HTML and the indexer cannot find the info its looking for. In which case see below.
|
||||
|
||||
|
@ -317,7 +317,7 @@ If none of the above has helped, then its time to look at some of these possible
|
|||
- 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.
|
||||
- The web site is filtering out non-local IP addresses. Some site such a Zamunda and Zelka for example, occasionally 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.
|
||||
|
||||
|
|
Loading…
Reference in a new issue