The NzbDrone log shows the following error:
Unable to connect to SABnzbd, please check your settings: Unable to connect to SABnzbd, please check your settings
Exception:
NzbDrone.Core.Download.Clients.DownloadClientException: Unable to connect to SABnzbd, please check your settings
at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.CheckForError (IRestResponse response) [0x00000] in :0
at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.ProcessRequest (IRestRequest restRequest, System.String action, NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdSettings settings) [0x00000] in :0
at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.GetQueue (Int32 start, Int32 limit, NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdSettings settings) [0x00000] in :0
at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.GetQueue () [0x00000] in :0
I have added a category TV to my Sabnzbd settings.After that I tried to let NzbDrone send the download command with that category.
Before this commit everything worked great. Does anybody know how I get the NzbDrone -> Sabnzbd connection working again?
Based on the error and the logs, drone is unable to connect to SAB at all as the request isn’t completing successfully. Unfortunately there isn’t more information available.
The change you highlight doesn’t change how drone connects to SAB, but tetsing will fail if a category is not configured, this has been fixed in develop now, though category’s are case sensitive, so make sure the category entered in drone matches the category in SAB exactly.
Okay, couple of more questions. you removed the hostname, which makes me assume it’s not on localhost. sabnzbd appears to be running on a synology nas. What about Drone?
If drone is on the synology too then use localhost/127.0.0.1.
If not, then try query sab from the browser: localhost:4000/api?mode=history&limit=1&apikey=<>&output=json
Replace the hostname&port and the apikey with the correct values.
As a result you should get a json containing the history, or just an error.
probably starting with {“history”:{“uniconfig”