Unable to obtain certificate on new installation

smares

I just set up mailcow on a VPS by Contabo running Debian 12.2. I have two IPv4 addresses. On one IP, I have Traefik running and some websites of friends (behind Traefik), and the other IP should be used for everything related to e-mail. The changes I did to the mailcow.conf are the following:

Change HTTP_BIND and HTTPS_BIND to the second IPv4 address.
Change SMTP_PORT, SMTPS_PORT, SUBMISSION_PORT, IMAP_PORT, IMAPS_PORT, POP_PORT, POPS_PORT and SIEVE_PORT to use the second IPv4 address (followed by the port number).
Change IPV4_NETWORK to 172.35.1 since I was getting an “ERROR: Pool overlaps with other one on this address space” error.
Change SNAT_TO_SOURCE to the second IPv4 address.

After starting mailcow, I get the following errors in the acme container:

Detecting IP addresses…
OK: , 0000:0000:0000:0000:0000:0000:0000:0000
No A or AAAA record found for hostname mail.smares.it
Cannot validate any hostnames, skipping Let’s Encrypt for 1 hour.

What am I missing? 😅

smares

I just followed the documentation on disabling IPv6 but the output is identical.

esackbauer

It seems to be an issue with Contabo, this user is having the same problem:
https://community.mailcow.email/d/2968
Maybe you two should talk to each. The other user tries to contact Contabo.

superviiv

@smares are you using debian? if yes could you post the contents of your
/etc/netplan/01-netcfg.yaml

smares

superviiv I don’t have Netplan and therefore no config for it.

smares

But this is /etc/network/interfaces:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 62.171.134.xxx
    network 62.171.128.0
    gateway 62.171.128.1
    broadcast 62.171.159.255
    netmask 255.255.224.0
    dns-search invalid
    dns-nameservers 213.136.95.10 213.136.95.11

iface eth0 inet static
    address 62.171.134.xxx/32

iface eth0 inet6 static
    address 2a02:c207:3004:xxxx::1
    netmask 64
    gateway fe80::1
    accept_ra 0
    autoconf 0
    privext 0
    dns-search invalid
    dns-nameservers 2a02:c207::1:53 2a02:c207::2:53

smares

If I run a shell in the acme container, I can ping 8.8.8.8, I cannot ping6 2001:4860:4860::8888 (ping6: sendto: Address not available), I cannot ping google.com (ping: bad address ‘google.com’) and I cannot host google.com (Host google.com not found: 2(SERVFAIL)).

ifconfig:

eth0      Link encap:Ethernet  HWaddr 02:42:AC:23:01:0C
          inet addr:172.35.1.12  Bcast:172.35.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8369 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7101 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:591478 (577.6 KiB)  TX bytes:577622 (564.0 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:7173 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7173 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:443443 (433.0 KiB)  TX bytes:443443 (433.0 KiB)

resolv.conf:

search invalid
nameserver 127.0.0.11
options ndots:0

(These are in the acme container)

smares

It seems to be a DNS issue. And not sure if related, but the unbound container restarts every few minutes, so does postfix and dovecot.

In the dovecot logs, I have lots of curl: (6) Could not resolve host: www.spamassassin.heinlein-support.de errors.
In the postfix logs, I have:

Checking if ASN for your IP is listed for Spamhaus Bad ASN List...
We couldn't determine your AS... (maybe DNS/Network issue?) Response Code: 000
Deactivating Spamhaus DNS Blocklists to be on the safe site!

And here is a lifecycle:

mailcowdockerized-postfix-mailcow-1  | Nov 18 13:02:30 8c3641250d23 postfix/postfix-script[344]: starting the Postfix mail system
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:02:30 8c3641250d23 postfix/master[346]: daemon started -- version 3.5.18, configuration /opt/postfix/conf
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:03:03 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 355 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:03:03 8c3641250d23 postfix/master[346]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:03:03 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 352 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:04:56 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 363 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:04:56 8c3641250d23 postfix/master[346]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:05:08 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 361 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:06:24 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 370 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:07:37 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 373 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:07:50 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 376 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:08:14 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 379 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:08:14 8c3641250d23 postfix/master[346]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:09:22 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 382 exit status 1
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:10:07 8c3641250d23 postfix/master[346]: warning: process /usr/lib/postfix/sbin/smtpd pid 385 exit status 1
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:19,702 WARN received SIGTERM indicating exit request
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:19,702 INFO waiting for processes, postfix, syslog-ng to die
mailcowdockerized-postfix-mailcow-1  | Nov 18 13:10:19 8c3641250d23 syslog-ng[9]: syslog-ng shutting down; version='3.28.1'
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:19,807 INFO stopped: syslog-ng (exit status 0)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,810 INFO stopped: postfix (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 346 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 347 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 348 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 349 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 351 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 354 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 365 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 366 (exit status 15)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 367 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,811 INFO reaped unknown pid 368 (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,812 INFO stopped: processes (terminated by SIGTERM)
mailcowdockerized-postfix-mailcow-1  | 2023-11-18 13:10:20,812 INFO reaped unknown pid 397 (exit status 0)

unbound log:

######################################################################## 100.0%
mailcowdockerized-unbound-mailcow-1  | setup in directory /etc/unbound
mailcowdockerized-unbound-mailcow-1  | removing artifacts
mailcowdockerized-unbound-mailcow-1  | Setup success. Certificates created. Enable in unbound.conf file to use
mailcowdockerized-unbound-mailcow-1  | [1700308507] unbound[1:0] notice: init module 0: validator
mailcowdockerized-unbound-mailcow-1  | [1700308507] unbound[1:0] notice: init module 1: iterator
mailcowdockerized-unbound-mailcow-1  | [1700308507] unbound[1:0] info: start of service (unbound 1.17.1).
mailcowdockerized-unbound-mailcow-1  | [1700308536] unbound[1:0] info: generate keytag query _ta-4f66. NULL IN
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info: service stopped (unbound 1.17.1).
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info: server stats for thread 0: 24 queries, 18 answers from cache, 6 recursions, 0 prefetch, 0 rejected by ip ratelimiting
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info: server stats for thread 0: requestlist max 2 avg 0.666667 exceeded 0 jostled 0
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info: average recursion processing time 0.097414 sec
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info: histogram of recursion processing times
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info: [25%]=0.012288 median[50%]=0.016384 [75%]=0.32768
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info: lower(secs) upper(secs) recursions
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info:    0.008192    0.016384 3
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info:    0.016384    0.032768 1
mailcowdockerized-unbound-mailcow-1  | [1700308896] unbound[1:0] info:    0.262144    0.524288 2
mailcowdockerized-unbound-mailcow-1  | Setting console permissions...
mailcowdockerized-unbound-mailcow-1  | Receiving anchor key...
mailcowdockerized-unbound-mailcow-1  | Receiving root hints...
######################################################################## 100.0%
mailcowdockerized-unbound-mailcow-1  | setup in directory /etc/unbound
mailcowdockerized-unbound-mailcow-1  | removing artifacts
mailcowdockerized-unbound-mailcow-1  | Setup success. Certificates created. Enable in unbound.conf file to use
mailcowdockerized-unbound-mailcow-1  | [1700308897] unbound[1:0] notice: init module 0: validator
mailcowdockerized-unbound-mailcow-1  | [1700308897] unbound[1:0] notice: init module 1: iterator
mailcowdockerized-unbound-mailcow-1  | [1700308898] unbound[1:0] info: start of service (unbound 1.17.1).
mailcowdockerized-unbound-mailcow-1  | [1700308927] unbound[1:0] info: generate keytag query _ta-4f66. NULL IN
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info: service stopped (unbound 1.17.1).
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info: server stats for thread 0: 26 queries, 20 answers from cache, 6 recursions, 0 prefetch, 0 rejected by ip ratelimiting
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info: server stats for thread 0: requestlist max 2 avg 0.666667 exceeded 0 jostled 0
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info: average recursion processing time 0.099606 sec
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info: histogram of recursion processing times
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info: [25%]=0.012288 median[50%]=0.016384 [75%]=0.32768
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info: lower(secs) upper(secs) recursions
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info:    0.008192    0.016384 3
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info:    0.016384    0.032768 1
mailcowdockerized-unbound-mailcow-1  | [1700309314] unbound[1:0] info:    0.262144    0.524288 2
mailcowdockerized-unbound-mailcow-1  | Setting console permissions...
mailcowdockerized-unbound-mailcow-1  | Receiving anchor key...
mailcowdockerized-unbound-mailcow-1  | Receiving root hints...
######################################################################## 100.0%
mailcowdockerized-unbound-mailcow-1  | setup in directory /etc/unbound
mailcowdockerized-unbound-mailcow-1  | removing artifacts
mailcowdockerized-unbound-mailcow-1  | Setup success. Certificates created. Enable in unbound.conf file to use
mailcowdockerized-unbound-mailcow-1  | [1700309315] unbound[1:0] notice: init module 0: validator
mailcowdockerized-unbound-mailcow-1  | [1700309315] unbound[1:0] notice: init module 1: iterator
mailcowdockerized-unbound-mailcow-1  | [1700309315] unbound[1:0] info: start of service (unbound 1.17.1).
mailcowdockerized-unbound-mailcow-1  | [1700309345] unbound[1:0] info: generate keytag query _ta-4f66. NULL IN

esackbauer

smares terminated by SIGTERM

That means the containers are stopped correctly by asking them to stop.
Please check the watchdog container log, why is it stopping/restarting the containers.
Most likely something in your system fails a health check.

smares

mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:51 CET 2023 Container is running for less than 360 seconds, skipping action...
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:51 CET 2023 Postfix health level: 63% (5/8), health trend: -3
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:51 CET 2023 PHP-FPM health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:51 CET 2023 SOGo health level: 100% (3/3), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:51 CET 2023 Dovecot health level: 0% (0/12), health trend: -10
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:51 CET 2023 Ratelimit health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:51 CET 2023 Unbound health level: 40% (2/5), health trend: -3
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:47:52 CET 2023 Dovecot hit error limit
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000161s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000190s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000279s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000238s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000178s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000129s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000160s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000223s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 24: Connection refused
mailcowdockerized-watchdog-mailcow-1  | SMTP CRITICAL - 0.000 sec. response time|time=0.000151s;;;0.000000
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 993: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 143: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 10001: Connection refused
mailcowdockerized-watchdog-mailcow-1  | connect to address 172.35.1.250 and port 4190: Connection refused
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:02 CET 2023 Container is running for less than 360 seconds, skipping action...
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:02 CET 2023 Dovecot replication health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:02 CET 2023 MySQL/MariaDB health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:02 CET 2023 Redis health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:02 CET 2023 Dovecot health level: 17% (2/12), health trend: -10
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:05 CET 2023 Mail queue health level: 100% (20/20), health trend: 0

Or just now:

mailcowdockerized-watchdog-mailcow-1  | Connection to DNS 172.35.1.254 was refused
mailcowdockerized-watchdog-mailcow-1  | DNSSEC failure
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:49 CET 2023 Container is running for less than 360 seconds, skipping action...
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:49 CET 2023 MySQL/MariaDB health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:49 CET 2023 Clamd health level: 100% (15/15), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:49 CET 2023 Unbound health level: 40% (2/5), health trend: -3
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:51 CET 2023 Fail2ban health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:51 CET 2023 Olefy health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:48:58 CET 2023 Rspamd health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:49:05 CET 2023 Ratelimit health level: 100% (1/1), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:49:10 CET 2023 SOGo health level: 100% (3/3), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:49:11 CET 2023 Redis health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:49:12 CET 2023 Mail queue health level: 100% (20/20), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:49:15 CET 2023 PHP-FPM health level: 100% (5/5), health trend: 0
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:49:16 CET 2023 Postfix health level: 0% (0/8), health trend: -3
mailcowdockerized-watchdog-mailcow-1  | Sat Nov 18 13:49:17 CET 2023 Postfix hit error limit

I’ll be damned… In my first post, I wrote

Change IPV4_NETWORK to 172.35.1 since I was getting an “ERROR: Pool overlaps with other one on this address space” error.

I just changed that to 172.29.1, rebuilt the containers, and it works. Why? 😅

I’ll be dam*ed… In my first post, I wrote

Change IPV4_NETWORK to 172.35.1 since I was getting an “ERROR: Pool overlaps with other one on this address space” error.

I just changed that to 172.29.1, rebuilt the containers, and it works. Why? 😅

In my first post, I wrote

Change IPV4_NETWORK to 172.35.1 since I was getting an “ERROR: Pool overlaps with other one on this address space” error.

I just changed that to 172.29.1, rebuilt the containers, and it works. Why? 😅

Sorry for the multiple posts above, I kept getting an error that something went wrong and I assumed it was because of the curse word, but even after changing, I got the same error that my response cannot be posted. Apparently it was, after all.

smares

I was stupid by the way, class B private IPs are 172.16.0.0 to 172.31.255.255. That is why 172.29 works, but 172.35 doesn’t.