You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 😵💫
by some miracle it seems the following works - but this is definetely caused by a cached iptables configuration. 100% needs to be looked into
docker compose down
service docker stop
sudo ip6tables -X
sudo ip6tables -F
sudo ip6tables -X
sudo iptables -F
sudo iptables -X
service docker start
sudo ip6tables -L --line-numbers # just to make sure that the tables are clear
sudo iptables -L --line-numbers # same as above
docker compose up -d
it may take a couple runs for it to work successfully
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: