I was hoping to easily replace Kerio Connect by mailcow by spinning up a Debian VM and following these steps. Every step seems to work and when entering the FQDN I’m greeted with “webserver is functioning normally”, but nothing more than that. When entering the IP address I’m greeted with the following screen:
I have also tried running everything on Synology/Container Manager with almost the same result. There I’m greeted with the same screens, but also the following error:
Error response from daemon: Bind mount failed: '/volume1/docker/mailcow-dockerized/data/web/.well-known/acme-challenge' does not exists
Also “mailcowdockerized-acme-mailcow-1” doesn’t seem the want to run. For Synology I had to change mailcow.conf to run on ports 8080 and 8443 instead of 80 and 443.
I would prefer running everything in Container Manager, so my question: how to debug from there?
Edit: After manually creating the directory (mkdir -p /volume1/docker/mailcow-dockerized/data/web/.well-known/acme-challenge), mailcowdockerized-acme-mailcow-1 does start, but mailcowdockerized-ipv6nat-mailcow-1 keeps restarting showing the following error: “unable to detect hairpin mode (is the docker daemon running?) ”. All else is the same.
Another error that might be interesting: [error] 22#22: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.200, server: [FQDN], request: “GET / HTTP/2.0”, upstream: “fastcgi://[fd4d:6169:6c63:6f77::a]:9002”, host: “192.168.2.200:8443”
