starred/Prowlarr

Fork 0

mirror of https://github.com/Prowlarr/Prowlarr.git synced 2026-03-02 22:57:22 -05:00

Synology Prowlarr won't add magnet to DownloadStation #1024

New issue

Closed

opened 2026-02-20 10:06:28 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 10:06:28 -05:00

Owner

Originally created by @devonuto on GitHub (Mar 12, 2024).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

DS is connected using 5916 port:

But if I click download on any link, it shows a red cloud, and says "failed to add task from url magnet"
Then if I look in the logs, I see a Reason: 120 - Unknown error.
Can confirm the API works for DownloadStation, as I use it for another application.

Trace logs attached.

Expected Behavior

Magnet is added to DownloadStation

Steps To Reproduce

Search in Prowlarr, click any "Add release to download client" button against any torrent. See failures.

Environment

- OS: DSM 7.2.1-69057 Update 3
- Prowlarr: 1.13.3.4273
- Docker Install: N/A using Prowlarr from Synology Package Centre (20230427-6)
- Using Reverse Proxy: N/A
- Browser: Chrome Version 122.0.6261.112 (Official Build) (64-bit)

What branch are you running?

Master

Trace Logs?

prowlarr.trace.txt

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @devonuto on GitHub (Mar 12, 2024). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior DS is connected using 5916 port: ![image](https://github.com/Prowlarr/Prowlarr/assets/3507808/31599dcf-47ae-4ad9-b75b-bab8127fc449) But if I click download on any link, it shows a red cloud, and says "failed to add task from url magnet" Then if I look in the logs, I see a Reason: 120 - Unknown error. Can confirm the API works for DownloadStation, as I use it for another application. Trace logs attached. ### Expected Behavior Magnet is added to DownloadStation ### Steps To Reproduce Search in Prowlarr, click any "Add release to download client" button against any torrent. See failures. ### Environment ```markdown - OS: DSM 7.2.1-69057 Update 3 - Prowlarr: 1.13.3.4273 - Docker Install: N/A using Prowlarr from Synology Package Centre (20230427-6) - Using Reverse Proxy: N/A - Browser: Chrome Version 122.0.6261.112 (Official Build) (64-bit) ``` ### What branch are you running? Master ### Trace Logs? [prowlarr.trace.txt](https://github.com/Prowlarr/Prowlarr/files/14570174/prowlarr.trace.txt) ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 10:06:28 -05:00

closed this issue
added the
Type: Bug

Area: Download Clients

sonarr upstream
labels

deekerman commented

2026-02-20 10:06:30 -05:00

Author

Owner

@devonuto commented on GitHub (Mar 12, 2024):

Just looking at the trace logs, I noticed:

{"error":{"code":120,"errors":{"name":"destination","reason":"required"}},"success":false}

So I added the same default destination that I have in my DownloadStation config:

Into the Download Client config in Prowlarr:

Now it works. Seems the "leave blank to use the default Download Station location" is what doesn't work here.

Would consider this a work-around, but given it says to leave blank to use the default, it should probably do that.

@devonuto commented on GitHub (Mar 12, 2024): Just looking at the trace logs, I noticed: {"error":{"code":120,"errors":{"name":"destination","reason":"required"}},"success":false} So I added the same default destination that I have in my DownloadStation config: ![image](https://github.com/Prowlarr/Prowlarr/assets/3507808/e9666ec9-f6b8-4248-9e13-29b88fd26755) Into the Download Client config in Prowlarr: ![image](https://github.com/Prowlarr/Prowlarr/assets/3507808/70f6e278-9955-417d-883a-a49d0ceb89a5) Now it works. Seems the "leave blank to use the default Download Station location" is what doesn't work here. Would consider this a work-around, but given it says to leave blank to use the default, it should probably do that.

deekerman commented

2026-02-20 10:06:30 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Mar 12, 2024):

Likely needs github.com/Sonarr/Sonarr@07cbd7c8d2

@bakerboy448 commented on GitHub (Mar 12, 2024): Likely needs https://github.com/Sonarr/Sonarr/commit/07cbd7c8d29f2e0731f0a11c685f898f7e83b0c8

deekerman commented

2026-02-20 10:06:30 -05:00

Author

Owner

@devonuto commented on GitHub (Mar 12, 2024):

Likely needs github.com/Sonarr/Sonarr@07cbd7c8d2

Given I found a workaround that I added, I don't think it needs sonarr. Just not picking up the default download location.

@devonuto commented on GitHub (Mar 12, 2024): > Likely needs https://github.com/Sonarr/Sonarr/commit/07cbd7c8d29f2e0731f0a11c685f898f7e83b0c8 Given I found a workaround that I added, I don't think it needs sonarr. Just not picking up the default download location.

deekerman commented

2026-02-20 10:06:30 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Mar 12, 2024):

Likely needs Sonarr/Sonarr@07cbd7c

That's surely an improvement, but what I pushed fixes this issue already.

@mynameisbogdan commented on GitHub (Mar 12, 2024): > Likely needs [Sonarr/Sonarr@07cbd7c](https://github.com/Sonarr/Sonarr/commit/07cbd7c8d29f2e0731f0a11c685f898f7e83b0c8) That's surely an improvement, but what I pushed fixes this issue already.