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

Unclear Sonarr installation feedback #72372

Closed
starman2k01 opened this issue May 23, 2022 · 28 comments · Fixed by #127620 · May be fixed by #127625
Closed

Unclear Sonarr installation feedback #72372

starman2k01 opened this issue May 23, 2022 · 28 comments · Fixed by #127620 · May be fixed by #127625

Comments

@starman2k01
Copy link

The problem

Feedback
Sonarr stopped working, so I deleted and re-installed. Filled in URL and API Key, "Failed to connect". Tried dozens of different URL formats. No feedback on what failed. Why not give the user exactly WHAT is failing? Client refused? Wrong API key? Can't ping client? etc. etc.
Latest HASS supervised.

URL
https://www.home-assistant.io/integrations/sonarr/

Version
2022.5.4

What version of Home Assistant Core has the issue?

Home Assistant Core 2022.5.5 Home Assistant Supervisor 2022.05.2 Home Assistant OS 8.1 Kernel version 5.15.32-v8 Agent version 1.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

sonarr

Link to integration documentation on our website

https://www.home-assistant.io/integrations/sonarr/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@probot-home-assistant
Copy link

sonarr documentation
sonarr source
(message by IssueLinks)

@probot-home-assistant
Copy link

Hey there @ctalkington, mind taking a look at this issue as it has been labeled with an integration (sonarr) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)

@Flagun
Copy link

Flagun commented May 27, 2022

I have the same problem. I removed the integration and tried to add it again with no success. Error: failed to connect.

@Cafun
Copy link

Cafun commented Jun 5, 2022

I also have the same problem. The URL I entered is accessible by Home Assistant.

@sbeaudoin
Copy link

Have it too. My sonarr is a docker and accessible on a specific port I must provinde in the url. There is a port redirection, meaning I access the web interface with port 8084 from any PC, but the docker port who is routed from 8084 is 8989.

@elforesto
Copy link

I found a workaround for this. You have to specify the port at the end for it to work, otherwise it seems to assume the default of 8989. Example: https://sonarr.mylan.local:443 if you're running on the standard port for HTTPS.

@saschaludwig
Copy link

I have Sonarr running on https:// with default port 443 in a subdirectory. So basically my URL is:
https://my.hosname.tld:443/sonarr/

But that URL scheme also doesn't work.
Even the workaround from @elforesto doesn't help.

@ghost
Copy link

ghost commented Aug 11, 2022

same issue can do a curl form inside docker to my sonarr instance so it's not that it can't reach it... looks like something with the actual integration

@financelurker
Copy link

financelurker commented Aug 28, 2022

I'm having the same issues... Is this still maintained? Has anyone had success setting up that integration?
Also it's a bit annoying that the form gets cleared after each try. Can this behavior be disabled somehow?

@ppastur
Copy link

ppastur commented Sep 21, 2022

Thanks @elforesto - I was having the same issue and your workaround worked for me

@KonigSeppy
Copy link

Thankyou @elforesto! I can stop scratching my head on this now!

apo-mak added a commit to apo-mak/home-assistant.github.io that referenced this issue Nov 9, 2022
Added Note for Correct Port  ... See home-assistant/core#72372
apo-mak added a commit to apo-mak/home-assistant.github.io that referenced this issue Nov 9, 2022
Added Note for Correct Port  ... See home-assistant/core#72372
@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@saschaludwig
Copy link

The problem is still not fixed.

@dukeplc
Copy link

dukeplc commented Feb 15, 2023

Not fixed

@Ocramius
Copy link

Note: tried also configuring higher log levels:

logger:
  default: info
  logs:
    homeassistant.components.sonarr: debug
    sonarr: debug

The above produces no useful logs.

The same issue occurs with both Sonarr and Radarr.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@saschaludwig
Copy link

saschaludwig commented Jun 9, 2023

Still not fixed

@napych
Copy link

napych commented Jun 17, 2023

Both sonarr and radarr integrations fail to connect when I specify https://my.domain, but they work if I specify https://ip.

@esran
Copy link

esran commented Aug 3, 2023

I've tried all combinations of host/ip and port but they all fail and I can see nothing in the log. I'm running HA in docker and my sonarr/radarr are behind nginx.

@gvillo
Copy link

gvillo commented Sep 19, 2023

same!

@Marknel
Copy link

Marknel commented Oct 2, 2023

Same issue here.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@Ocramius
Copy link

This still applies.

@github-actions github-actions bot removed the stale label Dec 31, 2023
@kiam001
Copy link

kiam001 commented Jan 18, 2024

Still issues with connect

@kiam001
Copy link

kiam001 commented Jan 18, 2024

Works with https://domain:443/sonarr

@esran
Copy link

esran commented Jan 18, 2024

Still no luck for me. Sonarr is running in docker behind nginx, also in docker. Homeassistant is running also in docker on a different host. I can ping sonarr from the HA container. I don't seem to see any logs when trying to configure things in HA.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2024
@jamesmacwhite
Copy link

jamesmacwhite commented May 11, 2024

The docs should be updated to point out the behaviour of the URL field automatically assumes the port is 8989 as a default, this will break many setups which are using reverse proxying and there's no clear error or warning to state this.

As a few others have already said, specifying the port (even if using TCP 443) must be done like this:

https://example.com:443
https://sub.example.com:443
https://sub.example.com:443/directory

This would cover the various reverse proxy examples depending on root domain, subdomain or sub directory under a domain.

The Radarr app is the same but the URL field placeholder/default is slightly clearer with the fact it populates the URL and port syntax, the Sonarr app doesn't even provide that,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.