Closed ro78 closed 5 months ago
Does it work if you set DISABLE_NETFILTER_ISOLATION_RULE=y
in mailcow.conf and do a docker compose up -d
?
I just did a docker compose down && docker compose up -d, and it's OK for the moment.
02/02/2024 16:40:30 Dovecot replication 0 Health level: 100% (20/20)
That will return. Can reproduce it on my side as well. Fix is on the way for this.
Updated after https://github.com/mailcow/mailcow-dockerized/pull/5699, for the moment no problem.
Does it work if you set
DISABLE_NETFILTER_ISOLATION_RULE=y
in mailcow.conf and do adocker compose up -d
?
I tried this, docker compose down and up again, unfortunately the issue came back shortly after
Fixed on 2024-01d.
Should we be setting DISABLE_NETFILTER_ISOLATION_RULE to n with this fix? I did this and I am getting broken replication again even with the fix in #5699
Should not make a difference. But you might be affected by: https://github.com/mailcow/mailcow-dockerized/issues/5697 which will be available in a few minutes.
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12
Server/VM specifications:
12 cores, 32 GB of RAM
Is Apparmor, SELinux or similar active?
No
Virtualization technology:
Baremetal
Docker version:
25.0.1
docker-compose version or docker compose version:
v2.24.2
mailcow version:
2024-01c
Reverse proxy:
Apache
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: