Error connecting from Sonarr to NZBGet

[prizebeef]

I have configured both NZBGet and Sonarr using Docker containers on a single host. Both are configured behind an NGINX reverse proxy linked with Lets Encrypt, so that I can expose each to a domain name via HTTPS connections (port 443).

So I can connect to either container using:
[list]http://dockerhost:defaultport[/list]
[list]http://dockerhost:6789[/list]
[list]http://dockerhost:8989[/list]

Or:
[list]https://nzb.mydomain.com[/list]
[list]https://sonarr.mydomain.com[/list]

NZBGet has the “AddUsername” and “AddPassword” fields populated. I reuse these credentials below in the Sonarr side.

I am trying to configure the Sonarr client to connect with NZBGet within the Settings > Download Client

I choose to add, with the big “+” button. Select “NZBGet” and changed the Host, Port and SSL (tick box) fields with every combination! I get 2 different error messages. 1 is if it cannot connect to the NZBGet instance at all, and the 2nd indicates it can reach the server but does not authenticate. This is the error message received when testing this and I am also unable to Save this config as a result as well:

Test was aborted due to an error: Error response received from nzbget: { “name”: “JSONRPCError”, “code”: 401, “message”: “Access denied” }

[fanboy]

I believe you need to use Restricted level not Add

[bakerboy448]

there is no reason to ever go through your reverse proxy to connect docker containers - you’re adding an unneeded single point of failure and additional complexity and latency.

SSL should also not be used between containers as you can effectively never get valid, signed SSL certs for local non-existent domains

401 is either bad credentials, a bad nzbget setting, or a poor setup somewhere