Heimdall failing to get Radarr status #741
Replies: 9 comments 1 reply
-
Hello, Have you checked that the update did not generate a new token? |
Beta Was this translation helpful? Give feedback.
-
@ratnose are you sure about those versions. I am running Heimdall v2.2.2 and Radarr v3.2.2.5080 and it's working fine. |
Beta Was this translation helpful? Give feedback.
-
Same problem here, checked API token, URL and even on ip-adres but it keeps giving the error stated above. Heimdall version V2.2.2 Radarr V4.0.0.5213 it seems to me it is in radarr but not 100% sure. |
Beta Was this translation helpful? Give feedback.
-
Same issue here with Heimdall 2.2.2 and Radarr 4.0.0.5342. |
Beta Was this translation helpful? Give feedback.
-
Same here... |
Beta Was this translation helpful? Give feedback.
-
Same issue with v2.2.3 |
Beta Was this translation helpful? Give feedback.
-
Any update on this? Running Heimdall 2.4.11 with Radarr 4.1.0.6175. Still having this issue. |
Beta Was this translation helpful? Give feedback.
-
This still seems to be an issue, but is it with LSIO or Heimdall? |
Beta Was this translation helpful? Give feedback.
-
I had read that no status on the Radarr box (when the API token has been registered) may mean that the PHP memory is set too low. Someone offered the suggestion on a Synology NAS using WebStation to adjust PHP MEMORY_LIMIT to above 512M. I did this to no avail. Does anyone have any insight on the issue of no status on Radarr? (SAB, Lidarr and Sonarr all work properly) |
Beta Was this translation helpful? Give feedback.
-
Since Radarr updated to API v3 Heimdall gives me this error:
"Failed: Please make sure your URL is correct and that there is a trailing slash"
I have tried adding a slash same issue.
I am running everything inside a docker-compose setup, Heimdall v2.2.3 Radarr v4.0.0.5146
Beta Was this translation helpful? Give feedback.
All reactions