You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version: qBittorrent v4.3.9, all plugins up to date, Jackett plugin v3.5, server v0.20.188.
["Bug report"] It seems pretty logical that using a proxy would make localhost and 127.0.0.1 lookups give different results than normally, which is probably why I couldn't get Jackett to work for well over an hour, until I realized I was using SOCKS5 proxy via Nordvpn.
When I disabled proxy settings, Jackett started working flawlessly.
I can't say for sure if this problem happens with other proxies other than SOCKS5, because that's all I can test personally.
[Feature request] It'd really be nice if localhost and 127.0.0.1 adresses were somehow excluded from the proxy connection. There seems to be options in qBittorrent to limit what the proxy is used for, but none of these affect search plugins; they must all the forced to use the proxy as long as its set up, which sucks in the specific case of Jackett.
The text was updated successfully, but these errors were encountered:
Version: qBittorrent v4.3.9, all plugins up to date, Jackett plugin v3.5, server v0.20.188.
["Bug report"] It seems pretty logical that using a proxy would make localhost and 127.0.0.1 lookups give different results than normally, which is probably why I couldn't get Jackett to work for well over an hour, until I realized I was using SOCKS5 proxy via Nordvpn.
When I disabled proxy settings, Jackett started working flawlessly.
I can't say for sure if this problem happens with other proxies other than SOCKS5, because that's all I can test personally.
[Feature request] It'd really be nice if localhost and 127.0.0.1 adresses were somehow excluded from the proxy connection. There seems to be options in qBittorrent to limit what the proxy is used for, but none of these affect search plugins; they must all the forced to use the proxy as long as its set up, which sucks in the specific case of Jackett.
The text was updated successfully, but these errors were encountered: