I ran into some problems setting up a reverse proxy with Jackett, and tracked it down to an issue with the Base Path setting.
Essentially my reverse proxy is setup at domain.com/jackett and it redirects all requests internally to localhost:9117/jackett. I noticed that for some reason it wasn't loading resources properly (javascript/css/etc.), only the HTML itself.
The issue is, when a Base Path is set up, instead of acting identical to hitting / (without a base URL) and redirecting to /Admin/Dashboard, it will instead just try to load the dashboard page, which breaks all relative URL's.
You can see this also if you load Jackett locally with a base url of "/jackett" and go to http://localhost:9117/jackett
Since it does not properly redirect to /Admin/Dashboard the call to "get_jackett_config" breaks. I would say that with a Base Path, navigating to that base path should result in the same action as navigating to root normally would.
I experienced this too:
Using Nginx I was able to get a rewrite working with this config:
location /jackett/ {
rewrite /jackett/(.*) /$1 break;
proxy_bind $server_addr;
proxy_pass http://127.0.0.1:9117;
}
Everything loads and functions fine at example.com/jackett/
This should be working now, please reopen if not the case
Most helpful comment
I experienced this too:
However
Using Nginx I was able to get a rewrite working with this config:
Everything loads and functions fine at example.com/jackett/