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 :
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 :
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 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.
Yes I have also encountered that problem I have just put radarr sonarr lidarr readarr and everything else I’m behind gluetun