Robert Dailey

I think your solution is acceptable, as long as if I disable the control user/pass (to allow access to web UI with no login required), the RPC endpoints still require...

Then we're back to square one. I need to be able to control authentication between web UI and API separately. That's the whole point of what I'm asking for. Whether...

I'm starting to think what I'm wanting to do won't work anyway. The webUI calls into NZBget's own RPC, which means from my reverse proxy I can't tell the difference...

Can I set the URL to nzbget to this? https://domain.com/nzbget/user:pass If I can do that, then my proxy is SSL so the credentials should be encrypted. Organizr loads nzbget inside...

Even if I can, I think I shouldn't because since nzbget is in an iframe, the username & password will be exposed on the client side due to the iframe...

The best way I have found to solve this issue with no required changes from nzbget is as follows: ``` set $upstream_nzbget http://nzbget:6789; location /nzbget { auth_request /organizr/auth-0; proxy_pass $upstream_nzbget;...

@lachlanhunt do you have instructions for nginx as well? Given that the developers have no intention of developing a proper built-in solution for this, I may go with your solution...

I don't see how those are examples of what I originally asked for. I already do auth through Organizr for the web UI, I just don't want it doing Organizr...

@nemchik Right below your comment ([here](https://github.com/nzbget/nzbget/issues/577#issuecomment-663933166)) he explains why your solution doesn't work. Leaving control creds blank in nzbget is the issue. Again, I don't think there's a solution mentioned...

> Honestly, I didn't have to go to the trouble of getting you all this info. Especially given that your responses have been rather negative and dismissive of the information....