[Resolved] 19/19.1 reverse proxy issue

Get help, report and discuss bugs.
Post Reply
lordjynx
Posts: 22
Joined: 23 Jan 2015, 17:46

[Resolved] 19/19.1 reverse proxy issue

Post by lordjynx » 18 Jul 2017, 17:32

Starting with 19.0/19.1 I've been noticing this minor issue:

I use nginx as my reverse proxy. The nginx requires a password to connect so I left the password requirement off on nzbget. Occasionally, when using the nzbget web-interface through nginx, I'll receive a 401 error in the nginx logs and the CSS won't load.

Here's the log from nginx:

[18/Jul/2017:12:05:46 -0500] "GET /nzbget/ HTTP/1.1" 401 590 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36" "-"

Backspacing off the last slash in /nzbget/ (IE: /nzbget) will allow the page to load fine.

nginx config file:

location /nzbget { proxy_pass http://x.x.x.x.:6789; }

Thanks,

LJ
Last edited by lordjynx on 19 Jul 2017, 14:18, edited 1 time in total.

hugbug
Developer & Admin
Posts: 6746
Joined: 09 Sep 2008, 11:58
Location: Germany (NRW)

Re: 19/19.1 reverse proxy issue

Post by hugbug » 18 Jul 2017, 17:51

Can't remember any changes in v19 regarding authorization.
What was the previous version, v18?

Any warnings or errors in nzbget log?

How is the authorization disabled in nzbget?

lordjynx
Posts: 22
Joined: 23 Jan 2015, 17:46

Re: 19/19.1 reverse proxy issue

Post by lordjynx » 18 Jul 2017, 18:26

18 testing & final /19 testing & final was what I was on previously. It's possible that 18 was doing it too and I just didn't notice it as much.

Unfortunately, the log file isn't showing any errors related to the loading failures. My settings are to log everything.

Authorization is disabled based on these settings:
ControlUsername/Password: Both Blank
RestrictedUsername/Password : Both Blank
FormAuth: No
SecureControl: No
AuthorizedIP: Blank

Thanks hugbug for help!

hugbug
Developer & Admin
Posts: 6746
Joined: 09 Sep 2008, 11:58
Location: Germany (NRW)

Re: 19/19.1 reverse proxy issue

Post by hugbug » 18 Jul 2017, 19:20

With these settings nzbget never sends 401. The authorization errors are also logged but you don't have any in the log. These two facts suggest that the errors come from nginx.

How is nginx protected, via http auth?

There is a bug in safari where it occasionaly stops sending http auth header. I had to develop a special workaround in nzbget for that. Nginx most likely doesn't have such workaround as it requires session tracking.

Well, the way nzbget tracks sessions was actually changed in v19 (when implementing web form auth) but since you don't have authorization in nzbget that change can't be responsible.

lordjynx
Posts: 22
Joined: 23 Jan 2015, 17:46

Re: 19/19.1 reverse proxy issue

Post by lordjynx » 18 Jul 2017, 19:32

HTTP auth, correct.

If v19 didn't change the way authentication works (at least how I'm using it), then I'll look at the nginx side. It's been updated a few times these past few months.

Maybe chrome add-ons/etc. are causing the issue.

Thanks hugbug.

hugbug
Developer & Admin
Posts: 6746
Joined: 09 Sep 2008, 11:58
Location: Germany (NRW)

Re: 19/19.1 reverse proxy issue

Post by hugbug » 18 Jul 2017, 20:17

Is this chrome or safari? The problem I had was only in safari.

lordjynx
Posts: 22
Joined: 23 Jan 2015, 17:46

Re: 19/19.1 reverse proxy issue

Post by lordjynx » 19 Jul 2017, 03:57

Chrome running on Linux Mint 18.2

It *might* be this plugin I'm using called 'nzbget-chrome v1.4' (it still shows downloads and adding works, just not the main css).

The page always seems to load up fine going there directly (it asks for credentials this way though.. plugin ^ does not). I believe chrome possibly blocks using user:pass@wwwsite.com now?

hugbug
Developer & Admin
Posts: 6746
Joined: 09 Sep 2008, 11:58
Location: Germany (NRW)

Re: 19/19.1 reverse proxy issue

Post by hugbug » 19 Jul 2017, 05:21

lordjynx wrote:
19 Jul 2017, 03:57
I believe chrome possibly blocks using user:pass@wwwsite.com now?
I think it is, I've read somewhere about this.

lordjynx
Posts: 22
Joined: 23 Jan 2015, 17:46

Re: [Resolved] 19/19.1 reverse proxy issue

Post by lordjynx » 19 Jul 2017, 14:19

It apparently does as of 58/59. Thanks for assistance as usual hugbug. I'll wait for an update from the add-on developer, if it can even be fixed!

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 3 guests