-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAILCOW target is in position 2 in the ip forward table #6241
Comments
im confused because everything i see online is saying that DOCKER-USER is ALWAYS put at # 1 in iptables, so why is mailcow asking to be # 1? it doesn't make sense to me 😵💫 |
also tried it with a new installation, so its nothing config related :/ & |
by some miracle it seems the following works - but this is definetely caused by a cached iptables configuration. 100% needs to be looked into
it may take a couple runs for it to work successfully |
having the same issue here |
Contribution guidelines
I've found a bug and checked that ...
Description
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 22.04.5 LTS
Server/VM specifications:
8 vCPU / 16GB ram
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
none
Docker version:
27.4.0
docker-compose version or docker compose version:
v2.31.0
mailcow version:
2024-11b
Reverse proxy:
apache2
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:
The text was updated successfully, but these errors were encountered: