SABnzbd Forums

Hi all, new user here having just switched over from NZBGet.

I've set up SABnzbd using the linuxserver docker container (latest version). Over an SSH tunnel the application works perfectly.

However, when accessed via a reverse proxy it has weird behaviour. Specifically, it frequently redirects me to the queue page or (more often) the login page. The login page only works a fraction of the time too.

Here is a GIF showing this behaviour:


My Nginx configuration is created by Nginx Proxy Manager (as a docker container). This works fine with my other containers and had no trouble with NZBGet. The issue occurs regardless of whether I use HTTP or HTTPS.

I am happy share my entire Nginx configuration if that would be helpful. Otherwise, I was hoping that someone with more knowledge of Nginx or a working setup with Nginx Proxy Manager would know the cause of the issue directly.

I know nothing about nginx, so just some hints:

What happens when you turn off login-required on the SAB webinterface?

Did you inspect the logging van SABnzbd and nginx?

What if you use a different browser?

Did you inspect browser interaction with nginx? Chrome: CTRL + SHIFT + I

Thanks for the suggestions.

What happens when you turn off login-required on the SAB webinterface?

The app works as expected with no redirects.

Did you inspect the logging van SABnzbd and nginx?

The only SABnzbd log is a repeated pair saying the login was successful, every time I login after being redirected to the login page.

There is nothing that stands out in the Nginx logs but I'm not an experienced user so can't say for sure.

What if you use a different browser?

The issue is also present when using Chrome.

Did you inspect browser interaction with nginx? Chrome: CTRL + SHIFT + I

Yes. No errors appear in the console.

When redirected to the login page, the cookies from the previous login in are still in memory. In fact, removing /login from the URL and refreshing often works and returns the queue page.

Make sure that your url_base in Config Specials is setup correctly.

I have my services sitting on their own sub-domains so I'm using "/" as the url_base. This gets converted to an empty string when entered in the web application settings (assume this is the "no trailing slash allowed" rule). Is this expected behaviour?