SABnzbd container has "lost" it's IP address

[enigmatic]

Since I originally setup YAMS, everything had been running smoothly. I initially had some issues setting up connectivity between the arr apps and SABnzbd but overcame this using the container address 172.18.0.8.

Yesterday I noticed that the SABnzbd container had stopped. I also noticed the the Portainer container now had the IP address that was previously used by SABnzbd.

I rebooted the entire YAMS config and whilst Portainer is now back up with a different IP, SABnzb no longer has an IP shown. In fact, SABnzbd is no longer showing as connected to a network.

The SABnzbd interface is available by an address on my LAN but cannot be contacted with a Portainer address so the connection is broken to all apps.

How do I get SABnzbd back to having a valid IP address within Portainer please?

[rogs]

Hey @enigmatic!

The problem here is that you are using the IPs of the internal docker network to connect between containers, which is not recommended. If you want to continue doing that, you can setup static IPs by following this stackoverflow: https://stackoverflow.com/questions/394 ... er-compose

Cheers!

Roger.

[enigmatic]

The only reason I was doing it this way is because it ended up being the only way to get a connection. I've had a post about all the issues I had with the setup previously.

I'm more than keen to have this work in a supported way but would still need to fix whatever underlying issue is present as I couldn't connect the apps to SABnzbd any other way previously

[rogs]

Try adding the static IPs as explained in the StackOverflow I added in my last response. See here: viewtopic.php?p=671#p671