Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonarr develop branch brakes calendar integration #538

Closed
3 tasks done
xicoms opened this issue Dec 13, 2022 · 4 comments
Closed
3 tasks done

Sonarr develop branch brakes calendar integration #538

xicoms opened this issue Dec 13, 2022 · 4 comments
Assignees
Labels
🐛 Bug Something isn't working

Comments

@xicoms
Copy link

xicoms commented Dec 13, 2022

Environment

Docker

Version

v0.10.7

Describe the problem

Upgrading sonarr container with the develop image broke sonarr's calendar integration with homarr.
Sonarr image version: 4.0.0.280—Dec 12 2022

Additional info

Sonarr Api response: (console)
Request Method: POST
Status Code: 500
content-length: 645
content-type: application/json; charset=utf-8
date: Tue, 13 Dec 2022 11:12:51 GMT

Please tick the boxes

@xicoms xicoms added the 🐛 Bug Something isn't working label Dec 13, 2022
@miguelccoelho
Copy link

I have a question for you, on your sonarr service, did you add the service URL with an IP address, or a DNS name? I'm asking because I got a 500 error too on my system, when using a DNS name, but when I switch to IP address, it starts working. Would like to confirm if we have similarities or not.

In my case, this is what I get in the network tab, preview:
{message: "getaddrinfo ENOTFOUND sonarr.rabbit", name: "Error",…}
code: "ENOTFOUND"
config: {transitional: {silentJSONParsing: true, forcedJSONParsing: true, clarifyTimeoutError: false},…}
message: "getaddrinfo ENOTFOUND sonarr.rabbit"
name: "Error"
stack: "Error: getaddrinfo ENOTFOUND sonarr.rabbit\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)"
status: null

@manuel-rw
Copy link
Collaborator

manuel-rw commented Jan 10, 2023

I would just like to clarify quickly here: We do not support development versions of integrations, as they often contain breaking changes or changes are frequently made.
The time investment is just not worth the outcome, as most people use stable.
We will fix this issue when Sonarr merges this from development to stable.

@manuel-rw manuel-rw closed this as not planned Won't fix, can't repro, duplicate, stale Jan 18, 2023
@manuel-rw
Copy link
Collaborator

Closing as not planned. Please reopen if needed

@ajnart ajnart reopened this Feb 2, 2023
@ajnart ajnart self-assigned this Feb 2, 2023
@ajnart ajnart linked a pull request Feb 3, 2023 that will close this issue
@ajnart
Copy link
Owner

ajnart commented Feb 8, 2023

Done in #689

@ajnart ajnart closed this as completed Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants