Sonarr can't connect to download station (Synology DSM7)

Help & Support
#1

Updated today from DSM 6 to 7 and sonarr stopped working. No longer I can add the Download Station as client, because sonarr can’t connect to it.

I cant use docker, my NAS does not support it.

The user is the same, with no 2 factor enabled.
Group is sc-download and all the permissions are ok (group and user can read/write).

Trying to add Download Station as Torrent Client, using:

host: 192.168.1.xxx *this is the ip address for the synology nas
port: port (this is the port I use to access the NAS)
username: user under the sc-download group
password
use SSL disabled

Can somebody please help me?

Log is above:

Sonarr version (exact version): 3.0.6.1265 Jun 17 2021
Mono version (if Sonarr is not running on Windows): 5.20.1.34-17
OS: Synology DSM 7.0-41890
Debug logs:

2021-08-05 20:13:34.2|Warn|SonarrErrorPipeline|Invalid request Validation failed:
– Host: Unable to connect to Torrent Download Station
2021-08-05 20:27:18.4|Info|RssSyncService|Starting RSS Sync
2021-08-05 20:27:20.0|Info|DownloadDecisionMaker|Processing 100 releases
2021-08-05 20:27:21.6|Info|RssSyncService|RSS Sync Completed. Reports found: 100, Reports grabbed: 0
2021-08-05 20:38:20.2|Info|SceneMappingService|Updating Scene mappings
2021-08-05 20:42:50.7|Info|RssSyncService|Starting RSS Sync
2021-08-05 20:42:52.3|Info|DownloadDecisionMaker|Processing 100 releases
2021-08-05 20:42:53.5|Info|RssSyncService|RSS Sync Completed. Reports found: 100, Reports grabbed: 0
2021-08-05 20:58:22.0|Info|RssSyncService|Starting RSS Sync
2021-08-05 20:58:23.5|Info|DownloadDecisionMaker|Processing 100 releases
2021-08-05 20:58:24.7|Info|RssSyncService|RSS Sync Completed. Reports found: 100, Reports grabbed: 0
2021-08-05 20:58:45.2|Error|TorrentDownloadStation|Error testing Torrent Download Station

[v3.0.6.1265] NzbDrone.Common.Http.HttpException: HTTP request failed: [400:BadRequest] [GET] at [http://192.168.1.xxx:port/webapi/query.cgi?api=(removed)&version=1&method=query&query=SYNO.API.Auth%2CSYNO.DownloadStation.Task]
at NzbDrone.Core.Download.Clients.DownloadStation.Proxies.DiskStationProxyBase.ProcessRequest[T] (NzbDrone.Common.Http.HttpRequestBuilder requestBuilder, System.String operation, NzbDrone.Core.Download.Clients.DownloadStation.DiskStationApi api, NzbDrone.Core.Download.Clients.DownloadStation.DownloadStationSettings settings) [0x000e8] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Download\Clients\DownloadStation\Proxies\DiskStationProxyBase.cs:125
at NzbDrone.Core.Download.Clients.DownloadStation.Proxies.DiskStationProxyBase.UpdateApiInfo (NzbDrone.Core.Download.Clients.DownloadStation.DownloadStationSettings settings) [0x0005e] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Download\Clients\DownloadStation\Proxies\DiskStationProxyBase.cs:207
at NzbDrone.Core.Download.Clients.DownloadStation.Proxies.DiskStationProxyBase.GetApiInfo (NzbDrone.Core.Download.Clients.DownloadStation.DiskStationApi api, NzbDrone.Core.Download.Clients.DownloadStation.DownloadStationSettings settings) [0x00022] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Download\Clients\DownloadStation\Proxies\DiskStationProxyBase.cs:234
at NzbDrone.Core.Download.Clients.DownloadStation.Proxies.DiskStationProxyBase.GetApiInfo (NzbDrone.Core.Download.Clients.DownloadStation.DownloadStationSettings settings) [0x00000] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Download\Clients\DownloadStation\Proxies\DiskStationProxyBase.cs:248
at NzbDrone.Core.Download.Clients.DownloadStation.TorrentDownloadStation.ValidateVersion () [0x00000] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Download\Clients\DownloadStation\TorrentDownloadStation.cs:392
at NzbDrone.Core.Download.Clients.DownloadStation.TorrentDownloadStation.TestConnection () [0x00000] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Download\Clients\DownloadStation\TorrentDownloadStation.cs:356

400 The plain HTTP request was sent to HTTPS port

400 Bad Request

The plain HTTP request was sent to HTTPS port
nginx

2021-08-05 20:58:45.2|Warn|SonarrErrorPipeline|Invalid request Validation failed:
– Host: Unable to connect to Torrent Download Station
Description of issue:

Done some testing, and if I copy and paste [http://192.168.1.xxx:port/webapi/query.cgi?api=(removed)&version=1&method=query&query=SYNO.API.Auth%2CSYNO.DownloadStation.Task]

to my chrome, and change http to https, I get a response:

{“data”:{“SYNO.API.Auth”:{“maxVersion”:7,“minVersion”:1,“path”:“entry.cgi”},“SYNO.DownloadStation.Task”:{“maxVersion”:3,“minVersion”:1,“path”:“DownloadStation/task.cgi”}},“success”:true}

But I have no idea to where I can fix this either on the NAS or the Sonarr configuration.

Can someone share a light on this, please? Thanks!

#2

I have done the same upgrade on my Synology Diskstation today and it looks like neither Sonarr nor Radarr are compatible with this new DSM 7.

I do wish when Synology replace their core programs they let us know which of our installed packages will stop working before we upgrade the system since we cannot now downgrade back to the previous versions DSM.

This is my second Diskstation, I got my original 10 years ago. This is the first time they have released a new DSM that has not been compatible with Sonarr or Radarr.

#3

That’s a shame. I did check on synocommunity if there were mono and sonarr packages for dsm7 before upgrading, and since they were available, I thought it would be ok. Oh, how I regret this.

I did set the NAS and Sonarr ages ago, and I was supposed to configure it like I did this time, right? Using the host and port just like the way I connect to the NAS? Every tutorial I find is about using docker (wich my NAS can’t) or using another app instead of Download Station.

On the weird side, Sonarr is able to find all the tv shows that are on the disks, so it is communicating with the NAS, but not when I try to set the download client.

#4

Had the same experience. Latest version of Sonarr doesn’t need Mono anymore.
Just install Sonarr in Docker; after installing it, Sonarr works like a charm if you follow this procedure @
[English]

[Dutch]
https://sdekraa.tweakblogs.net/blog/18374/nzbget-sonarr-radarr-en-bazarr-op-synology-(docker)

DSM7 is a joke (based on my experiences with it).

#5

download station is a garbage download client; switch to something else

but it’s fixed in nightly

1 Like
#6

I know DS is very limited, but there is no other app available to DSM 7 and I can’t use docker because my NAS model does not support it, unfortunately.

What does fixed in nightly means? Where can I get the fixed version?

#7

Fixed on the nightly branch.
https://wiki.servarr.com/sonarr/faq#how-do-i-update-sonarr

#9

Oh, I see.

But it seems that this would only be possible to install if I were using docker. Guess I’ll have to wait until the goodfolks at synocommunity updates the native distribution.

Edit: My bad, I missed that this nightly is actually called develop. Tried with it, version 3.0.6.1301—Aug 7 2021, and still no luck. Tried even with my personal account (with admin rights) and even the default admin account (enabled just for this test). Still the same error.

#10

I’ll be dammed, I figured it out! I was using the wrong port! I was using the same port I use to access the NAS, but it IS a https port, thus resulting in the error above. On the DSM control panel, under Login Portal there is both http and https ports. I tried using the http one and it worked. DS is added as a client.

Thanks for all the replies, and have a wonderful day.

1 Like
#11

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.