From 42f9f193bb7ff09ea55f0a55dcff8b39c0be9682 Mon Sep 17 00:00:00 2001 From: garfield69 Date: Tue, 30 Jul 2024 15:29:22 +1200 Subject: [PATCH] Updated Troubleshooting (markdown) --- Troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 703942e..ce6c585 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -109,6 +109,8 @@ See [[How to provide a Jackett Enhanced log for a ticket|https://github.com/Jack This type of error is almost always a problem outside of Jackett's control. Usually caused by one of the following: +- One of the following may be blocking access: Firewall, anti-malware, Ad-blocker, Accountability app. + - Review your security app and add the required rule to allow Jackett access to the WAN, and/or the port and/or the site's address, whichever is relevant. - 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does). - Try using any of the **Alternate Site Links** in the indexer config and see if they work for you. @@ -117,8 +119,6 @@ Usually caused by one of the following: - Use a VPN service or a proxy server. - or try https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation - or DNS over TLS https://fedoramagazine.org/use-dns-over-tls/. -- One of the following: Firewall, anti-malware, Ad-blocker, Accountability app. - - Review your security app and add the required rule to allow Jackett access to the WAN, and/or the port and/or the site's address, whichever is relevant. - The site is broken, their server is terminating the connection due to some internal error. - 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. Just be aware that if your browser has an inbuilt VPN like Opera for instance, then Jackett will not be seeing the same WAN paths that your browser does). - Edit the indexer config and see if there is any alternate SiteLinks you can try instead.