New User: Hostname/IP info for apps besides Plex

[TheMarf]

Hi All, just learned about this and installing via CA on Unraid. I was able to connect to Plex just fine but when trying to connect to Overseerr/Radarr/Sonarr I am unable to connect.

For example for Overseerr I put in the local ip (same as plex), port, and API key. I'm wondering if there is something I'm missing. I've tried making sure all dockers are on the same custom network etc. I'm sure it's an easy mistake that I've made but I cannot figure it out.

Sonarr/Radarr have a fourth field called Base URL....I didn't see those referenced in the guides about what goes in those fields.

[jorenn92]

Hey, base url should be empty unless you also have base url configured in Sonarr/Radarr.

Could you share a screenshot of your configuration?

[TheMarf]

Hi @jorenn92. Sorry for the delayed response. Was working on another server issue the past couple days.

I saw your message to the other user and enabled debug logging in radarr and I think I have something to share. I'm very novice when it comes to docker/logs etc.

Docker container settings to display ports

[TheMarf]

As a follow up. Since the logs looked okay I saved the connections anyways. And then when I test it shows success? So not sure what's correct.

[jorenn92]

Hey, no problem! The test button only tests the currently saved connection details. So if you make changes, always save first before testing.

Am i correct in understanding that it works now?

[TheMarf]

Yup. Seems to be working now. Thanks for the help.

My only feedback would be to clarify that in the documentation.

[jorenn92]

No problem, happy you got it working!
I’ll check if i can make it clearer in the docs.

[anorth2]

+1 Am running images on a docker network. All other containers (overseer, radarr, sonarr) can connect to each other via localhost. Maintainerr logs show "Couldn't fetch Radarr info.. Is Radarr up?" (and same message for Sonarr). It shows no log, but also errors on Overseerr.

[jorenn92]

Yeah, i should really work on a debug log level & throw the error messages for issues like this.

Can you curl/ping the other services when you exec into the maintainerr container? If that works, Maintainerr should also be able to reach the others.

[anorth2]

Yeah, I was able to exec "wget localhost:7878" and get a 401 unauthorized, so the containers are definitely reachable. Something is just going on with the axios request

/opt # wget localhost:7878
Connecting to localhost:7878 (127.0.0.1:7878)
wget: server returned error: HTTP/1.1 401 Unauthorized

[jorenn92]

Could you try to enable debug logging in Radarr or Sonarr & do the Maintainerr test a few times? Are there records in the *arr log?

A successful record should look something like this. You won't get a response 200, but at least we'll know if Maintainerr can reach the other services.
2024-01-05 11:06:26.2|Debug|Api|[GET] /api/v3/system/status?apikey=(removed) 200.OK (2 ms)

[anorth2]

@jorenn92 FYI I realized my issue was user error. I expected "Test" to behave like it does in the other arr apps and sabnzbd where it tests the credentials in the login field rather than the "saved" credentials. After saving and the hitting test it started working.

If I have time I may start opening some pull requests to make improvements around logging and other areas.

[jorenn92]

Okay, thanks for letting me know!

I added a basic debug log level in the latest release. For now, it’ll just show the exact error messages when something goes wrong.

This is activated by adding DEBUG=true to your docker environment variables.