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

❓ [Overseerr & Radarr] Connecting overseerr to radarr #1782

Open
Wazbat opened this issue Feb 22, 2025 · 3 comments
Open

❓ [Overseerr & Radarr] Connecting overseerr to radarr #1782

Wazbat opened this issue Feb 22, 2025 · 3 comments
Labels
prevent stale Prevents stale being applied

Comments

@Wazbat
Copy link

Wazbat commented Feb 22, 2025

Which addon?

Overseerr & Radarr


I absolutely love these addons, and I really appreciate the work and effort that goes into maintaining them. I've set up Overseerr on my local, as well as as Radarr, however I'm unable to get the two to connect to eachother via local addresses and I'm not sure what I'm doing wrong.

I've tried various different IPs in Overseerr, such as localhost or 127.0.0.1, however the log continues to show me errors.

[error][Radarr]: [Radarr] Failed to retrieve profiles: connect ECONNREFUSED ::1:7878 

I also have issues connecting Radarr to qBittorrent, that's also running on the same HA server

However, it does all seem to work if I use the device hostname, homeassistant.local. Radarr connects to qBittorrent, and Overseerr connects to Radarr. However I'm not sure if this the correct way to do it as I cannot find much information about this setup

@Wazbat Wazbat added the prevent stale Prevents stale being applied label Feb 22, 2025
@alexbelgium
Copy link
Owner

Hi, in theory the only thing that would work is to use the local ip (such as 192.168.178.12) while making sure ports are open for each addon

@Wazbat
Copy link
Author

Wazbat commented Feb 24, 2025

Is that the case? Other addons from my experience typically either use the local machine IP, or in the case of frigate, you're suppose to use the home assistant container name ccab4aaf-frigate as the hostname which uses the internal docker network

https://docs.frigate.video/configuration/#vscode-configuration-schema

@Wazbat
Copy link
Author

Wazbat commented Feb 26, 2025

Ah, I answered my own questions above yeah. You can use the internal docker container name, so then it doesn't even have to leave the docker network

Image

Image

Image

This also works in prowlarr

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prevent stale Prevents stale being applied
Projects
None yet
Development

No branches or pull requests

2 participants