Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jackett plugin gives connection error, even though properly configured #273

Open
COOLak opened this issue Mar 17, 2024 · 7 comments
Open

Comments

@COOLak
Copy link

COOLak commented Mar 17, 2024

Screenshot_1
Screenshot_2
Screenshot_3

As can be seen from the screenshots, everything is configured properly. I've added my API key to the file %localappdata%\qBittorrent\nova3\engines\jackett.json.

The IP and port of Jackett are also correct. Still "connection error". In web interface of Jacket itself, there are no isssues, and the search works.

Please advise?

@sourcelocation
Copy link

Same issue, have you found a solution?

@Piccirello
Copy link
Member

Are you using a proxy? If so, you may need to disable "Use proxy for general purposes" in qBittorrent options.

@COOLak
Copy link
Author

COOLak commented Mar 24, 2024

Are you using a proxy? If so, you may need to disable "Use proxy for general purposes" in qBittorrent options.

No, I'm not using a proxy. And I still haven't found a solution.

@makoto-kokoroki
Copy link

also having this problem since a few months ago;

@jiznon
Copy link

jiznon commented May 15, 2024

Also having this issue, but looking through the logs shows:

  Jackett.Common.IndexerException: Exception (torlock): Request to https://www.torlock2.com/all/torrents/finding-pictures-documentary.html?sort=added&order=desc failed (Error 522) - The tracker seems to be down.

Trying to visit that tracker's site in browser does indeed show it's down. So looks to be expected behavior. Only noteworthy thing is the Test on this passes. So that's peculiar.

My advice is to confirm that these sites are indeed down, and remove them if they aren't expected back up.

@makoto-kokoroki
Copy link

makoto-kokoroki commented May 15, 2024 via email

@jiznon
Copy link

jiznon commented May 15, 2024

Hey, we got two solutions to very similar problems. Thanks for reporting back

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants