-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
no indexers seem to work when proxies are enabled in versions > 0.11 #4862
Comments
I'm seeing this as well, all of my indexers are failing all of a sudden. Using latest Docker release. |
Turns out PIA's SOCKS5 proxy seems to be refusing connections |
Anybody got a fix? |
I don't think this has to do with proxies because I don't use a proxy. |
the jackett rarbg indexer uses the rarbg api at https://torrentapi.org/pubapi_v2.php which on my win10 was returning ERR_CONNECTION_REFUSED I dont know what the equivalent is on linux or even if it applies to docker images... @FlightLevel or @kaso17 can you assist please? thanks. |
I'm seeing the same issue on Jackett 0.11.8.0 (Docker on Synology) with ALL indexers... The error for RARBG is as follows but all indexers show the same type of error... Jackett.Common.IndexerException: Exception (rarbg): Connection refused ---> System.Net.Http.HttpRequestException: Connection refused ---> System.Net.Sockets.SocketException: Connection refused The error seems to be when using a proxy (I'm using a socks5 proxy)... If I disable the proxy settings temporarily, the indexers all test successfully... |
Problem for me was solved by restarting Docker Host, removing container and recreate with new image. Dropped indexer in Jackett and recreated, now working fine. |
@Ton-O, me too! Thank you! |
This is happening to me too on Docker/Synology. Sometimes 1 tracker works but the rest fail, sometimes they all fail instantly. I have tried deleting the container and recreating, stopping docker completely and restarting, upgraded the docker spk and none of these have fixed the issue. Running on 0.11.46.0. I'm also using PIA SOCKS5. Removing the SOCKS5 url fixed the issue but this is not an acceptable fix. |
I am having issues with both Nord and PIA proxies. Tried multiple servers/countries for each. Without fail, 1 test would work after changing servers, then any subsequent tests immediately get connection refused. Sadly disabling proxy until this is resolved. |
For your info: I'm NOT using proxies on the jacket-connection (only on the transmission-connection later in the chain). |
Agree with @mRaRn that removing the proxy fixes the issue so our particular issue appears to be with the SOCKS5 Proxy... for the time being, I rolled my jackett image back to “linuxserver/jackett:amd64-v0.10.861-ls10” and it works with the socks5 proxy again... Keen to hear from the jackett devs on whether this will be fixed in a future release before I test future updates! |
Created a new container as @n1nj4888 said with “linuxserver/jackett:amd64-v0.10.861-ls10” and it worked correctly. |
I have the same problem with socks5 proxy, so there is definitely a bug. |
Not sure which release introducted this proxy bug but it must have been one between v0.10.861 and v0.11.8. Hopefully the devs can take a look and fix this issue since I won’t be able to upgrade to the latest jackett until this is fixed as don’t want to remove my proxies. |
Same issue here. Using Sock5 and Connection Refused on all indexers. |
Hi @sv01a - Are you able to take a look at this issue given I recall you developed the initial proxy support in Jackett? |
Can someone with SOCKS issue please try v0.11.1 and see if that works? Confirming its impacting every indexer and not just some? |
Hi @FlightLevel. I spun up a new container "linuxserver/jackett:amd64-v0.11.1-ls13 and Jackett GUI shows v0.11.1. When hitting the "Test All" icon, all Indexers (5 configured), fail almost immediately... All with the same form of error: Jackett.Common.IndexerException: Exception (rarbg): Connection refused ---> System.Net.Http.HttpRequestException: Connection refused ---> System.Net.Sockets.SocketException: Connection refused |
@n1nj4888 I'll take a look. are you sure that your proxy are alive? |
Thanks guys! The proxy settings work on 0.10.861, just not on 0.11.1 or above... |
Shew, I can confirm the socks5 proxy is up and working without issue on all other applications... Jackett.Common.IndexerException: Exception (1337x): Connection refused ---> System.Net.Http.HttpRequestException: Connection refused ---> System.Net.Sockets.SocketException: Connection refused |
Hi @sv01a, did you manage to take a look and figure out the issue with the socks proxy? |
I just update to 0.11.115.0 today. I started having this problem. If I disable proxy, it works just fine. I hope the Jackett Team fixes this soon. I want proxy to work. |
@sv01a was going to look into this as they were involved in the initial implementation of the proxies on Jackett. Not sure if they managed to take a look? Also - I think we should rename this issue / create a new one that is clearer that the issue is that no indexers seem to work when proxies are enabled in versions > 0.11 |
Hi @sv01a - Any update on this please? Actually both this and #2602. @FlightLevel indicates that if no-one will support proxy in jackett it maybe removed. I’m sure there’s a number of us that would like to prevent that happening! |
@daddyboo on behalf of other docker users that want to use this, could you tell us how you passed the httpclient2 run time parm to start jackett with this method? thanks. |
@garfield69 I use Portainer (https://www.portainer.io) to work with my docker containers. I did a couple of experiments and find out that it works if I pass parameter without any spaces. Here is a screenshot https://imgur.com/GlEni4S |
@n1nj4888 so have you tried using |
On unRAID, I put this in 'extra parameters' which resolved the proxy issue: |
Ok so I’ve changed the docker RUN_OPTS environment variable to simply -chttpclient2 (no spaces) and Jackett now runs and indicates it is using the different HTTP client. Running a “Test all” on the indexers passes on every single indexer now. I also tried changing the configured proxy port to something I know to be wrong and it then failed all the index tests (as expected)... So it would appear that this fix fixes proxy settings in the newer versions of Jackett !!! I think there are two outstanding questions: (A) If httpclient2 works and the standard one doesn’t, wouldn’t it make sense to make httpclient2 the default client for any configured proxies (so that the user doesn’t need to pass additional env variables? (B) Passing the docker env “-chttpclient2” works so there is presumably a bug in the parsing of this so that is is passed to the jackett executable as “-c httpclient2” (with space) Thanks for all your help with this! |
Adding
to the docker run command fixes the issue on my setup. Thanks! |
Can someone using SOCKS please try using |
Hi @FlightLevel, Using SOCKS5 on v0.11.230.0, changed docker RUN_OPTS to “--UseClient=httpclient“. Jacket docker starts and I’m able to login to the Web GUI... However, running the “Test All” results in the same errors to the jackett log:
Also tried adding “TorrentHeaven” as a new indexer but it fails to add with the following notification error (to the GUI): “Request to Jackett server failed.” And the corresponding jackett log error:
|
@FlightLevel indexers with certificates: shokweb, trancetraffic, frozenlayer, takeabyte, ilcorsaroblu, nyaasi, ilcorsaronero, nnm-club. |
@FlightLevel oops, forgot c#. psytorrents, scenehd, elitetracker, torrentheaven. |
Adding
to the docker-compose worked for me |
Can someone using httpclient2 and SOCKS test ilcorsaronero and see if that works |
Can someone also try the latest release and use |
All indexer tests pass with ilcorsaronero passes on both httpclient2 and httpclient2netcore. |
@FlightLevel |
@keerio |
@garfield69 |
-e RUN_OPTS="-chttpclient2netcore" also works for me |
The latest pre-release has httpclient2netcore as the default client. If no regressions are found in the next few days, it will go to general release |
-chttpclient2netcore = good for me on 0.11.256.0 with Synology/Docker. |
Great work @FlightLevel, @garfield69 and all others involved for sorting this! |
Good to hear, you can all remove your RUN_OPTS now |
Hi @FlightLevel - Presumably the red Proxy warning text will be removed from the GUI in a future release if there are no further major issues reported with the proxy functionality? |
Dashboard message now updated |
Question: I'm getting this same error using a socks5 proxy when running as a Windows service. Is there a fix for that? For now I've switched to an HTTP proxy and that appears to be working fine. |
This fix has been detailed here: Jackett/Jackett#4862 (comment)
This fix has been shown in the following Jackett Issue: Jackett/Jackett#4862 (comment)
Please use the search bar at the top of the page and make sure you are not creating an already submitted issue. Duplicating issues makes it more difficult for everyone to follow. Your issue may have already been solved in the past as well.
RARBG fails the index test.
Jackett version: 0.11.8.0
Mono version (if not using Windows): Whatever comes in Docker
The text was updated successfully, but these errors were encountered: