Readarr connection broken
Closed this issue · 7 comments
Docker composed, standalone
Unable to connect to Readarr
Package Version 0.4.4.2686-ls131 by linuxserver.io
[ERROR] 2024/11/28 21:48:49 Readarr (http://192.168.y.x:8787): api.Get(v1/queue): httpClient.Do(req): Get "http://192.168.y.x:8787/api/v1/queue?includeUnknownAuthorItems=true&page=1&pageSize=2000&sortDirection=ascending&sortKey=timeleft": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
The exact URL and API key are matched as defined, and working in Postman GET, if the API-key key is defined as X-Api-Key and added to header.
Unpackerr can't connect to 192.168.y.x on port 8787. Either wrong IP, wrong port, or the network is unreachable from unpacker's location. Did you have any questions?
In addition, curl also works at that port an IP from the Docker host.
The POSTMAN, Curl, and web browser can access Readarr from various points on LAN.
UnPackerr can access 3 other services properly.
[INFO] 2024/11/28 22:10:39 [Whisparr] Updated (http://192.168.y.x:6969): 0 Items Queued, 0 Retrieved
[INFO] 2024/11/28 22:10:39 [Radarr] Updated (http://192.168.y.x:7878): 15 Items Queued, 15 Retrieved
[INFO] 2024/11/28 22:10:39 [Lidarr] Updated (http://192.168.y.x:8686): 3 Items Queued, 3 Retrieved
[INFO] 2024/11/28 22:10:39 [Sonarr] Updated (http://192.168.y.x:9090): 240 Items Queued, 240 Retrieved
[ERROR] 2024/11/28 22:10:49 Readarr (http://192.168.y.x:8787): api.Get(v1/queue): httpClient.Do(req): Get...
The error messages indicates a lack of network route from unpackerr to that IP, or you've set the timeout to 0. Not really any other in-betweens. Including the entire log instead of edited snippets will increase my ability to provide troubleshooting steps.
Log from last boot, removed IP and faff working logs.
How long does postman take to pull a result from this url? http://192.168.y.x:8787/api/v1/queue?includeUnknownAuthorItems=true&page=1&pageSize=2000&sortDirection=ascending&sortKey=timeleft
How many bytes is the result?
Strange. If x and y are the same variables throughout the log, then you have a gremlin I can't explain. Perhaps try drastic things like reboot, recreate the container, try another image (hotio vs golift), etc. Try increasing the timeout, just in case.