Hi All.
My team and I have been battling to get mailcow running on our servers for the past few weeks.
Installation goes perfectly fine, but ACME-mailcow is unable to generate the certificates.
It detects our Public IP correctly, but then the A record DNS lookup reverts back to the VMs internal LAN IP.
Here are our logs, we have tried 8 times on fresh Ubuntu 22.04 installs. Any help would be greatly appreciated.
acme-mailcow-1 | 2024-04-15T06:58:11.088646840Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Docker API…
acme-mailcow-1 | 2024-04-15T06:58:11.111293170Z Mon Apr 15 09:58:11 EAT 2024 - Docker API OK
acme-mailcow-1 | 2024-04-15T06:58:11.127157703Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Postfix…
acme-mailcow-1 | 2024-04-15T06:58:11.145927392Z Mon Apr 15 09:58:11 EAT 2024 - Postfix OK
acme-mailcow-1 | 2024-04-15T06:58:11.160810560Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Dovecot…
acme-mailcow-1 | 2024-04-15T06:58:11.180074776Z Mon Apr 15 09:58:11 EAT 2024 - Dovecot OK
acme-mailcow-1 | 2024-04-15T06:58:11.271384324Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for database…
acme-mailcow-1 | 2024-04-15T06:58:11.305947845Z Mon Apr 15 09:58:11 EAT 2024 - Database OK
acme-mailcow-1 | 2024-04-15T06:58:11.321035452Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Nginx…
acme-mailcow-1 | 2024-04-15T06:58:11.347624963Z Mon Apr 15 09:58:11 EAT 2024 - Nginx OK
acme-mailcow-1 | 2024-04-15T06:58:11.361708441Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for resolver…
acme-mailcow-1 | 2024-04-15T06:58:11.479971547Z Mon Apr 15 09:58:11 EAT 2024 - Resolver OK
acme-mailcow-1 | 2024-04-15T06:58:11.493756001Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for domain table…
acme-mailcow-1 | 2024-04-15T06:58:11.640666094Z OK
acme-mailcow-1 | 2024-04-15T06:58:11.654540698Z Mon Apr 15 09:58:11 EAT 2024 - Initializing, please wait…
acme-mailcow-1 | 2024-04-15T06:58:12.370569315Z Mon Apr 15 09:58:12 EAT 2024 - Using existing domain rsa key /var/lib/acme/acme/key.pem
acme-mailcow-1 | 2024-04-15T06:58:12.384939555Z Mon Apr 15 09:58:12 EAT 2024 - Using existing Lets Encrypt account key /var/lib/acme/acme/account.pem
acme-mailcow-1 | 2024-04-15T06:58:12.403864022Z Mon Apr 15 09:58:12 EAT 2024 - Detecting IP addresses…
acme-mailcow-1 | 2024-04-15T06:58:22.445191380Z Mon Apr 15 09:58:22 EAT 2024 - OK: 196.xxx.xx.xx, 0000:0000:0000:0000:0000:0000:0000:0000
acme-mailcow-1 | 2024-04-15T06:58:22.794571804Z Mon Apr 15 09:58:22 EAT 2024 - Found A record for mail.xyz.com: 10.10.1.109
acme-mailcow-1 | 2024-04-15T06:58:22.809034264Z Mon Apr 15 09:58:22 EAT 2024 - Cannot match your IP 196.xxx.xx.xx against hostname mail.xyz.com (DNS returned 10.10.1.109)
acme-mailcow-1 | 2024-04-15T06:58:22.829510734Z Mon Apr 15 09:58:22 EAT 2024 - Cannot validate any hostnames, skipping Let’s Encrypt for 1 hour.
acme-mailcow-1 | 2024-04-15T06:58:22.842764297Z Mon Apr 15 09:58:22 EAT 2024 - Use SKIP_LETS_ENCRYPT=y in mailcow.conf to skip it permanently.
acme-mailcow-1 | 2024-04-15T06:58:22.859996359Z OK
To add more info, our network is behind a CISCO router and which is NAT-ing our public IP to the VMs Internal IP.