Hello, This morning, I reinstalled mailcow to a fresh install of Debian 12. I followed the instructions but I've this error and I don't understand why : `root@mail:/opt/mailcow-dockerized# docker logs 692b9c50820c Setting console permissions... Receiving anchor key... Receiving root hints... ######################################################################## 100.0% setup in directory /etc/unbound Certificate request self-signature ok subject=CN=unbound-control removing artifacts Setup success. Certificates created. Enable in unbound.conf file to use 2024-12-23 08:15:04,596 INFO Set uid to user 0 succeeded 2024-12-23 08:15:04,600 INFO supervisord started with pid 1 2024-12-23 08:15:05,603 INFO spawned: 'processes' with pid 22 2024-12-23 08:15:05,607 INFO spawned: 'syslog-ng' with pid 23 2024-12-23 08:15:05,610 INFO spawned: 'unbound' with pid 24 2024-12-23 08:15:05,612 INFO spawned: 'unbound-healthcheck' with pid 25 [1734938105] unbound[24:0] notice: init module 0: validator [1734938105] unbound[24:0] notice: init module 1: iterator Dec 23 08:15:05 692b9c50820c syslog-ng[23]: syslog-ng starting up; version='4.7.1' [1734938105] unbound[24:0] info: start of service (unbound 1.20.0). 2024-12-23 08:15:06,642 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-12-23 08:15:06,642 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-12-23 08:15:06,642 INFO success: unbound entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-12-23 08:15:06,642 INFO success: unbound-healthcheck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-12-23 08:15:13: Healthcheck: DNS Resolution Failed on attempt 1 for fuzzy.mailcow.email! Trying again... 2024-12-23 08:15:15: Healthcheck: DNS Resolution Failed on attempt 2 for fuzzy.mailcow.email! Trying again... 2024-12-23 08:15:17: Healthcheck: DNS Resolution Failed on attempt 3 for fuzzy.mailcow.email! Trying again... 2024-12-23 08:15:17: Healthcheck: DNS Resolution not possible after 3 attempts for fuzzy.mailcow.email... Gave up! 2024-12-23 08:15:19: Healthcheck: DNS Resolution Failed on attempt 1 for github.com! Trying again... [1734938121] unbound[24:0] info: generate keytag query _ta-4f66. NULL IN 2024-12-23 08:15:21: Healthcheck: DNS Resolution Failed on attempt 2 for github.com! Trying again... 2024-12-23 08:15:23: Healthcheck: DNS Resolution Failed on attempt 3 for github.com! Trying again... 2024-12-23 08:15:23: Healthcheck: DNS Resolution not possible after 3 attempts for github.com... Gave up! 2024-12-23 08:15:25: Healthcheck: DNS Resolution Failed on attempt 1 for hub.docker.com! Trying again... 2024-12-23 08:15:27: Healthcheck: DNS Resolution Failed on attempt 2 for hub.docker.com! Trying again... 2024-12-23 08:15:29: Healthcheck: DNS Resolution Failed on attempt 3 for hub.docker.com! Trying again... 2024-12-23 08:15:29: Healthcheck: DNS Resolution not possible after 3 attempts for hub.docker.com... Gave up! 2024-12-23 08:15:29: Healthcheck: Too many DNS failures (1 failures allowed, you got 3 failures), marking Healthcheck as unhealthy... 2024-12-23 08:16:07: Healthcheck: DNS Resolution Failed on attempt 1 for fuzzy.mailcow.email! Trying again... 2024-12-23 08:16:10: Healthcheck: DNS Resolution Failed on attempt 2 for fuzzy.mailcow.email! Trying again... 2024-12-23 08:16:12: Healthcheck: DNS Resolution Failed on attempt 3 for fuzzy.mailcow.email! Trying again... 2024-12-23 08:16:12: Healthcheck: DNS Resolution not possible after 3 attempts for fuzzy.mailcow.email... Gave up! 2024-12-23 08:16:14: Healthcheck: DNS Resolution Failed on attempt 1 for github.com! Trying again... 2024-12-23 08:16:16: Healthcheck: DNS Resolution Failed on attempt 2 for github.com! Trying again... 2024-12-23 08:16:18: Healthcheck: DNS Resolution Failed on attempt 3 for github.com! Trying again... 2024-12-23 08:16:18: Healthcheck: DNS Resolution not possible after 3 attempts for github.com... Gave up! 2024-12-23 08:16:20: Healthcheck: DNS Resolution Failed on attempt 1 for hub.docker.com! Trying again... 2024-12-23 08:16:22: Healthcheck: DNS Resolution Failed on attempt 2 for hub.docker.com! Trying again... 2024-12-23 08:16:24: Healthcheck: DNS Resolution Failed on attempt 3 for hub.docker.com! Trying again... 2024-12-23 08:16:24: Healthcheck: DNS Resolution not possible after 3 attempts for hub.docker.com... Gave up! 2024-12-23 08:16:24: Healthcheck: Too many DNS failures (1 failures allowed, you got 3 failures), marking Healthcheck as unhealthy...` I tested dig, ping, nslookup from the VPS and all is OK. `root@mail:/opt/mailcow-dockerized# dig fuzzy.mailcow.email ; DiG 9.18.28-1~deb12u2-Debian fuzzy.mailcow.email ;; global options: +cmd ;; Got answer: ;; ->>HEADER

Any local firewall like ufw running on the host system? selinux enabled? Please attach to the unbound container and run this command inside: `dig fuzzy.mailcow.email +trace` Paste the output here

Hello, UFW is not yet installed. Please find the output of the requested command : ` root@mail:~# dig fuzzy.mailcow.email +trace ; DiG 9.18.28-1~deb12u2-Debian fuzzy.mailcow.email +trace ;; global options: +cmd . 517669 IN NS a.root-servers.net. . 517669 IN NS b.root-servers.net. . 517669 IN NS c.root-servers.net. . 517669 IN NS d.root-servers.net. . 517669 IN NS e.root-servers.net. . 517669 IN NS f.root-servers.net. . 517669 IN NS g.root-servers.net. . 517669 IN NS h.root-servers.net. . 517669 IN NS i.root-servers.net. . 517669 IN NS j.root-servers.net. . 517669 IN NS k.root-servers.net. . 517669 IN NS l.root-servers.net. . 517669 IN NS m.root-servers.net. . 517669 IN RRSIG NS 8 0 518400 20250105050000 20241223040000 61050 . tvqBg3Mx6vpVH+W5lS9TZjLy2OuIwXrns4kAS6YtB1AeI2nIc2kVeLav CGw0TEIMyvG/ZWh3o+u3CVSgTPlTsU8xkWKwVtiZwNvZKFCNZkNmL/QC 3I23d/3upWchQ1xdAe3/Dl3VpdgwQr8bhdkAdiY2QBx22FR8oz0ccG4v whtBoxpMVXciHmKnFfzE1S6CXYs54s6baMsXY+G+Sd7npRGitLhIiwtp FtpT6vlztSkrfA99CvOoVLO67aIR9wfRrVFecVQM6KxdHcfU7mmM+rWD u0eUdefnpQNolZ8WAs7S86U5u9BtzjVBs6iRyjDfomSAWxD7ica+Rekv AVZZjQ== ;; Received 525 bytes from 1.1.1.1#53(1.1.1.1) in 2 ms ;; communications error to 192.112.36.4#53: timed out ;; communications error to 192.112.36.4#53: timed out ;; communications error to 192.112.36.4#53: timed out ;; communications error to 170.247.170.2#53: timed out ;; UDP setup with 2001:dc3::35#53(2001:dc3::35) for fuzzy.mailcow.email failed: network unreachable. ;; UDP setup with 2801:1b8:10::b#53(2801:1b8:10::b) for fuzzy.mailcow.email failed: network unreachable. ;; communications error to 192.5.5.241#53: timed out ;; UDP setup with 2001:500:2::c#53(2001:500:2::c) for fuzzy.mailcow.email failed: network unreachable. ;; communications error to 198.97.190.53#53: timed out ;; communications error to 192.33.4.12#53: timed out ;; UDP setup with 2001:500:12::d0d#53(2001:500:12::d0d) for fuzzy.mailcow.email failed: network unreachable. ;; communications error to 192.36.148.17#53: timed out ;; communications error to 202.12.27.33#53: timed out ;; communications error to 198.41.0.4#53: timed out ;; UDP setup with 2001:7fe::53#53(2001:7fe::53) for fuzzy.mailcow.email failed: network unreachable. ;; UDP setup with 2001:500:1::53#53(2001:500:1::53) for fuzzy.mailcow.email failed: network unreachable. ;; communications error to 199.7.91.13#53: timed out ;; communications error to 192.203.230.10#53: timed out ;; UDP setup with 2001:7fd::1#53(2001:7fd::1) for fuzzy.mailcow.email failed: network unreachable. ;; communications error to 199.7.83.42#53: timed out ;; UDP setup with 2001:500:a8::e#53(2001:500:a8::e) for fuzzy.mailcow.email failed: network unreachable. email. 172800 IN NS v0n0.nic.email. email. 172800 IN NS v0n1.nic.email. email. 172800 IN NS v0n2.nic.email. email. 172800 IN NS v0n3.nic.email. email. 172800 IN NS v2n0.nic.email. email. 172800 IN NS v2n1.nic.email. email. 86400 IN DS 62422 8 2 92A9DA686674B9BC30EE72224130A7C761D5B01902DA9A5A62038C79 6A16BD33 email. 86400 IN RRSIG DS 8 1 86400 20250105050000 20241223040000 61050 . INAuq9MtxqYVd9ROZR6/SksqpH7HaHWxkePbIGlvdkDRTrMGss/ykhIK BukgaRjRonxrnyZMtDRHx5cc6LTq59jaIrxM2dqVlQMH1+Eua84widot fAV+xxqCPlhhELMbV+TVL/19CMiRITqLr2v4OfgTsvfF8Y99uXS5unfb lw6W1DZigUnkFwZSKOxDnBt9w1Voln5QLyQ69ozmsphYWdeHWW9hKwgR 5eynBTkbdPd9i6s5CupRWqU3A3BV5jiGMwvUMYmRyV4jOE+ntdI5GmrS q22UqSHJCwxbGhGV3ZHsjRch3tB9mCkc5k0Fkf7IFnIsGLqKaSnbKW22 V2ry1A== ;; Received 765 bytes from 192.58.128.30#53(j.root-servers.net) in 11 ms ;; UDP setup with 2a01:8840:f6::35#53(2a01:8840:f6::35) for fuzzy.mailcow.email failed: network unreachable. ;; UDP setup with 2a01:8840:1d::35#53(2a01:8840:1d::35) for fuzzy.mailcow.email failed: network unreachable. mailcow.email. 3600 IN NS angus.ns.servercow.de. mailcow.email. 3600 IN NS dexter.ns.servercow.net. mailcow.email. 3600 IN NS galloway.ns.servercow.com. mailcow.email. 3600 IN DS 41879 13 2 7427B02EF2AB136E84740A14D3D2F7CC84AB821D55AB0EFEFCF4B950 4DC55FC6 mailcow.email. 3600 IN RRSIG DS 8 2 3600 20250107153947 20241217143947 37680 email. ZMi58/JjWDIS+v8C3plTlSwhr/Xw++Z/HDf7TLhNJFYglfid0hJ/hY7V 498ZOk5rKeOmm8TohmYhZawOFBsFf3RQ/fxBh2qARWo9TUMaLG6xBDHB wgkTdkN2AwvMzOqP4WkVfizwQeGEBsOrNYHTLDZSoLAz6wcgAVbJ6Ykj RuE= ;; Received 372 bytes from 161.232.12.35#53(v0n3.nic.email) in 1 ms fuzzy.mailcow.email. 64800 IN A 95.217.129.125 fuzzy.mailcow.email. 64800 IN RRSIG A 13 3 64800 20250102000000 20241212000000 41879 mailcow.email. +BRhFGOmb92ZW4LuTRDwwmrZ2RDWcMzqCLMLhvZEJYVOTIz5SoZehjA5 AzF/qr2iXQmGk1ZdMVUll+yVCWy4uw== ;; Received 173 bytes from 45.85.48.12#53(dexter.ns.servercow.net) in 16 ms ` Thanks for your help. Christophe

I asked you to do this from inside the unbound container `docker exec mailcowdockerized-unbound-mailcow-1 dig fuzzy.mailcow.email +trace` It seems you have IPv6 problems even from the host system And IPv4 gets blocked somehow ```ghhhhh ;; communications error to 198.97.190.53#53: timed out ;; communications error to 192.33.4.12#53: timed out ```

Here's the result : `root@mail:~# docker exec mailcowdockerized-unbound-mailcow-1 dig fuzzy.mailcow.email +trace ; DiG 9.18.27 fuzzy.mailcow.email +trace ;; global options: +cmd . 512949 IN NS a.root-servers.net. . 512949 IN NS b.root-servers.net. . 512949 IN NS c.root-servers.net. . 512949 IN NS d.root-servers.net. . 512949 IN NS e.root-servers.net. . 512949 IN NS f.root-servers.net. . 512949 IN NS g.root-servers.net. . 512949 IN NS h.root-servers.net. . 512949 IN NS i.root-servers.net. . 512949 IN NS j.root-servers.net. . 512949 IN NS k.root-servers.net. . 512949 IN NS l.root-servers.net. . 512949 IN NS m.root-servers.net. . 512949 IN RRSIG NS 8 0 518400 20250105050000 20241223040000 61050 . tvqBg3Mx6vpVH+W5lS9TZjLy2OuIwXrns4kAS6YtB1AeI2nIc2kVeLav CGw0TEIMyvG/ZWh3o+u3CVSgTPlTsU8xkWKwVtiZwNvZKFCNZkNmL/QC 3I23d/3upWchQ1xdAe3/Dl3VpdgwQr8bhdkAdiY2QBx22FR8oz0ccG4v whtBoxpMVXciHmKnFfzE1S6CXYs54s6baMsXY+G+Sd7npRGitLhIiwtp FtpT6vlztSkrfA99CvOoVLO67aIR9wfRrVFecVQM6KxdHcfU7mmM+rWD u0eUdefnpQNolZ8WAs7S86U5u9BtzjVBs6iRyjDfomSAWxD7ica+Rekv AVZZjQ== ;; Received 525 bytes from 127.0.0.11#53(127.0.0.11) in 2 ms ;; communications error to 192.203.230.10#53: timed out ;; communications error to 192.203.230.10#53: timed out ;; communications error to 192.203.230.10#53: timed out ;; communications error to 2001:500:2d::d#53: timed out ;; communications error to 199.7.91.13#53: timed out ;; communications error to 2001:500:2::c#53: timed out ;; communications error to 2001:500:a8::e#53: timed out ;; communications error to 170.247.170.2#53: timed out ;; communications error to 192.112.36.4#53: timed out ;; communications error to 2001:dc3::35#53: timed out ;; communications error to 193.0.14.129#53: timed out ;; communications error to 192.5.5.241#53: timed out ;; communications error to 2801:1b8:10::b#53: timed out ;; communications error to 2001:7fd::1#53: timed out ;; communications error to 2001:500:12::d0d#53: timed out ;; communications error to 198.97.190.53#53: timed out ;; communications error to 2001:503:c27::2:30#53: timed out ;; communications error to 199.7.83.42#53: timed out ;; communications error to 192.33.4.12#53: timed out ;; communications error to 2001:503:ba3e::2:30#53: timed out ;; communications error to 2001:500:2f::f#53: timed out ;; communications error to 202.12.27.33#53: timed out ;; communications error to 192.36.148.17#53: timed out ;; communications error to 198.41.0.4#53: timed out ;; communications error to 2001:500:9f::42#53: timed out email. 172800 IN NS v0n0.nic.email. email. 172800 IN NS v0n1.nic.email. email. 172800 IN NS v0n2.nic.email. email. 172800 IN NS v0n3.nic.email. email. 172800 IN NS v2n0.nic.email. email. 172800 IN NS v2n1.nic.email. email. 86400 IN DS 62422 8 2 92A9DA686674B9BC30EE72224130A7C761D5B01902DA9A5A62038C79 6A16BD33 email. 86400 IN RRSIG DS 8 1 86400 20250105050000 20241223040000 61050 . INAuq9MtxqYVd9ROZR6/SksqpH7HaHWxkePbIGlvdkDRTrMGss/ykhIK BukgaRjRonxrnyZMtDRHx5cc6LTq59jaIrxM2dqVlQMH1+Eua84widot fAV+xxqCPlhhELMbV+TVL/19CMiRITqLr2v4OfgTsvfF8Y99uXS5unfb lw6W1DZigUnkFwZSKOxDnBt9w1Voln5QLyQ69ozmsphYWdeHWW9hKwgR 5eynBTkbdPd9i6s5CupRWqU3A3BV5jiGMwvUMYmRyV4jOE+ntdI5GmrS q22UqSHJCwxbGhGV3ZHsjRch3tB9mCkc5k0Fkf7IFnIsGLqKaSnbKW22 V2ry1A== ;; Received 765 bytes from 192.58.128.30#53(j.root-servers.net) in 10 ms mailcow.email. 3600 IN NS galloway.ns.servercow.com. mailcow.email. 3600 IN NS dexter.ns.servercow.net. mailcow.email. 3600 IN NS angus.ns.servercow.de. mailcow.email. 3600 IN DS 41879 13 2 7427B02EF2AB136E84740A14D3D2F7CC84AB821D55AB0EFEFCF4B950 4DC55FC6 mailcow.email. 3600 IN RRSIG DS 8 2 3600 20250107153947 20241217143947 37680 email. ZMi58/JjWDIS+v8C3plTlSwhr/Xw++Z/HDf7TLhNJFYglfid0hJ/hY7V 498ZOk5rKeOmm8TohmYhZawOFBsFf3RQ/fxBh2qARWo9TUMaLG6xBDHB wgkTdkN2AwvMzOqP4WkVfizwQeGEBsOrNYHTLDZSoLAz6wcgAVbJ6Ykj RuE= ;; Received 372 bytes from 161.232.13.35#53(v2n1.nic.email) in 1 ms fuzzy.mailcow.email. 64800 IN RRSIG A 13 3 64800 20250102000000 20241212000000 41879 mailcow.email. tUKkde0E0g+kY59RNfukXI4rIFUbNKfxJ3H8STmU+4h2MsGaQ6GMCclz 6QYVUp1ruXi4WzeEw6tfHO1dE+QlmA== fuzzy.mailcow.email. 64800 IN A 95.217.129.125 ;; Received 173 bytes from 94.130.42.192#53(galloway.ns.servercow.com) in 16 ms `

> @"crahier"#p20878 ;; communications error to 192.203.230.10#53: timed out > ;; communications error to 192.203.230.10#53: timed out > ;; communications error to 192.203.230.10#53: timed out > ;; communications error to 2001:500:2d::d#53: timed out > ;; communications error to 199.7.91.13#53: timed out > ;; communications error to 2001:500:2::c#53: timed out > ;; communications error to 2001:500:a8::e#53: timed out > ;; communications error to 170.247.170.2#53: timed out > ;; communications error to 192.112.36.4#53: timed out > ;; communications error to 2001:dc3::35#53: timed out > ;; communications error to 193.0.14.129#53: timed out > ;; communications error to 192.5.5.241#53: timed out > ;; communications error to 2801:1b8:10::b#53: timed out > ;; communications error to 2001:7fd::1#53: timed out > ;; communications error to 2001:500:12::d0d#53: timed out > ;; communications error to 198.97.190.53#53: timed out > ;; communications error to 2001:503:c27::2:30#53: timed out > ;; communications error to 199.7.83.42#53: timed out > ;; communications error to 192.33.4.12#53: timed out > ;; communications error to 2001:503:ba3e::2:30#53: timed out > ;; communications error to 2001:500:2f::f#53: timed out > ;; communications error to 202.12.27.33#53: timed out > ;; communications error to 192.36.148.17#53: timed out > ;; communications error to 198.41.0.4#53: timed out > ;; communications error to 2001:500:9f::42#53: timed out Hmm, you're sure there is no other firewall involved?

And which docker did you install? The one from Debian repositories, or the one from the Docker repositories (as suggested by the installation docs)?

@"DocFraggle"#p20879 Here're the services installed : `root@mail:~# service --status-all [ - ] apache-htcacheclean [ - ] apache2 [ - ] apparmor [ - ] bind9 [ - ] bootlogs [ - ] bootmisc.sh [ - ] brightness [ - ] checkfs.sh [ - ] checkroot-bootclean.sh [ - ] checkroot.sh [ + ] cron [ + ] dbus [ + ] docker [ - ] exim4 [ - ] fetchmail [ - ] hostname.sh [ - ] hwclock.sh [ - ] killprocs [ + ] kmod [ ? ] modules_dep.sh [ ? ] mount-configfs [ - ] mountall-bootclean.sh [ - ] mountall.sh [ - ] mountdevsubfs.sh [ - ] mountkernfs.sh [ - ] mountnfs-bootclean.sh [ - ] mountnfs.sh [ - ] named [ - ] networking [ + ] procps [ - ] quota [ - ] quotarpc [ - ] rc.local [ + ] resolvconf [ - ] rmnologin [ - ] rpcbind [ - ] rsync [ - ] saslauthd [ - ] screen-cleanup [ - ] sendsigs [ + ] ssh [ - ] sudo [ + ] udev [ - ] umountfs [ - ] umountnfs.sh [ - ] umountroot [ - ] urandom [ - ] uuidd [ - ] wide-dhcpv6-client [ + ] xinetd ` @"[unknown]"#p20880 I followed the instructions https://docs.mailcow.email/getstarted/prerequisite-system/ The installed versions : ` root@mail:~# docker version Client: Docker Engine - Community Version: 27.4.1 API version: 1.47 Go version: go1.22.10 Git commit: b9d17ea Built: Tue Dec 17 15:45:56 2024 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 27.4.1 API version: 1.47 (minimum version 1.24) Go version: go1.22.10 Git commit: c710b88 Built: Tue Dec 17 15:45:56 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.7.24 GitCommit: 88bf19b2105c8b17560993bee28a01ddc2f97182 runc: Version: 1.2.2 GitCommit: v1.2.2-0-g7cb3632 docker-init: Version: 0.19.0 GitCommit: de40ad0 root@mail:~# docker-compose version Docker Compose version v2.32.1` @"[unknown]"#p20880 I followed the instructions https://docs.mailcow.email/getstarted/prerequisite-system/ The installed versions : ` root@mail:~# docker version Client: Docker Engine - Community Version: 27.4.1 API version: 1.47 Go version: go1.22.10 Git commit: b9d17ea Built: Tue Dec 17 15:45:56 2024 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 27.4.1 API version: 1.47 (minimum version 1.24) Go version: go1.22.10 Git commit: c710b88 Built: Tue Dec 17 15:45:56 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.7.24 GitCommit: 88bf19b2105c8b17560993bee28a01ddc2f97182 runc: Version: 1.2.2 GitCommit: v1.2.2-0-g7cb3632 docker-init: Version: 0.19.0 GitCommit: de40ad0 root@mail:~# docker-compose version Docker Compose version v2.32.1`

Please post the output of `iptables -nL` and `iptables -t nat -nL` Are you using `docker-compose ` or `docker compose` (mind the blank between docker and compose) to run commands on your stack?

@"DocFraggle"#p20884 Here're the results : ` root@mail:~# iptables -nL Chain INPUT (policy ACCEPT) target prot opt source destination MAILCOW 0 -- 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy ACCEPT) target prot opt source destination MAILCOW 0 -- 0.0.0.0/0 0.0.0.0/0 DOCKER-USER 0 -- 0.0.0.0/0 0.0.0.0/0 DOCKER-ISOLATION-STAGE-1 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED DOCKER 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED DOCKER 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain DOCKER (2 references) target prot opt source destination ACCEPT 6 -- 0.0.0.0/0 172.22.1.3 tcp dpt:3306 ACCEPT 6 -- 0.0.0.0/0 172.22.1.5 tcp dpt:8983 ACCEPT 6 -- 0.0.0.0/0 172.22.1.249 tcp dpt:6379 ACCEPT 6 -- 0.0.0.0/0 172.22.1.250 tcp dpt:110 ACCEPT 6 -- 0.0.0.0/0 172.22.1.250 tcp dpt:143 ACCEPT 6 -- 0.0.0.0/0 172.22.1.250 tcp dpt:993 ACCEPT 6 -- 0.0.0.0/0 172.22.1.250 tcp dpt:995 ACCEPT 6 -- 0.0.0.0/0 172.22.1.250 tcp dpt:4190 ACCEPT 6 -- 0.0.0.0/0 172.22.1.250 tcp dpt:12345 Chain DOCKER-ISOLATION-STAGE-1 (1 references) target prot opt source destination DOCKER-ISOLATION-STAGE-2 0 -- 0.0.0.0/0 0.0.0.0/0 DOCKER-ISOLATION-STAGE-2 0 -- 0.0.0.0/0 0.0.0.0/0 RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-ISOLATION-STAGE-2 (2 references) target prot opt source destination DROP 0 -- 0.0.0.0/0 0.0.0.0/0 DROP 0 -- 0.0.0.0/0 0.0.0.0/0 RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-USER (1 references) target prot opt source destination RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 Chain MAILCOW (2 references) target prot opt source destination DROP 6 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 3306,6379,8983,12345 ` the other one : ` root@mail:~# iptables -t nat -nL Chain PREROUTING (policy ACCEPT) target prot opt source destination DOCKER 0 -- 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type LOCAL Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination DOCKER 0 -- 0.0.0.0/0 !127.0.0.0/8 ADDRTYPE match dst-type LOCAL Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE 0 -- 172.17.0.0/16 0.0.0.0/0 MASQUERADE 0 -- 172.22.1.0/24 0.0.0.0/0 MASQUERADE 6 -- 172.22.1.3 172.22.1.3 tcp dpt:3306 MASQUERADE 6 -- 172.22.1.5 172.22.1.5 tcp dpt:8983 MASQUERADE 6 -- 172.22.1.249 172.22.1.249 tcp dpt:6379 MASQUERADE 6 -- 172.22.1.250 172.22.1.250 tcp dpt:110 MASQUERADE 6 -- 172.22.1.250 172.22.1.250 tcp dpt:143 MASQUERADE 6 -- 172.22.1.250 172.22.1.250 tcp dpt:993 MASQUERADE 6 -- 172.22.1.250 172.22.1.250 tcp dpt:995 MASQUERADE 6 -- 172.22.1.250 172.22.1.250 tcp dpt:4190 MASQUERADE 6 -- 172.22.1.250 172.22.1.250 tcp dpt:12345 Chain DOCKER (2 references) target prot opt source destination RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 DNAT 6 -- 0.0.0.0/0 127.0.0.1 tcp dpt:13306 to:172.22.1.3:3306 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 127.0.0.1 tcp dpt:18983 to:172.22.1.5:8983 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 127.0.0.1 tcp dpt:7654 to:172.22.1.249:6379 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 to:172.22.1.250:110 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:143 to:172.22.1.250:143 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:993 to:172.22.1.250:993 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 to:172.22.1.250:995 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:4190 to:172.22.1.250:4190 Warning: Extension DNAT is not supported, missing kernel module? DNAT 6 -- 0.0.0.0/0 127.0.0.1 tcp dpt:19991 to:172.22.1.250:12345 ` I launched mailcow via `docker-compose up -d`

Please use `docker compose` without - Restart your stack ``` docker compose down docker compose up -d ``` The error for DNAT is strange

mailcow community

Loading...

Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error.

Debian 12 - Problem with unbound

« Previous Page