Background:

Many years ago I wanted to transition some apps to containers. I needed a web UI that less technical household members could access to start/reboot containers. Portainer seemed like the most popular choice at the time, so I went with it. Until Arcane, all of my containers were first brought up through Portainer.

Recently I found Arcane to be a better solution. For the first time I made a compose.yaml and spun it up via the docker up command. I brought the Portainer container down while testing Arcane just in case. I like Arcane better and it was able to bring my Portainer-created containers up and down and upgrade them, so I removed the Portainer container.

Where I'm at now:

Arcane has been working as expected. I recently tried to bring up two new containers and I cannot reach them via HTTP(S), even from the server itself. Using the private IP plus port of these two new containers I get connection refused. Using the loopback and port while on the server, I get connection reset. Netstat from within the containers show they're listening on the ports.

Bringing them up via cli or within Arcane doesn't change behavior.

All my working containers are using bridge:bridge, except Arcane which is using arcane_default:bridge.

The non-working containers were using cL_default:bridge and cA_default:bridge.

I changed cA to use bridge:bridge, but it still wasn't reachable. In that state, when there's a container update, the update from Arcane fails because cA_default isn't attached to the container...but I don't see anywhere it's specified, I just see bridge:bridge.

I'm not sure what's going on. I'm surprised new containers aren't working. I assumed if something were to break, it would have been my old Portainer-created containers.

I'm attaching pics of the network inspect output of a few containers, iptables, and the Arcane network topology diagram. My firewall is PFsense, and there are no rules blocking LAN to LAN communication. Any help is appreciated.

Arcane (working - brought up via cli): Imgur

cA (not working - brought up with cli after Arcane install, changed to bridge:bridge): Imgur

cL (not working - brought up through cli after Arcane install): Imgur

cR (working - brought up through Portainer): Imgur

Arcane Network Topology: Imgur

IpTables output: Imgur