Issues with Custom location tautulli

[Shifter2600]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?YES
• Are you sure you're not using someone else's docker image?YES
• If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?YES I can access my https://domain.com

Describe the bug Setup Custom Location with added config options required by tautulli. https://github.com/Tautulli/Tautulli-Wiki/wiki/Frequently-Asked-Questions there is a bit on NGINX NPM v2.0.13

To Reproduce Steps to reproduce the behavior: This is what is entered into my 1.conf location /tautulli { proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_pass http://192.168.210.5:8181/; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; }

Expected behavior when I navigate to https://domain.com/tautulli it should route to my application.

Screenshots see above in to reproduce

Operating System

• Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. Not relevant since container is working on other domains

Additional context Add any other context about the problem here, docker version, browser version if applicable to the problem. Too much info is better than too little. Nothing to add

[npike]

Did you ever find a solution for this?

[Shifter2600]

Did you ever find a solution for this?

No still no solution.

[shanelord01]

Pulling this zombie out of the grave - I have this issue. Cannot get it to work behind NPM. I'm not even using custom locations (i have "tautulli.mydomain.com" setup).

Be great if someone on the NPM team could setup Tautulli behind NPM (HTTPS on WAN, HTTP from NPM to Tautulli) and report back how to get it to work. Currently I get a timeout.

Thanks, Shane.

[shanelord01]

@npike & @Shifter2600

So after checking the Network tab in Chrome browser Developer tools, I found that as NPM loads Tautulli, it redirects to the login page. When it did this, it stripped the port from the redirect URL. Not sure if this would work for you.

Example: https://tautulli.mydomain.com:45505

303 redirects to

https://tautulli.mydomain.com/auth/login?redirect_uri=/

By adding an advanced config line in the proxy settings for this site in NPM: proxy_redirect https://tautulli.mydomain.com/ https://tautulli.mydomain.com:45505/;

The page now loads fine. Redirect loads showing this in Network tab of Chrome Dev Tools: https://tautulli.mydomain.com:45505/auth/login?redirect_uri=/

Not sure how this impacts things (beyond working) overall - but hoping someone can check why this works and whether my solution is the best one or not.

Thanks, Shane.

[RobertusIT]

proxy_redirect https://tautulli.mydomain.com/ https://tautulli.mydomain.com:45505/;

i have tried without success...

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1: