#Sabnzbd refused to connect download#

#Sabnzbd refused to connect download#

Why? Passing nzb files (or download insructions relating thereto) and otherwise managing media renaming, etc. Where? Localhost (all installed on the same NAS) What is talking to what? Sonarr/Radarr talking to SABnzbd SSH and other service ports came into the convo because the Asustor support team said that my NAS may have reserved these for itself and somehow this is the reason why the app requests are failing but maybe that's a stretch.

1) Apps talking to each other on the localhost (has nothing to do with router)Ģ) Accessing the apps remotely (where port forwarding comes into play)īasically, I need to figure out what is actively denying these requests on the NAS.

Yes, I guess I am conflating things here: When I try add SABnzbdPlus as a download client, I get the following error when trying to connect from within both Sonarr and Radarr to SABnzbdPlus (port and API key redacted): Here are a few examples of how my apps are failing to work together:Įxample 1: I send NZBs from Sonarr and Radarr to SABnzbdPlus. Has the migration confused it somehow? Are app permissions screwed up due to the migration perhaps? I wonder if this migration has confused my router? This seems unlikely because I have factory reset my router as part of this diagnosis process, which brings me back to the NAS. I have setup port forwarding for the apps on the NAS, and it says that these app ports are being forwarded correctly. It means that the apps were previously setup on the older NAS but, in theory, this shouldn't matter - the new NAS should just pick up on the existing installs since its the same brand (and this is according to their own documentation).

I have migrated my HDDs from the old NAS to the new one.

Background: I've just got a new NAS that I use for media management and I am having a problem where my apps can't talk to each other via API since the upgrade.