Error loading indexers, request to Jackett server failed, is server running ?

[Waterboy1602]

Environment

OS: FreeBSD: Iocage Jail

.Net Runtime: Mono

.Net Version: Mono V6.8.0.105

Jackett Version: V0.16.613.0

Last Working Jackett Version: No idea anymore

Are you using a proxy or VPN? Yes, VPN to access my network from distance to connect to Jackett service. That's when I get this error.

Description

When accessing Jackett in the browser I get this error: Error loading indexers, request to Jackett server failed, is server running ?. The indexers wont load and I also can't add new ones.

Logged Error Messages

There is nothing logged when I access the Jackett page.
I can only something in my browser console that says Failed to load resource: net::ERR_INVALID_CHUNKED_ENCODING.

Screenshots

[ngosang]

I can't reproduce.
Make sure Jackett server is running (restart Jackett service)

[Waterboy1602]

I've found that I only get this error when I connect to my VPN from outside my internal network. When I connect to my subnetwork with a VPN I don't get this error.

It could possible have something to do with my VPN, but that would be weird because I use exactly the same VPN.

[ngosang]

This is not a Jackett issue, it's network related.

If you are running Jackett in LAN network (eg, at home) and you want to reach Jackett from Internet or from a VPN service you have to do one of these things:

1. Open the Jackett port and use the public IP to connect to Jackett
2. Configure a reverse proxy. https://github.com/Jackett/Jackett#running-jackett-behind-a-reverse-proxy

[PrimalNaCl]

I'm seeing this exact same issue and I'm:
0) NOT running any sort of VPN.

1. ON a computer on my LOCAL network.
2. connecting to the a jail running jackett on the same class C.

From w/in the jail:
root@jackett:~ # ps wwaxl
UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND
0 23207 1 0 52 0 6536 2376 select IsJ - 0:00.00 dhclient: epair0b [priv] (dhclient)
65 23266 1 0 33 0 6536 2496 select ICsJ - 0:00.00 dhclient: epair0b (dhclient)
0 23332 1 0 20 0 6424 2500 select SsJ - 0:00.00 /usr/sbin/syslogd -c -ss
354 23387 1 0 24 0 6376 2048 piperd IsJ - 0:00.00 daemon: /usr/local/bin/mono[23388] (daemon)
354 23388 23387 0 20 0 216864 161212 uwait IJ - 0:07.28 /usr/local/bin/mono /usr/local/share/jackett/JackettConsole.exe -d /usr/local/jackett (mono-sgen)
0 23395 1 0 20 0 6456 2368 nanslp IsJ - 0:00.00 /usr/sbin/cron -J 15 -s
0 23635 23564 0 52 0 6940 2876 wait SJ 1 0:00.01 login [pam] (login)
0 23636 23635 0 31 0 7468 3816 pause SJ 1 0:00.01 -csh (csh)
0 23639 23636 0 31 0 6984 2836 - R+J 1 0:00.00 ps wwaxl
root@jackett:~ #
root@jackett:~ # netstat -an4
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp46 0 0 *.9117 . LISTEN

So, unless there's a split between web UI and 'service' (similar to deluge) it would appear the 'service' is up and this is an issue with the widget; jackett.

Please advise.
Thanks!

[stillka]

Solution for me was fixing rights of jacket directories:
chown -R jackett:jackett /usr/local/jackett
chown -R jackett:jackett /usr/local/share/jackett

2021-04-11 08:12:30 | Info | Jackett startup finished in 18.860 s
-- | -- | --
2021-04-11 08:12:28 | Info | Adding aggregate indexer ('all' indexer) ...
2021-04-11 08:12:28 | Info | Loaded 545 indexers in total
2021-04-11 08:12:28 | Info | Loaded 449 Cardigann indexers: 
2021-04-11 08:12:17 | Info | Loading Cardigann indexers from: /usr/local/jackett/cardigann/definitions/, /etc/xdg/cardigan/definitions/, /usr/local/share/jackett/Definitions
2021-04-11 08:12:17 | Info | Loaded 96 Native indexers: 
2021-04-11 08:12:16 | Info | Loading Native indexers ...
2021-04-11 08:12:16 | Info | Using HTTP Client: HttpWebClient
2021-04-11 08:12:16 | Info | Mono version: 6.8.0.105 (6.8.0.105 Mon Mar  9 21:00:56 UTC 2020)
2021-04-11 08:12:16 | Info | Using FlareSolverr: No
2021-04-11 08:12:16 | Info | Using proxy: Disabled
2021-04-11 08:12:16 | Info | App config/log directory: /usr/local/jackett
2021-04-11 08:12:16 | Info | ThreadPool MaxThreads: 400 workerThreads, 200 completionPortThreads
2021-04-11 08:12:16 | Info | Running in Docker: No
2021-04-11 08:12:16 | Info | Jackett variant: Mono
2021-04-11 08:12:16 | Info | OS version: Unix 12.2.3.0 (64bit OS) (64bit process)
2021-04-11 08:12:16 | Info | Environment version: 4.0.30319.42000 (/usr/local/lib/mono/4.5)
2021-04-11 08:12:13 | Info | Jackett Data will be stored in: /usr/local/jackett
2021-04-11 08:12:13 | Info | Starting Jackett v0.17.866

[Zamana]

I'm facing this exactly same problem right now, on version 0.18.786.

Jackett runs in a jail, accessible only from inside my LAN, but I have Nginx as reverse proxy translating 192.168.0.105:9117 to jackett.local (I have my own private local DNS that does the resolution).

And I guess that my reverse proxy configuration is right:

        listen       80;
        server_name  jackett.local;

        location / {
                proxy_pass http://192.168.0.105:9117;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Forwarded-Host $http_host;
                proxy_redirect off;
      }

Is there anything else that needs to be done to fix this "request to Jackett server failed" ?

[garfield69]

I don't know much about proxy setup but the wiki on Jackett has this: https://github.com/Jackett/Jackett/wiki/Reverse-Proxy
maybe its relevant for your issue?

[Zamana]

Hi!

Yes. This reverse proxy setup was copied from this link.

That's why I guess that it is right.

[garfield69]

@ilike2burnthing have any experience with nginx and jackett proxy setup?

[garfield69]

@Zamana but your version is missing some of the keywords

    proxy_http_version 1.1;
    proxy_set_header   Upgrade $http_upgrade;
    proxy_set_header   Connection keep-alive;
    proxy_cache_bypass $http_upgrade;

and yours has

                proxy_redirect off;

which isn't in the example.
is not any of these differences important?

[garfield69]

and the base too

location /jackett/ {

not relevant ?

[Zamana]

You're right guys. My configuration was messed up. I'm sorry.

Anyway the issue continues...

This message appears when I try the "manual search". Is it related?

[garfield69]

locate your jackett ServerConfig.json file.
what does your BasePathOverride set to?

[Zamana]

It is blank: ""

[garfield69]

ok. well that exhausts my contribution, let hope some other team members are available to try help.

[ilike2burnthing]

Similar issue? #11983

[Zamana]

I don't think so. In that case he is trying to access Jackett from outside his LAN and with httpS: that's not my case.

Anyway, I can access Jackett normally. The problem occurs when I try to do a "Manual Search" for some torrent that I know exactly what it is and I know that it exists in one of the torrent sites added to my list.

[ilike2burnthing]

I was meaning more the solution to it, the location and base path override needing to be set to /jackett/ for the reverse proxy to work.

[garfield69]

actually, to be clear, I think the base is set without the last slash according to the wiki. or do we need to update the wiki?

[garfield69]

I mean in the serverconfig. the nginx def needs both, if the wiki is correct.

[ilike2burnthing]

Yes, sorry, that was me being lazy/tired.

location - /jackett/
base - /jackett

iirc if you try to enter a trailing slash for the base it gets trimmed anyway

[Zamana]

Thank you guys, but the question regarding slash or no slash is this:

Most people configure their reverse proxy to use myhost.mydomain/jackett (and myhost.mydomain/radarr etc).

In my case, all my apps are configured with their own URLs, so that I can use jackett.mydomain, radarr.mydomain etc.

That's why my location is "/", and not "/jackett" or "/jackett/". These last ones doesn't apply to my case.

[ilike2burnthing]

Ah. I use the subdirectory, rather than subdomain, with nginx, so I'm not sure how you'd go about resolving that (if that's actually the issue).

Could you try jackett.local/jackett with the above location and base path to see if that works?

[zebrapurring]

In my case, the issue was caused by Nginx reverse proxy buffers being too small. With the browser developer tools you can see the request to /api/v2.0/indexers fails with error net::ERR_INCOMPLETE_CHUNKED_ENCODING. Copying this request to run it with curl, I noticed the endpoint was working fine, and it returned about 1 MB of JSON data.

So I updated the Nginx proxy buffer size to 10 MB with proxy_buffers and proxy_buffer_size. Below you can find my complete Nginx configuration:

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name jackett.my.domain;

    include ssl.conf;
    # ssl certs
    ssl_certificate     /usr/local/etc/ssl/jackett.crt;
    ssl_certificate_key /usr/local/etc/ssl/jackett.key;

    client_max_body_size 0;
    proxy_redirect off;
    proxy_buffering off;

    location / {
        # Configure reverse proxy
        proxy_pass http://jackett.internal.my.domain:9117/;
        proxy_http_version 1.1;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto $scheme;
        proxy_set_header   X-Forwarded-Host $http_host;

        # Enable websockets
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
        proxy_cache_bypass $http_upgrade;

        # Increase buffer size to 10MB
        proxy_buffers 8 10240k;
        proxy_buffer_size 10240k;
    }
}