Connection errors

[Woodymakespizza]

Hey all, have been reading recently and after seeing a great many "I didnt know what I was missing until I got Huntarr" I decided to give it a go. I have an Asustor NAS with Sonarr, Radarr, and Lidarr that I use to feed my plex server. Those were all installed directly from the Asustor app store, but Huntarr was not in there, so I used portainer. I got Huntarr up and running, but it is giving me connection errors no matter what I put for the URL for any of them. I have tried the NAS IP, which is the same IPs I use to access the Arrs, Ive tried host/(arr)/port, really everything I can think of to no avail. Any suggestions would be appreciated.

[sleighton]

Check for port conflicts

1. Find the used ports: Log into your ASUSTOR ADM and go to App Central.
2. Open the settings for Radarr and Sonarr and note the ports they are running on. The defaults are typically 8989 for Sonarr and 7878 for Radarr, but ASUSTOR's installer may have assigned different ones.

Verify bridge network

In Portainer, check if the Huntarr container is attached to a standard bridge network. ASUSTOR can create its own network interfaces, and if containers aren't on the same network, they can't communicate.

[Woodymakespizza]

Ports are the correct default ports. They werent on the bridge, but I connected them and stopped then restarted all services, still no-go.

[sleighton]

@Woodymakespizza But are the arrs on the bridge? Huntarr and the arrs must be accessible to each other over a network, so either they all are on the bridge or they all have to be on the same network or they can't talk to each other.

[Woodymakespizza]

The arrs were not on the bridge before. I went into portainer and connected each of them, restarted all four services, still got a connection error. I restarted the whole system and confirmed all were connected to the bridge, tried again, same error.

[sleighton]

@Woodymakespizza Interesting posts here that discuss the docker networking issues with Asustor. You might find some useful configuration points. Looks like Asustor has beefed up security with respect to docker containers and you may HAVE TO have the containers on the same docker network to get them to communicate with each other, which implies bridge is not the answer.

https://www.reddit.com/r/asustor/comments/1o8l5x3/adm_release_510rmg1_broke_my_sonarradarrprowlarr/

[Woodymakespizza]

Appears to be solved. Im not sure what did it. I created a vlan and then the bridge net addresses worked. Thank you Sleighton.

[sleighton]

Glad to hear you got it solved!