From 7dea7e7ad22dee6672c7adb94653d4ec504503af Mon Sep 17 00:00:00 2001 From: garfield69 Date: Sun, 25 Feb 2024 06:05:32 +1300 Subject: [PATCH] Updated Troubleshooting (markdown) --- Troubleshooting.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index c489628..1bede32 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -193,7 +193,8 @@ 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. Use a VPN service where you can specify a server using an IP that will pass the Web site's IP filter. +- 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. - 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. 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.