Duplicate check
Before submitting a bug report, I have:
What is the behavior?
After updating qBittorrent to version 5.2.0, Cleanuparr can no longer log in to the qBittorrent client and now shows the error "Failed to login to client".
I noticed the same issue earlier with Homarr integrations. The Homarr developers confirmed that qBittorrent changed something in their API/authentication behavior in 5.2.0 and released a fix for it.
Now Cleanuparr appears to be affected by the same change.
Which operating system do you use?
Linux
What type of deployment do you use?
Docker container
Relevant log output
Failed to login to qBittorrent client 20ab86eb-e118-4b8d-bd1f-b74f9eaf1e8e
Exception
System.Net.Http.HttpRequestException: An error occurred while sending the request.
---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
---> System.Net.Sockets.SocketException (104): Connection reset by peer
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|4_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
at Microsoft.Extensions.Http.PolicyHttpMessageHandler.SendCoreAsync(HttpRequestMessage request, Context context, CancellationToken cancellationToken)
at Polly.Retry.AsyncRetryEngine.ImplementationAsync[TResult](Func`3 action, Context context, CancellationToken cancellationToken, ExceptionPredicates shouldRetryExceptionPredicates, ResultPredicates`1 shouldRetryResultPredicates, Func`5 onRetryAsync, Int32 permittedRetryCount, IEnumerable`1 sleepDurationsEnumerable, Func`4 sleepDurationProvider, Boolean continueOnCapturedContext)
Anything else?
homarr-labs/homarr#5639
Duplicate check
Before submitting a bug report, I have:
What is the behavior?
After updating qBittorrent to version 5.2.0, Cleanuparr can no longer log in to the qBittorrent client and now shows the error "Failed to login to client".
I noticed the same issue earlier with Homarr integrations. The Homarr developers confirmed that qBittorrent changed something in their API/authentication behavior in 5.2.0 and released a fix for it.
Now Cleanuparr appears to be affected by the same change.
Which operating system do you use?
Linux
What type of deployment do you use?
Docker container
Relevant log output
Anything else?
homarr-labs/homarr#5639