You are not the only one with this problem. Your domains probably have an IPv6 record?
@Adam says:
"[...] it's because the ipv6 addresses are routed via the Docker proxy rather than NAT [...]"
This should be fixed with an update in the future. According to Adam, a workaround would be the following (test at your own risk):
docker ps -a | grep -v CONTAINER | awk '{print $1}' | xargs -i docker network disconnect enhance-network {}
docker network rm enhance-network
docker network create --ipv6 enhance-network --subnet fd76:cd8e:5f::/48 --subnet 199.99.88.0/23
docker ps -a | grep -v CONTAINER | awk '{print $1}' | xargs -i docker network connect enhance-network {}
systemctl restart docker
In /etc/docker/daemon.json add:
{
"experimental": true,
"ip6tables": true
}
I haven't had a chance to test it myself yet. So I can't say whether the workaround works.
My customers and I had the problem that the security plugin Solid Security was constantly blocking the container IPs and thus the websites were no longer accessible to anyone. After Adam's tip, we then whitelisted the container IPs 199.99.88.0/23 in the plugin settings. It's not a satisfying solution, but it works for now.
I'm also testing cPGuard on some servers at the moment and I keep seeing the container IP 199.99.88.1 in the WAF logs.
