starred/Prowlarr

Fork 0

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

[FEAT]: Download clients sync #294

New issue

Closed

opened 2026-02-20 09:41:10 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-20 09:41:10 -05:00

Owner

Originally created by @hrenard on GitHub (Sep 18, 2021).

Is there an existing issue for this?

I have searched the existing issues

I have to configure my download clients on every *arr (6).

Describe the solution you'd like

I would like Prowlarr to sync my download clients too.

Describe alternatives you've considered

Doing it manually.
Using NZBHydra2.
Developing another arr.

Anything else?

It expends the scope of the project, but it feels like the right place to do it.
It should be relatively straight forward to implement.

AB#1595

Originally created by @hrenard on GitHub (Sep 18, 2021). ### Is there an existing issue for this? - [X] I have searched the existing issues ### Is your feature request related to a problem? Please describe I have to configure my download clients on every *arr (6). ### Describe the solution you'd like I would like Prowlarr to sync my download clients too. ### Describe alternatives you've considered - Doing it manually. - Using NZBHydra2. - Developing another arr. ### Anything else? It expends the scope of the project, but it feels like the right place to do it. It should be relatively straight forward to implement. [AB#1595](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/1595)

deekerman

2026-02-20 09:41:10 -05:00

closed this issue
added the
Type: Feature Request

Area: Download Clients

Type: Duplicate
labels

deekerman commented

2026-02-20 09:41:12 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Sep 18, 2021):

Duplicate of https://github.com/Prowlarr/Prowlarr/issues/323 (now renamed for clarity / easier searching)

No plans for this.

Please try to search better next time; hopefully it being renamed will help those in the future

@bakerboy448 commented on GitHub (Sep 18, 2021): Duplicate of https://github.com/Prowlarr/Prowlarr/issues/323 (now renamed for clarity / easier searching) No plans for this. Please try to search better next time; hopefully it being renamed will help those in the future

deekerman commented

2026-02-20 09:41:12 -05:00

Author

Owner

@hrenard commented on GitHub (Sep 18, 2021):

Too bad. Sorry for the duplicate.

@hrenard commented on GitHub (Sep 18, 2021): Too bad. Sorry for the duplicate.

deekerman commented

2026-02-20 09:41:12 -05:00

Author

Owner

@neo-neo1 commented on GitHub (Nov 6, 2021):

Why sync indexers yet "no plans" for download clients? Isn't this the central efficiency prowlarr touts?

@neo-neo1 commented on GitHub (Nov 6, 2021): Why sync indexers yet "no plans" for download clients? Isn't this the central efficiency prowlarr touts?

deekerman commented

2026-02-20 09:41:12 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Nov 6, 2021):

Why sync indexers yet "no plans" for download clients? Isn't this the central efficiency prowlarr touts?

Prowlarr only uses Download Clients to send manual searched results to in Prowlarr. It’s not taking over your download stack, just indexer management.

you also typically only setup and configure a download client once nor replace them often if at all

@bakerboy448 commented on GitHub (Nov 6, 2021): > Why sync indexers yet "no plans" for download clients? Isn't this the central efficiency prowlarr touts? Prowlarr only uses Download Clients to send manual searched results to in Prowlarr. It’s not taking over your download stack, just indexer management. you also typically only setup and configure a download client once nor replace them often if at all

deekerman commented

2026-02-20 09:41:12 -05:00

Author

Owner

@Panzer1119 commented on GitHub (Nov 7, 2021):

I'm neither replacing my indexers often if at all.

It would be convenient to have these things in one place, even if it is just to temporarily disable a download client.

But there are more reasons why this could be helpful e.g. if you want to change your priorities.

Just some days ago i changed the port of my download client and then i had to change that little information in all of my 11 *arr instances.

@Panzer1119 commented on GitHub (Nov 7, 2021): I'm neither replacing my indexers often if at all. It would be convenient to have these things in one place, even if it is just to temporarily disable a download client. But there are more reasons why this could be helpful e.g. if you want to change your priorities. Just some days ago i changed the port of my download client and then i had to change that little information in all of my 11 *arr instances.

deekerman commented

2026-02-20 09:41:12 -05:00

Author

Owner

@netty0 commented on GitHub (Nov 7, 2021):

Why sync indexers yet "no plans" for download clients? Isn't this the central efficiency prowlarr touts?

Prowlarr only uses Download Clients to send manual searched results to in Prowlarr. It’s not taking over your download stack, just indexer management.

You can't see the forest for the trees. The fact that Prowlarr would be a good candidate to sync SETTINGS of download clients has nothing to do with how Prowlarr utilizes Download Clients. Users filling out identical fields for Download Clients across Sonarr/Radarr/Prowlarr/etc.. is no different than users filling out indexer settings across Sonarr/Radarr/Prowlarr. Identical use cases.

you also typically only setup and configure a download client once nor replace them often if at all

Says who? This is no different than stating "you typically setup and configure indexer settings once". You're displaying cliche "If I don't need it no one else will" gatekeeper traits.

@netty0 commented on GitHub (Nov 7, 2021): > > Why sync indexers yet "no plans" for download clients? Isn't this the central efficiency prowlarr touts? > > Prowlarr only uses Download Clients to send manual searched results to in Prowlarr. It’s not taking over your download stack, just indexer management. You can't see the forest for the trees. The fact that Prowlarr would be a good candidate to sync SETTINGS of download clients has nothing to do with how Prowlarr utilizes Download Clients. Users filling out identical fields for Download Clients across Sonarr/Radarr/Prowlarr/etc.. is no different than users filling out indexer settings across Sonarr/Radarr/Prowlarr. Identical use cases. > > you also typically only setup and configure a download client once nor replace them often if at all Says who? This is no different than stating "you typically setup and configure indexer settings once". You're displaying cliche "If I don't need it no one else will" gatekeeper traits.