Jackett: Jacket Service Loads, but 404 on web page.

[neuman1812]

Jackett version: 0.10.69
Mono version (if not using Windows):
mono --version Mono JIT compiler version 5.14.0.177 (tarball Mon Aug 6 10:53:50 UTC 2018) Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com TLS: __thread SIGSEGV: normal Notifications: epoll Architecture: armel,vfp+hard Disabled: none Misc: softdebug Interpreter: yes LLVM: yes(3.6.0svn-mono-/) GC: sgen (concurrent by default)

---

syslog-

Aug 18 11:32:06 media_pi mono[10311]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Internal.WebHost[1]
Aug 18 11:32:06 media_pi mono[10311]:       Request starting HTTP/1.0 GET http://192.168.1.102/
Aug 18 11:32:06 media_pi mono[10311]: 08-18 11:32:06 Info Request starting HTTP/1.0 GET http://192.168.1.102/
Aug 18 11:32:06 media_pi mono[10311]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
Aug 18 11:32:06 media_pi mono[10311]:       Request finished in 37.9289ms 301
Aug 18 11:32:06 media_pi mono[10311]: 08-18 11:32:06 Info Request finished in 37.9289ms 301
Aug 18 11:32:06 media_pi mono[10311]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Internal.WebHost[1]
Aug 18 11:32:06 media_pi mono[10311]:       Request starting HTTP/1.0 GET http://192.168.1.102//UI/Dashboard
Aug 18 11:32:06 media_pi mono[10311]: 08-18 11:32:06 Info Request starting HTTP/1.0 GET http://192.168.1.102//UI/Dashboard
Aug 18 11:32:06 media_pi mono[10311]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
Aug 18 11:32:06 media_pi mono[10311]:       Request finished in 7.6546ms 404
Aug 18 11:32:06 media_pi mono[10311]: 08-18 11:32:06 Info Request finished in 7.6546ms 404

sudo systemctl status jackett ● jackett.service - Jackett Daemon Loaded: loaded (/etc/systemd/system/jackett.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2018-08-18 11:30:53 EDT; 4min 14s ago Main PID: 10311 (mono) CGroup: /system.slice/jackett.service └─10311 /usr/bin/mono --debug /opt/jackett/JackettConsole.exe --NoRestart
As stated in the title, the jacket services is loading, but when attempting to load web page, gives 404. Connection to sonarr/radarr broken as they are getting the 404 response. This is after the update to 10.69. No other changes were made to the system, Raspberry Pi running stretch. With nginx reverse proxy

Nginx log when attempting to access.

[18/Aug/2018:11:36:59 -0400] "GET /jackett/UI/Dashboard HTTP/1.1" 404 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36"

Jackett Log -
2018-08-18 11:39:35.5989 Info Request starting HTTP/1.0 GET http://192.168.1.102//UI/Dashboard
2018-08-18 11:39:35.6120 Info Request finished in 12.5849ms 404

[Celoxocis]

i have the exact same issue and i just pulled the latest jackett version...

[guythnick]

Same behavior for me as well.

[D4rk56]

Same

[kaso17]

Are you running rerverse proxys?
If not make sure the basebath override is set to the empty string.
@neuman1812 you've two slashes in your URL? Try accessing http://192.168.1.102/UI/Dashboard please.

[Celoxocis]

yes I'm running a reverse proxy using nginx as a tls proxy.
(ssl cert done with Let's Encrypt)
my basepath override is set to "/jackett"
proxy type was always kept as "http".

and my nginx proxy setup looks like this:

location /jackett/ {
sendfile off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://intenal-ip-address:9117/;
}

it works without any issues with all previous versions all up to version 0.9.41.0. which i have pinned now but it breaks with any newer version.

i noticed when i try to access the gui. it try's to load
"https://FQDN/UI/Dashboard"
instead of
"https://FQDN/jackett/UI/Dashboard"

so what has changed in version 10.x? what is required in nginx to make it work?

[Celoxocis]

okay i think i figured it out for now. it works on the latest 10.x version.
i had to add "jackett/" to the proxy_pass url.

location /jackett/ {
sendfile off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://internal-ip-address:9117/jackett/;
}

[neuman1812]

@kaso17 the url I have bookmarked is "https://192.168.1.102/jackett/UI/Dashboard" The double URL only shows up in the Jackett log

Info Request starting HTTP/1.0 GET http://192.168.1.102/jackett//UI/Dashboard

Following @Celoxocis I modified my nginx config as follows

location /jackett/ {                     **#### < Added backslash after jackett**
    proxy_pass       http://127.0.0.1:9117/jackett/;   **##### > Added /jackett/**
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

Jacket Url now loads, ,sonarr and radarr connect. However an Error is generated in the syslog as follows.

Error Log(syslog) - https://hastebin.com/yofiwunene.coffeescript

Jackett log as follows:
2018-08-19 08:34:50.3467 Info Request starting HTTP/1.0 GET http://192.168.1.102/jackett/api/v2.0/server/config?_=1534682089957
2018-08-19 08:34:50.3467 Info Route matched with {action = "Config", controller = "ServerConfiguration"}. Executing action Jackett.Server.Controllers.ServerConfigurationController.Config (JackettConsole)
2018-08-19 08:34:50.3542 Info Authorization was successful.
2018-08-19 08:34:50.3542 Info Executing action method Jackett.Server.Controllers.ServerConfigurationController.Config (JackettConsole) - Validation state: Valid
2018-08-19 08:34:50.3542 Info Executed action method Jackett.Server.Controllers.ServerConfigurationController.Config (JackettConsole), returned result Microsoft.AspNetCore.Mvc.ObjectResult in 0.2703ms.
2018-08-19 08:34:50.3542 Info Executing ObjectResult, writing value of type 'Jackett.Common.Models.DTO.ServerConfig'.
2018-08-19 08:34:50.3542 Info Executed action Jackett.Server.Controllers.ServerConfigurationController.Config (JackettConsole) in 9.7486ms
2018-08-19 08:34:50.3750 Info Request finished in 28.3401ms 200 application/json; charset=utf-8
2018-08-19 08:34:50.4006 Info Request starting HTTP/1.0 GET http://192.168.1.102/jackett/favicon.ico
2018-08-19 08:34:50.4175 Info Sending file. Request path: '/favicon.ico'. Physical path: '/opt/jackett/Content/favicon.ico'
2018-08-19 08:34:50.4175 Info Request finished in 19.6177ms 200 image/x-icon
2018-08-19 08:34:50.4512 Info Request starting HTTP/1.0 GET http://192.168.1.102/jackett/api/v2.0/indexers?_=1534682089958
2018-08-19 08:34:50.4621 Info Route matched with {action = "Indexers", controller = "IndexerApi"}. Executing action Jackett.Server.Controllers.IndexerApiController.Indexers (JackettConsole)
2018-08-19 08:34:50.4656 Info Authorization was successful.
2018-08-19 08:34:50.4656 Info Executing action method Jackett.Server.Controllers.IndexerApiController.Indexers (JackettConsole) - Validation state: Valid
2018-08-19 08:34:50.4656 Info Executed action method Jackett.Server.Controllers.IndexerApiController.Indexers (JackettConsole), returned result Microsoft.AspNetCore.Mvc.ObjectResult in 0.0244ms.
2018-08-19 08:34:50.4656 Info Executing ObjectResult, writing value of type 'System.Linq.Enumerable+SelectIPartitionIterator`2[[Jackett.Common.Indexers.IIndexer, Jackett.Common, Version=0.10.69.0, Culture=neutral, PublicKeyToken=null],[Jackett.Common.Models.DTO.Indexer, Jackett.Common, Version=0.10.69.0, Culture=neutral, PublicKeyToken=null]]'.
2018-08-19 08:34:51.7084 Info Executed action Jackett.Server.Controllers.IndexerApiController.Indexers (JackettConsole) in 1244.4278ms
2018-08-19 08:34:51.7084 Info Request finished in 1260.5609ms 200 application/json; charset=utf-8

[kaso17]

Can someone running nginx confirm that this config is working?

location /jackett {
    proxy_pass http://127.0.0.1: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 $host;
    proxy_redirect off;
}

[thrnz]

I can confirm that the following recently stopped working in Apache with the same symptoms as above:

ProxyPass /jackett http://127.0.0.1:9117
ProxyPassReverse /jackett http://127.0.0.1:9117

It was causing a redirect to a non-existant http://hostname/UI/Login?ReturnUrl=%2FUI%2FDashboard despite having "BasePathOverride" set to '/jackett' in Jackett's ServerConfig.json.

It was fixed by adding /jackett to the forwarded address:

ProxyPass /jackett http://127.0.0.1:9117/jackett
ProxyPassReverse /jackett http://127.0.0.1:9117/jackett

[guythnick]

It was fixed by adding /jackett to the forwarded address:

ProxyPass /jackett http://127.0.0.1:9117/jackett
ProxyPassReverse /jackett http://127.0.0.1:9117/jackett

What file was this added to?

[thrnz]

What file was this added to?

Whichever Apache .conf file the reverse proxy is defined in. In may case 'conf/sites-available/mydomainname.conf' under the appropriate <VirtaulHost>.

I'm unsure when the reverse proxy first broke as I rarely use the WebUI, and Jackett itself is in a self-updating Docker container. Requests to Jackett from other Docker containers were still working as expected.

But I can confirm that the fix from @Celoxocis also works with an Apache reverse proxy.

[Celoxocis]

is it possible that for whatever reason the basepath override which we had set to to "/jackett" prior version 10.x. doesn't work properly as expected in version 10.x?

[Celoxocis]

@neuman1812 i was curious and checked my log output and i don't have the doubledash in my request. nor any errors.

here is my jackett log when requestion https://FQDN/jackett which redirects me properly to https://FQDN/jackett/UI/Dashboard

https://pastebin.com/nNZRyayK

@kaso17
i tested the suggested config and it works too for me.
I'm on 0.10.69.0

update: i did notice "Download Locally" seems to be broken on 0.10.69.0 when using a reverse proxy.
saving the same files to server blackhole directory work fine.
it used to work fine on for both on 0.9.x.

[D4rkSl4ve]

Here is how I fixed mine:

https://github.com/Jackett/Jackett/issues/3600#issuecomment-414418402

[Panderine]

I'm having the same issue, I use traefik as a docker reverse proxy. It won't detect jackett as a backend as well. I don't use URL override since I have a self subdomain for jackett.

[kaso17]

The readme has been updated with an updated nginx example which works fine for me (using basepath=/jackett):

please try it:

location /jackett {
    proxy_pass http://127.0.0.1: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;
}

@Panderine make sure you set the X-Forwarded-Proto and X-Forwarded-Host headers in traefik.

[D4rkSl4ve]

The above jackett.conf worked. Thanks!

On Wed, Aug 22, 2018 at 12:52 PM, kaso17 [e-mail] wrote:

The readme has been updated with an updated nginx example which works fine
for me (using basepath=/jackett):

please try it:

location /jackett {
proxy_pass http://127.0.0.1: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;
}

@Panderine https://github.com/Panderine make sure you set the
X-Forwarded-Proto and X-Forwarded-Host headers in traefik.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Jackett/Jackett/issues/3643#issuecomment-415101614,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ak3yDbI7oZsDNRUDODheVLK4YlpBz4fxks5uTYxigaJpZM4WCnUS
.

[Panderine]

@kaso17 I'm terrible sorry i'm very noob at this. I read the documentation o traefik and I believe the way to add those headers is by using the label "traefik.frontend.headers.SSLProxyHeaders=" on the jackett container. Problem is I don't know what to replace $scheme and $http_host with since I belive this variables won't work directly like that on traefik. Besides that, why is this needed now? I didn't have this headers forwarded before and traefik used to work. What changed?

[kaso17]

@Panderine
Adjusting the host (and the proto header in case TLS was used) header was necessary before too. But before it was used only for generating download links (due to that a wrong header wasn't that obvious).
With the new webserver they are more widely used causing more obvious problems.

Unfortunately I've no experience with traefik. Please run a tcpdump (tcpdump -Avvvni any port 9117 -s 9000) of the jackett traffic and post the output (after a failed request).

[Celoxocis]

@kaso17 does adjusting the host in nginx fix issues with "download locally" in jackett?
($host; =>$http_host;)

[kaso17]

@Celoxocis using $http_host is highly recommended and needed for the download links to be build correctly if your nginx is running on a non default HTTP (80)/HTTPS (443) port (The $host variable never contains the original port while $http_host does).

Also make sure there are no tailing slashes at the location path and the proxy_pass statements and proxy_redirect off; is set.

[ghost]

@neuman1812 is this still an issue for you?

[neuman1812]

@flightlevel

The modifications in my NGINX config that I stated earlier do allow it to work. If I remove those modifications it does not work.

So whatever changed in the .10.69 version broke my setup, I'm currently on 10.134 with the same issue. As long as I keep my nginx config modified it works.