starred/Cleanuparr-Cleanuparr
1
0
Fork 0
mirror of https://github.com/Cleanuparr/Cleanuparr.git synced 2026-02-04 12:21:33 -06:00
Code Issues 38 Packages Projects Releases 10 Wiki Activity

[FEATURE] Support Basic Auth for qBittorrent Download Client #45

New Issue
Closed
opened 2025-10-09 16:57:01 -05:00 by giteasync · 5 comments
giteasync commented 2025-10-09 16:57:01 -05:00
Owner
Copy Link

Originally created by @incredible-dev on GitHub.

What would you like to see implemented next?

Description:

Cleanuparr currently fails to connect to qBittorrent instances that are protected with Basic Authentication. This limitation prevents users from integrating their secure qBittorrent setups with Cleanuparr.

Expected Behavior:

Cleanuparr should be able to connect to qBittorrent instances that require Basic Auth by allowing users to provide a username and password (or token) in the configuration.

Steps to Reproduce:

  1. Set up qBittorrent with Basic Auth enabled.
  2. Configure Cleanuparr with the correct qBittorrent endpoint and credentials.
  3. Attempt connection – observe connection failure.

Actual Behavior:

Cleanuparr fails to authenticate with the qBittorrent client and throws a connection error.

Proposed Solution:

Add support for HTTP Basic Authentication when connecting to qBittorrent, either via headers or URL-based credentials.

Originally created by @incredible-dev on GitHub. ### What would you like to see implemented next? **Description:** Cleanuparr currently fails to connect to qBittorrent instances that are protected with Basic Authentication. This limitation prevents users from integrating their secure qBittorrent setups with Cleanuparr. **Expected Behavior:** Cleanuparr should be able to connect to qBittorrent instances that require Basic Auth by allowing users to provide a username and password (or token) in the configuration. **Steps to Reproduce:** 1. Set up qBittorrent with Basic Auth enabled. 2. Configure Cleanuparr with the correct qBittorrent endpoint and credentials. 3. Attempt connection – observe connection failure. **Actual Behavior:** Cleanuparr fails to authenticate with the qBittorrent client and throws a connection error. **Proposed Solution:** Add support for HTTP Basic Authentication when connecting to qBittorrent, either via headers or URL-based credentials.
giteasync added the
enhancement
planned
 labels 2025-10-09 16:57:01 -05:00
giteasync commented 2025-10-09 16:57:02 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

@Eyt-Lev Open a separate issue and provide more context, like logs and stuff and what is not working.

@Flaminel commented on GitHub: @Eyt-Lev Open a separate issue and provide more context, like logs and stuff and what is not working.
giteasync commented 2025-10-09 16:57:02 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

This is now available in v2.1.6.

@Flaminel commented on GitHub: This is now available in `v2.1.6`.
giteasync commented 2025-10-09 16:57:02 -05:00
Author
Owner
Copy Link

@incredible-dev commented on GitHub:

Yes, this is already supported in the ARR stack.
Radarr and Sonarr are able to connect to qBittorrent instances using Basic Auth without any issues.
They typically allow the configuration of the full base URL including credentials (https://user:pass@host) or use additional headers if needed.

It would be helpful if Cleanuparr could support the same capability, as many users secure their download clients in similar ways.

@incredible-dev commented on GitHub: Yes, this is already supported in the ARR stack. Radarr and Sonarr are able to connect to qBittorrent instances using Basic Auth without any issues. They typically allow the configuration of the full base URL including credentials (https://user:pass@host) or use additional headers if needed. It would be helpful if Cleanuparr could support the same capability, as many users secure their download clients in similar ways.
giteasync commented 2025-10-09 16:57:02 -05:00
Author
Owner
Copy Link

@Eyt-Lev commented on GitHub:

how does it work now? i spent a couple hours trying to connect qb
what is that if not basic auth

Image

I'm just trying to connect qb can someone help? (i know it should probably be a separate issue but it seems relevant)

@Eyt-Lev commented on GitHub: how does it work now? i spent a couple hours trying to connect qb what is that if not basic auth <img width="567" height="827" alt="Image" src="https://github.com/user-attachments/assets/0c842780-4daf-48e7-8a03-e69753a77694" /> I'm just trying to connect qb can someone help? (i know it should probably be a separate issue but it seems relevant)
giteasync commented 2025-10-09 16:57:03 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

Is this something that is already available through the arrs?

@Flaminel commented on GitHub: Is this something that is already available through the arrs?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
planned
pull-request
Mirrored from GitHub Pull Request
question
No Label
enhancement
planned
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Cleanuparr-Cleanuparr#45
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?