this post was submitted on 22 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

502 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
1
Can't connect prowlarr to sonarr (but prowlarr to radarr is working) through gluetun (alien.top)
submitted 11 months ago by StanRex@alien.top to c/main@selfhosted.forum
2 comments fedilink hide all child comments
 

Hello dear self-hosted community,

I've been bashing my head on this for a few hours, and would like to get your opinion on this :

I'm using this docker-compose file :

https://pastebin.com/jBwauQRr

to deploy a stack of Prowlarr/Radarr/Sonarr/Gluetun/transmission, all going through NordVPN thanks to Gluetun

(I'm aware that usually, it's only recommended to make Transmission go through Gluetun, but for peace of mind, I'd rather all have the traffic be "anonymized")

​

So far, I've been able to get gluetun, prowlarr, radarr and transmission all playing along nicely.

​

However, when I tried adding sonarr, I encountered an issue.

Sonarr container is up and running, I can reach the UI on http://192.168.1.27:8989

Prowlarr, same thing on http://192.168.1.27:9696 (and connected successfully to Radarr)

​

When I try to add a Prowlarr ton Sonarr integration, I get this :

https://preview.redd.it/6e0qmpvhdsvb1.png?width=742&format=png&auto=webp&s=589d39bbeeac3dbbc0873d389402f99f637ffd00

Logs aren't super useful either

prowlarr        | 2023-10-22T16:57:40.240785339Z [Warn] ProwlarrErrorPipeline: Invalid request Validation failed: 
prowlarr        | 2023-10-22T16:57:42.373688787Z  -- BaseUrl: Unable to complete application test, cannot connect to Sonarr. Http request timed out

​

There must be something I'm not seeing, but from what I could see, the setup between Prowlarr to Radarr, and Prowlarr to Sonarr should be fairly similar, so I don't know what I'm missing.

​

Thanks in advance for your help !

​

edit : got the Prowlarr to Sonarr connection working by removing Sonarr from the gluetun network. Not how I would have wanted to solve this, but my understanding is that as long as transmission and Prowlarr are using gluetun, I should be good

you are viewing a single comment's thread
view the rest of the comments
[–] s_91@alien.top 1 points 11 months ago

You can either run all the *arr containers under Gluetun, then reference them using "sonarr:8989" and so on. Or let your containers in Gluetun access your LAN devices (in our case, access other docker containers) using: access-your-lan-through-gluetun. This way you can reference sonarr like this "machine_ip_address:8989" and so on.