antonio3427 Posted May 6, 2021 Posted May 6, 2021 I am having issues with a number of dockers showing refused to connect: Below are the dockers I have so far: Plex, NZBgetm and radarr have no issues. Lidarr and Sonarr refuse to connect I am running a bond interface: I have deleted the dockers, deleted their folders in my appdata folder and re-installed unraid-diagnostics-20210506-1031.zip Quote
loungelizard Posted May 28, 2021 Posted May 28, 2021 All I can say is, I'm having the exact same problem. Plex, Radarr etc. working fine, sonarr won't be able to connect even though it's started. Setting is exactly matching the radarr setting.... Any ideas? Quote
Merlryn Posted May 29, 2021 Posted May 29, 2021 I actually have the same issue that I can't figure out. My issue is that my containers can't see each other that are exposed through the Unraid/Docker host and port. So Sonarr/Radarr can't see SabNZB for example. If I try to connect to SabNZB from another host on the network, it does pickup. Also if I use the internal docker ip (172.17.0.x) it does work fine. I've tried turning on "Host access to custom networks". I've also completely reinstalled the containers with no change. I even just used all the defaults with no data import just to make sure it wasn't my data or setup. If I shell into the container it can ping the host just fine. For fun I installed InFluxDB and Telegraf and I can't get telegraf to send info to InFluxDB at all. However other hosts on the network can send data to InfluxDB just fine. I'm pretty sure this broke somewhere around 6.9 upgrade but I got it fixed with the internal docker ip and forgot about it. I haven't really looked at it until I found the issue with Telegraf<>InfluxDB. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.