Is there an existing issue for this?

• I have searched the existing open and closed issues

Current Behavior

Appears similar to Issue #3925 that is now closed and unable to reopen.

I am not able to use the search function in readarr as when I enter anything I get the following error message in Readarr:

"Search for 'test' failed. Unable to communicate with ReadarrAPI, returning status code: 522."

Expected Behavior

Readarr Search function returns found books

Steps To Reproduce

No response

Environment

- OS: Unraid 7.1.3
- Readarr: 0.4.19.2806
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser: N/A
- Database: Sqlite 3.45.1

What branch are you running?

Master

Trace Logs?

2025-06-15 13:12:37,142 DEBG 'readarr' stdout output:
[Warn] HttpClient: HTTP Error - Res: HTTP/2.0 [POST] https://api.bookinfo.club/v1/book/bulk: 522.522 (0 bytes)

2025-06-15 13:12:37,270 DEBG 'readarr' stdout output:
[Warn] BookInfoProxy: NzbDrone.Common.Http.HttpException: HTTP request failed: [522:522] [POST] at [https://api.bookinfo.club/v1/book/bulk]

[v0.4.19.2806] NzbDrone.Common.Http.HttpException: HTTP request failed: [522:522] [POST] at [https://api.bookinfo.club/v1/book/bulk]
2025-06-15 13:12:37,270 DEBG 'readarr' stdout output:

at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Readarr.Common/Http/HttpClient.cs:line 119
at NzbDrone.Common.Http.HttpClient.PostAsync[T](HttpRequest request) in ./Readarr.Common/Http/HttpClient.cs:line 369
at NzbDrone.Common.Http.HttpClient.Post[T](HttpRequest request) in ./Readarr.Common/Http/HttpClient.cs:line 377
at NzbDrone.Core.MetadataSource.BookInfo.BookInfoProxy.MapSearchResult(List`1 ids) in ./Readarr.Core/MetadataSource/BookInfo/BookInfoProxy.cs:line 493
at NzbDrone.Core.MetadataSource.BookInfo.BookInfoProxy.Search(String query, Boolean getAllEditions) in ./Readarr.Core/MetadataSource/BookInfo/BookInfoProxy.cs:line 296

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.