andryyy
commented
5 years ago I’m pretty sure it cannot read the cert or key.
Am 03.06.2019 um 10:07 schrieb Zakariae Filali notifications@github.com:
Describe the bug, try to make it reproducible I installed mailcow on a fresh Ubuntu 18.04, I checked the ports and the ssl are fine since I can access the https://mail..., but the dovecot container keeps on restarting
System information and quick debugging General logs:
Please take a look at the documentation. dovecot-mailcow_1 | 70_HS_body.cf dovecot-mailcow_1 | 70_HS_header.cf dovecot-mailcow_1 | 2019-06-03 07:52:42,595 CRIT Set uid to user 0 dovecot-mailcow_1 | 2019-06-03 07:52:42,600 INFO supervisord started with pid 1 dovecot-mailcow_1 | 2019-06-03 07:52:43,603 INFO spawned: 'processes' with pid 88 dovecot-mailcow_1 | 2019-06-03 07:52:43,606 INFO spawned: 'cron' with pid 89 dovecot-mailcow_1 | 2019-06-03 07:52:43,609 INFO spawned: 'dovecot' with pid 90 dovecot-mailcow_1 | 2019-06-03 07:52:43,612 INFO spawned: 'syslog-ng' with pid 91 dovecot-mailcow_1 | Jun 3 07:52:43 mail syslog-ng[91]: syslog-ng starting up; version='3.8.1' dovecot-mailcow_1 | 2019-06-03 07:52:43,705 INFO exited: dovecot (exit status 89; not expected) dovecot-mailcow_1 | 2019-06-03 07:52:44,706 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) dovecot-mailcow_1 | 2019-06-03 07:52:44,706 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) dovecot-mailcow_1 | 2019-06-03 07:52:44,708 INFO spawned: 'dovecot' with pid 96 dovecot-mailcow_1 | 2019-06-03 07:52:44,709 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) dovecot-mailcow_1 | 2019-06-03 07:52:44,770 INFO exited: dovecot (exit status 89; not expected) dovecot-mailcow_1 | 2019-06-03 07:52:46,775 INFO spawned: 'dovecot' with pid 98 dovecot-mailcow_1 | 2019-06-03 07:52:46,833 INFO exited: dovecot (exit status 89; not expected) dovecot-mailcow_1 | 2019-06-03 07:52:49,838 INFO spawned: 'dovecot' with pid 100 dovecot-mailcow_1 | 2019-06-03 07:52:49,899 INFO exited: dovecot (exit status 89; not expected) dovecot-mailcow_1 | 2019-06-03 07:52:49,900 INFO gave up: dovecot entered FATAL state, too many start retries too quickly dovecot-mailcow_1 | 2019-06-03 07:52:50,904 WARN received SIGQUIT indicating exit request dovecot-mailcow_1 | 2019-06-03 07:52:50,905 INFO waiting for cron, processes, syslog-ng to die dovecot-mailcow_1 | Jun 3 07:52:50 mail syslog-ng[91]: syslog-ng shutting down; version='3.8.1' dovecot-mailcow_1 | 2019-06-03 07:52:51,008 INFO stopped: syslog-ng (exit status 0) dovecot-mailcow_1 | 2019-06-03 07:52:52,010 INFO stopped: cron (terminated by SIGTERM) dovecot-mailcow_1 | 2019-06-03 07:52:52,011 INFO stopped: processes (terminated by SIGTERM) Further information (where applicable):
Your OS (is Apparmor or SELinux active?) Ubuntu 18.04 Your virtualization technology (KVM/QEMU, Xen, VMware, VirtualBox etc.) it's a baremetal server Don't try to run mailcow on a Synology or QNAP NAS, do you? No Docker and Docker Compose version: Docker version 18.09.6, docker-compose version 1.24.0 Output of git diff origin/master, any other changes to the code? services:
- acme.sh:
- build: acme.sh
- environment:
- ACME_DNS=${ACME_DNS}
- ACME_HOST=${MAILCOW_HOSTNAME}
- CF_Key=${CF_KEY}
- CF_Email=${CF_EMAIL}
- ACCOUNTEMAIL=${CF_EMAIL}
- volumes:
- ./data/acme:/acme.sh
- ./data/assets/ssl/:/certs
unbound-mailcow: image: mailcow/unbound:1.7 build: ./data/Dockerfiles/unbound @@ -267,6 +279,7 @@ services:
nginx-mailcow: depends_on:
- acme.sh
- sogo-mailcow
- php-fpm-mailcow
- redis-mailcow @@ -330,7 +343,7 @@ services:
- TZ=${TZ} volumes:
- ./data/web/.well-known/acme-challenge:/var/www/acme:rw
- ./data/assets/ssl:/var/lib/acme/:rw
- ./data/assets/ssl:/var/lib/acme/:rw
- ./data/assets/ssl-example:/var/lib/ssl-example/:ro - mysql-socket-vol-1:/var/run/mysqld/restart: always @@ -441,7 +454,7 @@ services:
- postfix-mailcow
- memcached-mailcow
- nginx-mailcow
- acme-mailcow
- acme-mailcow
- netfilter-mailcow - watchdog-mailcow - dockerapi-mailcowAll third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn, ip6tables -L -vn, iptables -L -vn -t nat and ip6tables -L -vn -t nat All ports are open using ufw Reverse proxy? If you think this problem is related to your reverse proxy, please post your configuration. No reverse proxy Browser (if it's a Web UI issue) - please clean your browser cache and try again, problem persists? Check docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254 (set the IP accordingly, if you changed the internal mailcow network) and docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @1.1.1.1 - output? Timeout? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
kariae
ghost
Braintelligence
choffman5718
alexanderadam
Yatekii
pilotboy72
zauberstuhl
Tominator89
Describe the bug, try to make it reproducible I installed mailcow on a fresh Ubuntu 18.04, I checked the ports and the ssl are fine since I can access the https://mail..., but the dovecot container keeps on restarting
System information and quick debugging General logs:
Full logs in gist
Further information (where applicable):
git diff origin/master, any other changes to the code?unbound-mailcow: image: mailcow/unbound:1.7 build: ./data/Dockerfiles/unbound @@ -267,6 +279,7 @@ services:
nginx-mailcow: depends_on:
- ./data/assets/ssl:/var/lib/acme/:rw
restart: always @@ -441,7 +454,7 @@ services:
- acme-mailcow