-
-
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 11 in the ip forward table, restarting container to fix it... #5801
Comments
Related? #5798 Edit: Sorry, you already commented that... |
Yepp, thanks! |
Having the same problem.. When I stop the mailcow, clear all the references from the IP and IPv6 table, netfilter container will work for couple days but after a while it starts crashing again.. I did this like 5 times by now.. What is causing this please?? Thanks!
|
Having same issue on my end with this. |
Today I switched from iptables to nftables on my Debian 11 server. After configuration of related services like fail2ban and restart of Docker and Fail2Ban the issue persists. When I do an update I also get the following message: I crawled a bit through the docker-compose.yml and mailcow.conf but didn't find any option to related to the "nat" issue. |
Same issue here... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
same problem here |
Same issue for me! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This is still the problem.. why it wont be fixed? Netfilter container will always get screwed and keeps restarting.. always.. it is really annoying:
Every time have to clear it manually.. both ipv4 and ipv6 tables of all MAILCOW references.. |
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 11.9
Server/VM specifications:
32 GB DDR3-RAM, Intel Xeon E3-1245 V2 with 4 Cores and 8 Threads
Is Apparmor, SELinux or similar active?
yes, Apparmor
Virtualization technology:
Dedicated Server, no virtualization; MAILCOW is dockerized
Docker version:
26.0.0
docker-compose version or docker compose version:
v2.11.1
mailcow version:
2024-02
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:
The text was updated successfully, but these errors were encountered: