Mailcow-dockerized: Mailcow Update done, now 502 bad Gateway

Created on 19 Oct 2018 · 28Comments · Source: mailcow/mailcow-dockerized

Sorry for the post here. I have trubble now to reach the GUI. i get 502 Bad Gateway.

docker-compose logs nginx-mailcow

nginx-mailcow_1      | 2018/10/19 18:59:32 [warn] 11#11: conflicting server name "srv1.coalmail.de" on 0.0.0.0:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "srv1.coalmail.de" on 0.0.0.0:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:32 [warn] 11#11: conflicting server name "autodiscover.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autodiscover.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:32 [warn] 11#11: conflicting server name "autoconfig.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autoconfig.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:32 [warn] 11#11: conflicting server name "srv1.coalmail.de" on [::]:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "srv1.coalmail.de" on [::]:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:32 [warn] 11#11: conflicting server name "autodiscover.*" on [::]:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autodiscover.*" on [::]:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:32 [warn] 11#11: conflicting server name "autoconfig.*" on [::]:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autoconfig.*" on [::]:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:35 [warn] 1#1: conflicting server name "srv1.coalmail.de" on 0.0.0.0:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "srv1.coalmail.de" on 0.0.0.0:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:35 [warn] 1#1: conflicting server name "autodiscover.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autodiscover.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:35 [warn] 1#1: conflicting server name "autoconfig.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autoconfig.*" on 0.0.0.0:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:35 [warn] 1#1: conflicting server name "srv1.coalmail.de" on [::]:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "srv1.coalmail.de" on [::]:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:35 [warn] 1#1: conflicting server name "autodiscover.*" on [::]:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autodiscover.*" on [::]:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:35 [warn] 1#1: conflicting server name "autoconfig.*" on [::]:80, ignored
nginx-mailcow_1      | nginx: [warn] conflicting server name "autoconfig.*" on [::]:80, ignored
nginx-mailcow_1      | 2018/10/19 18:59:43 [error] 16#16: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 217.83.239.52, server: srv1.coalmail.de, request: "GET HTTP/2.0", upstream: "fastcgi://172.22.1.9:9002", host: "srv1.coalmail.de"
nginx-mailcow_1      | 2018/10/19 18:59:43 [error] 16#16: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 217.83.239.52, server: srv1.coalmail.de, request: "GET HTTP/2.0", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9002", host: "srv1.coalmail.de"
nginx-mailcow_1      | 217.83.239.52 - - [19/Oct/2018:18:59:43 +0200] "GET / HTTP/2.0" 502 150 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0"
nginx-mailcow_1      | 2018/10/19 18:59:44 [error] 16#16: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.1.12, server: _, request: "HEAD /forwardinghostshp HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx"
nginx-mailcow_1      | 2018/10/19 18:59:44 [error] 16#16: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.1.12, server: _, request: "HEAD /forwardinghostshp HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9001", host: "nginx"
nginx-mailcow_1      | 172.22.1.12 - - [19/Oct/2018:18:59:44 +0200] "HEAD /forwardinghosts.php HTTP/1.1" 502 0 "-" "-"
nginx-mailcow_1      | 2018/10/19 18:59:44 [error] 16#16: *7 no live upstreams while connecting to upstream, client: fd4d:6169:6c63:6f77::1, server: _, request: "HEAD /settings.php HTTP/1.1", upstrm: "fastcgi://phpfpm", host: "nginx"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::1 - - [19/Oct/2018:18:59:44 +0200] "HEAD /settings.php HTTP/1.1" 502 0 "-" "-"
nginx-mailcow_1      | 2018/10/19 19:00:04 [error] 16#16: *10 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::1, server: _, request: "GET /forwdinghosts.php?host=193.169.252.113 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9001", host: "nginx:8081"
nginx-mailcow_1      | 2018/10/19 19:00:04 [error] 16#16: *10 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::1, server: _, request: "GET /forwdinghosts.php?host=193.169.252.113 HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::1 - - [19/Oct/2018:19:00:04 +0200] "GET /forwardinghosts.php?host=193.169.252.113 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2018/10/19 19:03:45 [error] 16#16: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 217.83.239.52, server: srv1.coalmail.de, request: "GET HTTP/2.0", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9002", host: "srv1.coalmail.de"
nginx-mailcow_1      | 217.83.239.52 - - [19/Oct/2018:19:03:45 +0200] "GET / HTTP/2.0" 502 150 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0"
nginx-mailcow_1      | 2018/10/19 19:03:45 [error] 16#16: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 217.83.239.52, server: srv1.coalmail.de, request: "GET HTTP/2.0", upstream: "fastcgi://172.22.1.9:9002", host: "srv1.coalmail.de"

grep -rn 'server_name' /opt/mailcow-dockerized/data/conf/nginx/

/opt/mailcow-dockerized# grep -rn 'server_name' /opt/mailcow-dockerized/data/conf/nginx/
/opt/mailcow-dockerized/data/conf/nginx/server_name.active:1:server_name srv1.coalmail.de autodiscover.* autoconfig.*;
/opt/mailcow-dockerized/data/conf/nginx/site.conf:4:  include /etc/nginx/conf.d/server_name.active;
/opt/mailcow-dockerized/data/conf/nginx/site.conf:14:server_names_hash_bucket_size 64;
/opt/mailcow-dockerized/data/conf/nginx/site.conf:59:  include /etc/nginx/conf.d/server_name.active;
/opt/mailcow-dockerized/data/conf/nginx/site.conf:161:    proxy_set_header x-webobjects-server-name $server_name;
/opt/mailcow-dockerized/data/conf/nginx/site.conf:175:    proxy_set_header x-webobjects-server-name $server_name;
/opt/mailcow-dockerized/data/conf/nginx/meta_exporter.conf:4:  server_name _;
/opt/mailcow-dockerized/data/conf/nginx/dynmaps.conf:5:  server_name _;
/opt/mailcow-dockerized/data/conf/nginx/templates/server_name.template:1:server_name ${MAILCOW_HOSTNAME} autodiscover.* autoconfig.*;

before update i disable apache2 and reconfigured the mailcow.conf to standard Bindings

HTTP_PORT=80
HTTP_BIND=0.0.0.0

HTTPS_PORT=443
HTTPS_BIND=0.0.0.0

netstat -tulpn | grep -E -w '25|80|110|143|443|465|587|993|995

Returns nothing
So any help :-(

dunno

Source

JonnyFPV

Most helpful comment

it works :D

JonnyFPV on 20 Oct 2018

👍2 🎉1

All 28 comments

PHP-FPM is either not running (Nginx cannot find the upstream) or it is a IPv6 firewall issue. Is it a Hetzner cloud server?

andryyy on 19 Oct 2018

hi,

no its a netcup VServer

befor update it was running great

JonnyFPV on 19 Oct 2018

I'm on a netcup vserver as well without a problem. What is your docker-compose ps output? What does docker exec $(docker ps -f name=php-fpm-mailcow -q) netstat -tulpen show? docker-compose logs php-fpm-mailcow? Did you try turning it off and on again? ;) docker-compose down && docker-compose up -d? All containers up?

before update i disable apache2

do you have something else running on port 9000?

PaulRitzkat on 20 Oct 2018

I'm having the same problem with a fresh install on Debian 9.4. I followed the instructions but at the end of the process, nginx is not allowing any connections (502 Bad Gateway) for the main UI as well as SOGo.

First, immediately after the install, starting the containers throws "permission denied" errors. These can be cleaned up by disabling oom (commenting 2 lines from the mailcow.conf file). This eliminates the permission denied error, but the 502 error persists.

I've also tried to disable iptables and/or ufw, but it has no effect. Disabling IPv6 also has no effect.

root@la:/opt/mailcow-dockerized# docker-compose logs nginx-mailcow
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Attaching to mailcowdockerized_nginx-mailcow_1
nginx-mailcow_1      | 2018/10/19 23:37:34 [emerg] 11#11: host not found in upstream "rspamd" in /etc/nginx/conf.d/site.conf:103
nginx-mailcow_1      | nginx: [emerg] host not found in upstream "rspamd" in /etc/nginx/conf.d/site.conf:103
nginx-mailcow_1      | nginx: configuration file /etc/nginx/nginx.conf test failed
nginx-mailcow_1      | 2018/10/19 23:37:39 [error] 17#17: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.1.11, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx"
nginx-mailcow_1      | 2018/10/19 23:37:39 [error] 17#17: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.1.11, server: _, request: "HEAD /settings.php HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9001", host: "nginx"
nginx-mailcow_1      | 2018/10/19 23:37:39 [error] 17#17: *4 no live upstreams while connecting to upstream, client: 172.22.1.11, server: _, request: "HEAD /settings.php HTTP/1.1", upstream: "fastcgi://phpfpm", host: "nginx"
nginx-mailcow_1      | 172.22.1.11 - - [19/Oct/2018:23:37:39 -0700] "HEAD /settings.php HTTP/1.1" 502 0 "-" "-"
nginx-mailcow_1      | 2018/10/19 23:37:39 [error] 17#17: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.1.11, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9001", host: "nginx"
nginx-mailcow_1      | 172.22.1.11 - - [19/Oct/2018:23:37:39 -0700] "HEAD /forwardinghosts.php HTTP/1.1" 502 0 "-" "-"
nginx-mailcow_1      | 2018/10/19 23:37:44 [error] 17#17: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 24.140.255.227, server: la.tactilemuseum.com, request: "GET / HTTP/2.0", upstream: "fastcgi://172.22.1.9:9002", host: "la.tactilemuseum.com"
nginx-mailcow_1      | 2018/10/19 23:37:44 [error] 17#17: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 24.140.255.227, server: la.tactilemuseum.com, request: "GET / HTTP/2.0", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9002", host: "la.tactilemuseum.com"
nginx-mailcow_1      | 24.140.255.227 - - [19/Oct/2018:23:37:44 -0700] "GET / HTTP/2.0" 502 552 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36"

Other potentially important logs:

mysql-mailcow_1      | 2018-10-19 23:37:29 139986929964800 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
mysql-mailcow_1      | 2018-10-19 23:37:29 139986929964800 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade

and sogo and php-fpm are continually advising the following:

sogo-mailcow_1       | Waiting for database to come up...
sogo-mailcow_1       | Waiting for database to come up...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...

jobidon on 20 Oct 2018

SQL is not running. Run mysql_upgrade. See other issues. :-)

I think we need a custom SQL image to automate those tasks.

andryyy on 20 Oct 2018

> docker-compose ps

``
root@srv1:/opt/mailcow-dockerized# docker-compose ps
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
                Name                               Command               State                                                         Ports
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
mailcowdockerized_acme-mailcow_1        /sbin/tini -g -- /srv/dock ...   Up
mailcowdockerized_clamd-mailcow_1       /sbin/tini -g -- /bootstrap.sh   Up      3310/tcp
mailcowdockerized_dockerapi-mailcow_1   python2 -u /server.py            Up
mailcowdockerized_dovecot-mailcow_1     /docker-entrypoint.sh /bin ...   Up      0.0.0.0:110->110/tcp, 127.0.0.1:19991->12345/tcp, 0.0.0.0:143->143/tcp, 0.0.0.0:4190->4190/tcp,
                                                                                 0.0.0.0:993->993/tcp, 0.0.0.0:995->995/tcp
mailcowdockerized_ipv6nat_1             /docker-ipv6nat --retry          Up
mailcowdockerized_memcached-mailcow_1   docker-entrypoint.sh memcached   Up      11211/tcp
mailcowdockerized_mysql-mailcow_1       docker-entrypoint.sh mysqld      Up      127.0.0.1:13306->3306/tcp
mailcowdockerized_netfilter-mailcow_1   python2 -u /server.py            Up
mailcowdockerized_nginx-mailcow_1       /bin/sh -c envsubst < /etc ...   Up      0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
mailcowdockerized_php-fpm-mailcow_1     /docker-entrypoint.sh php- ...   Up      9000/tcp
mailcowdockerized_postfix-mailcow_1     /bin/sh -c exec /usr/bin/s ...   Up      0.0.0.0:25->25/tcp, 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, 588/tcp
mailcowdockerized_redis-mailcow_1       docker-entrypoint.sh redis ...   Up      6379/tcp
mailcowdockerized_rspamd-mailcow_1      /docker-entrypoint.sh /usr ...   Up
mailcowdockerized_sogo-mailcow_1        /bin/sh -c exec /usr/bin/s ...   Up
mailcowdockerized_unbound-mailcow_1     /docker-entrypoint.sh /usr ...   Up      53/tcp, 53/udp
mailcowdockerized_watchdog-mailcow_1    /sbin/tini -g -- /bin/sh - ...   Up
``

``
root@srv1:/opt/mailcow-dockerized# docker exec $(docker ps -f name=php-fpm-mailcow -q) netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.11:34015        0.0.0.0:*               LISTEN      -
udp        0      0 127.0.0.11:51322        0.0.0.0:*                           -
``



md5-5ea01e052cf66e24bc51f9760ff70b78



``
root@srv1:/opt/mailcow-dockerized# docker-compose logs php-fpm-mailcow
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Attaching to mailcowdockerized_php-fpm-mailcow_1
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
``

and yes i restartet the container a few times :-(
No other service on 9000 i think. i was using ufw. i deletet it with apt-get purge ufw. but no effect.

JonnyFPV on 20 Oct 2018

source mailcow.conf; docker-compose exec mysql-mailcow mysql_upgrade -uroot -p${DBROOT}

andryyy on 20 Oct 2018

it works :D

JonnyFPV on 20 Oct 2018

👍2 🎉1

Running the above command caused an access denied:

root@la:/opt/mailcow-dockerized# source mailcow.conf; docker-compose exec mysql-mailcow mysql_upgrade -uroot -p${DBROOT}
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
FATAL ERROR: Upgrade failed

However, when I issued the following:

source mailcow.conf; docker-compose exec mysql-mailcow mysql_upgrade -uroot -p${DBROOT} --host=localhost

the mysql upgrade worked. But I still have a 502 Bad Gateway error. Logs indicate that php and sogo still can't connect to the DB, and nginx still faces connection refused:

php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...
sogo-mailcow_1       | Waiting for database to come up...
sogo-mailcow_1       | Waiting for database to come up...
sogo-mailcow_1       | Waiting for database to come up...
sogo-mailcow_1       | Waiting for database to come up...
...
nginx-mailcow_1      | fd4d:6169:6c63:6f77::6 - - [20/Oct/2018:08:20:48 -0700] "GET /forwardinghosts.php?host=208.49.63.59 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2018/10/20 08:20:57 [error] 16#16: *32 no live upstreams while connecting to upstream, client: 172.22.1.11, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://phpfpm", host: "nginx"
nginx-mailcow_1      | 172.22.1.11 - - [20/Oct/2018:08:20:57 -0700] "HEAD /forwardinghosts.php HTTP/1.1" 502 0 "-" "-"
nginx-mailcow_1      | 2018/10/20 08:22:22 [error] 16#16: *33 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::6, server: _, request: "GET /forwardinghosts.php?host=74.112.64.182 HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx:8081"
nginx-mailcow_1      | 2018/10/20 08:22:22 [error] 16#16: *33 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::6, server: _, request: "GET /forwardinghosts.php?host=74.112.64.182 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9001", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::6 - - [20/Oct/2018:08:22:22 -0700] "GET /forwardinghosts.php?host=74.112.64.182 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2018/10/20 08:22:24 [error] 16#16: *36 no live upstreams while connecting to upstream, client: fd4d:6169:6c63:6f77::6, server: _, request: "GET /forwardinghosts.php?host=200.14.133.71 HTTP/1.1", upstream: "fastcgi://phpfpm", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::6 - - [20/Oct/2018:08:22:24 -0700] "GET /forwardinghosts.php?host=200.14.133.71 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2018/10/20 08:22:42 [error] 16#16: *37 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::6, server: _, request: "GET /forwardinghosts.php?host=209.237.239.64 HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx:8081"
nginx-mailcow_1      | 2018/10/20 08:22:42 [error] 16#16: *37 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::6, server: _, request: "GET /forwardinghosts.php?host=209.237.239.64 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::c]:9001", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::6 - - [20/Oct/2018:08:22:42 -0700] "GET /forwardinghosts.php?host=209.237.239.64 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 24.140.255.227 - - [20/Oct/2018:08:23:13 -0700] "GET /SOGo/ HTTP/1.1" 502 552 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36"
nginx-mailcow_1      | 2018/10/20 08:23:13 [error] 16#16: *40 connect() failed (111: Connection refused) while connecting to upstream, client: 24.140.255.227, server: la.tactilemuseum.com, request: "GET /SOGo/ HTTP/1.1", upstream: "http://172.22.1.248:20000/SOGo/", host: "la.tactilemuseum.com"

This is all on a fresh install, where I had deleted all images, containers and volumes prior to the installation.

jobidon on 20 Oct 2018

There is no "access denied" when it is a fresh installation. It would not have any database and tables.

mysql_upgrade is _not_ needed when you install a new mailcow. Just run the commands from the docs. But make sure you delete all previous/old volumes and containers (docker-compose down -v) before trying again.

When you see any connection failures on a _fresh_ installation, it indicates a problem with a local firewall, not with old MySQL data. 👍

Please try again and if it still fails, post the output of docker-compose logs --tail=200 mysql-mailcow and iptables -L -vn.

andryyy on 20 Oct 2018

I also thought this was unusual:

MariaDB [(none)]> SELECT user,host,password FROM mysql.user;
+---------+-----------+-------------------------------------------+
| user    | host      | password                                  |
+---------+-----------+-------------------------------------------+
| root    | localhost |                                           |
| mailcow | %         | *41E37E39C883D9703FA272A555D3C195A521C62B |
| root    | %         | *FB35A74FA62A918117CC439901B5B5C28703A9BF |
+---------+-----------+-------------------------------------------+
3 rows in set (0.00 sec)

is it expected to have 2 root user entries? Each with a different password depending on hostname?

jobidon on 20 Oct 2018

That's not normal indeed. Some of the previously run commands messed up the table. Just run docker-compose down -v and start over.

andryyy on 20 Oct 2018

ok, here's what I did. First cleaning up:

docker rm $(docker ps -a -q)
docker volume prune
rm -Rf /opt/mailcow-dockerized/

then reinstall:

root@la:/opt# git clone https://github.com/mailcow/mailcow-dockerized
Cloning into 'mailcow-dockerized'...
remote: Enumerating objects: 140, done.
remote: Counting objects: 100% (140/140), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 18148 (delta 63), reused 109 (delta 61), pack-reused 18008
Receiving objects: 100% (18148/18148), 10.94 MiB | 0 bytes/s, done.
Resolving deltas: 100% (10586/10586), done.
root@la:/opt# cd mailcow-dockerized/
root@la:/opt/mailcow-dockerized# ./generate_config.sh 
Press enter to confirm the detected value '[value]' where applicable or enter a custom value.
Hostname (FQDN): [mx.domain.tld]
Timezone [America/Los_Angeles]: 
root@la:/opt/mailcow-dockerized# docker-compose up -d
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Creating volume "mailcowdockerized_vmail-vol-1" with default driver
Creating volume "mailcowdockerized_mysql-vol-1" with default driver
Creating volume "mailcowdockerized_mysql-socket-vol-1" with default driver
Creating volume "mailcowdockerized_redis-vol-1" with default driver
Creating volume "mailcowdockerized_rspamd-vol-1" with default driver
Creating volume "mailcowdockerized_postfix-vol-1" with default driver
Creating volume "mailcowdockerized_crypt-vol-1" with default driver
Creating mailcowdockerized_dovecot-mailcow_1 ... 
Creating mailcowdockerized_dockerapi-mailcow_1 ... error
Creating mailcowdockerized_ipv6nat_1           ... done
Creating mailcowdockerized_postfix-mailcow_1   ... 
Creating mailcowdockerized_sogo-mailcow_1      ... 
Creating mailcowdockerized_dovecot-mailcow_1   ... done
Creating mailcowdockerized_unbound-mailcow_1   ... 
Creating mailcowdockerized_clamd-mailcow_1     ... 
Creating mailcowdockerized_postfix-mailcow_1   ... done
Creating mailcowdockerized_mysql-mailcow_1     ... 
Creating mailcowdockerized_watchdog-mailcow_1  ... 

ERROR: for mailcowdockerized_dockerapi-mailcow_1  Cannot start service dockerapi-mailcow: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"process_linux.go:367: setting cgroup config for procHooks process caused \Creating mailcowdockerized_sogo-mailcow_1      ... done
Creating mailcowdockerized_redis-mailcow_1     ... done
Creating mailcowdockerized_unbound-mailcow_1   ... done
Creating mailcowdockerized_clamd-mailcow_1     ... done
Creating mailcowdockerized_memcached-mailcow_1 ... done
Creating mailcowdockerized_mysql-mailcow_1     ... done
.oom_control: permission denied\\\"\"": unknown
Creating mailcowdockerized_php-fpm-mailcow_1   ... done
Creating mailcowdockerized_netfilter-mailcow_1 ... done
Creating mailcowdockerized_nginx-mailcow_1     ... done
Creating mailcowdockerized_rspamd-mailcow_1    ... done
Creating mailcowdockerized_acme-mailcow_1      ... done

ERROR: for dockerapi-mailcow  Cannot start service dockerapi-mailcow: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"process_linux.go:367: setting cgroup config for procHooks process caused \\\"failed to write 1 to memory.oom_control: write /sys/fs/cgroup/memory/docker/30accfbb9f5c9b3f20565805d804720ad6607367db34a46a1e101cd645266bb9/memory.oom_control: permission denied\\\"\"": unknown

ERROR: for watchdog-mailcow  Cannot start service watchdog-mailcow: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"process_linux.go:367: setting cgroup config for procHooks process caused \\\"failed to write 1 to memory.oom_control: write /sys/fs/cgroup/memory/docker/ddf5f74be5697d7d5fabb59d70f39df5bcec68ef022115077e43cbc5203f79db/memory.oom_control: permission denied\\\"\"": unknown
ERROR: Encountered errors while bringing up the project.

At this point, accessing sogo works, but the mailcow gui through https gives a strange error:

Connection to dockerapi container failed.

The following error was reported:
0 - php_network_getaddresses: getaddrinfo failed: Name does not resolve

Logs:

nginx-mailcow_1      | 2018/10/20 09:06:21 [emerg] 16#16: host not found in upstream "rspamd" in /etc/nginx/conf.d/site.conf:103
nginx-mailcow_1      | nginx: [emerg] host not found in upstream "rspamd" in /etc/nginx/conf.d/site.conf:103
nginx-mailcow_1      | nginx: configuration file /etc/nginx/nginx.conf test failed
...
mysql-mailcow_1      | Initializing database
mysql-mailcow_1      | 2018-10-20  9:06:17 140427106609088 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
mysql-mailcow_1      | 
mysql-mailcow_1      | 
mysql-mailcow_1      | PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
mysql-mailcow_1      | To do so, start the server, then issue the following commands:
mysql-mailcow_1      | 
mysql-mailcow_1      | '/usr/bin/mysqladmin' -u root password 'new-password'
mysql-mailcow_1      | '/usr/bin/mysqladmin' -u root -h  password 'new-password'
mysql-mailcow_1      | 
mysql-mailcow_1      | Alternatively you can run:
mysql-mailcow_1      | '/usr/bin/mysql_secure_installation'
mysql-mailcow_1      | 
mysql-mailcow_1      | which will also give you the option of removing the test
mysql-mailcow_1      | databases and anonymous user created by default.  This is
mysql-mailcow_1      | strongly recommended for production servers.
mysql-mailcow_1      | 
mysql-mailcow_1      | See the MariaDB Knowledgebase at http://mariadb.com/kb or the
mysql-mailcow_1      | MySQL manual for more instructions.
mysql-mailcow_1      | 
mysql-mailcow_1      | Please report any problems at http://mariadb.org/jira
mysql-mailcow_1      | 
mysql-mailcow_1      | The latest information about MariaDB is available at http://mariadb.org/.
mysql-mailcow_1      | You can find additional information about the MySQL part at:
mysql-mailcow_1      | http://dev.mysql.com
mysql-mailcow_1      | Consider joining MariaDB's strong and vibrant community:
mysql-mailcow_1      | https://mariadb.org/get-involved/
mysql-mailcow_1      | 
mysql-mailcow_1      | Database initialized
mysql-mailcow_1      | MySQL init process in progress...
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] mysqld (mysqld 10.2.18-MariaDB-1:10.2.18+maria~bionic) starting as process 105 ...
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Uses event mutexes
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Using Linux native AIO
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Number of pools: 1
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Using SSE2 crc32 instructions
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Completed initialization of buffer pool
mysql-mailcow_1      | 2018-10-20  9:06:25 140049489954560 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Highest supported file format is Barracuda.
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: 128 out of 128 rollback segments are active.
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql-mailcow_1      | 2018-10-20  9:06:25 140050235230144 [Note] InnoDB: Waiting for purge to start
mysql-mailcow_1      | 2018-10-20  9:06:26 140050235230144 [Note] InnoDB: 5.7.23 started; log sequence number 1619996
mysql-mailcow_1      | 2018-10-20  9:06:26 140049481561856 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql-mailcow_1      | 2018-10-20  9:06:26 140049481561856 [Note] InnoDB: Buffer pool(s) load completed at 181020  9:06:26
mysql-mailcow_1      | 2018-10-20  9:06:26 140050235230144 [Warning] 'user' entry 'root@eb630873aa72' ignored in --skip-name-resolve mode.
mysql-mailcow_1      | 2018-10-20  9:06:26 140050235230144 [Warning] 'proxies_priv' entry '@% root@eb630873aa72' ignored in --skip-name-resolve mode.
mysql-mailcow_1      | 2018-10-20  9:06:26 140049922463488 [Note] Event Scheduler: scheduler thread started with id 6
mysql-mailcow_1      | 2018-10-20  9:06:26 140050235230144 [Note] mysqld: ready for connections.
mysql-mailcow_1      | Version: '10.2.18-MariaDB-1:10.2.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
mysql-mailcow_1      | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
mysql-mailcow_1      | 2018-10-20  9:06:31 140049422505728 [Warning] 'proxies_priv' entry '@% root@eb630873aa72' ignored in --skip-name-resolve mode.
mysql-mailcow_1      | 
mysql-mailcow_1      | 2018-10-20  9:06:31 140049422198528 [Note] mysqld (initiated by: unknown): Normal shutdown
mysql-mailcow_1      | 2018-10-20  9:06:31 140049431205632 [Note] InnoDB: FTS optimize thread exiting.
mysql-mailcow_1      | 2018-10-20  9:06:31 140049422198528 [Note] Event Scheduler: Killing the scheduler thread, thread id 6
mysql-mailcow_1      | 2018-10-20  9:06:31 140049422198528 [Note] Event Scheduler: Waiting for the scheduler thread to reply
mysql-mailcow_1      | 2018-10-20  9:06:31 140049422198528 [Note] Event Scheduler: Stopped
mysql-mailcow_1      | 2018-10-20  9:06:31 140049422198528 [Note] Event Scheduler: Purging the queue. 0 events
mysql-mailcow_1      | 2018-10-20  9:06:31 140049422198528 [Note] InnoDB: Starting shutdown...
mysql-mailcow_1      | 2018-10-20  9:06:31 140049481561856 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
mysql-mailcow_1      | 2018-10-20  9:06:31 140049481561856 [Note] InnoDB: Buffer pool(s) dump completed at 181020  9:06:31
mysql-mailcow_1      | 2018-10-20  9:06:32 140049422198528 [Note] InnoDB: Shutdown completed; log sequence number 1620024
mysql-mailcow_1      | 2018-10-20  9:06:32 140049422198528 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
mysql-mailcow_1      | 2018-10-20  9:06:32 140049422198528 [Note] mysqld: Shutdown complete
mysql-mailcow_1      | 
mysql-mailcow_1      | 
mysql-mailcow_1      | MySQL init process done. Ready for start up.
mysql-mailcow_1      | 
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] mysqld (mysqld 10.2.18-MariaDB-1:10.2.18+maria~bionic) starting as process 1 ...
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Uses event mutexes
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Using Linux native AIO
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Number of pools: 1
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Using SSE2 crc32 instructions
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Completed initialization of buffer pool
mysql-mailcow_1      | 2018-10-20  9:06:34 140711232984832 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Highest supported file format is Barracuda.
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: 128 out of 128 rollback segments are active.
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql-mailcow_1      | 2018-10-20  9:06:34 140711976839104 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql-mailcow_1      | 2018-10-20  9:06:35 140711976839104 [Note] InnoDB: 5.7.23 started; log sequence number 1620024
mysql-mailcow_1      | 2018-10-20  9:06:35 140711064213248 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql-mailcow_1      | 2018-10-20  9:06:35 140711064213248 [Note] InnoDB: Buffer pool(s) load completed at 181020  9:06:35
mysql-mailcow_1      | 2018-10-20  9:06:35 140711976839104 [Note] Server socket created on IP: '::'.
mysql-mailcow_1      | 2018-10-20  9:06:35 140711976839104 [Warning] 'proxies_priv' entry '@% root@eb630873aa72' ignored in --skip-name-resolve mode.
mysql-mailcow_1      | 2018-10-20  9:06:35 140711790589696 [Note] Event Scheduler: scheduler thread started with id 6
mysql-mailcow_1      | 2018-10-20  9:06:35 140711976839104 [Note] mysqld: ready for connections.
mysql-mailcow_1      | Version: '10.2.18-MariaDB-1:10.2.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
root@la:/opt/mailcow-dockerized# iptables -L -vn
Chain INPUT (policy ACCEPT 149 packets, 19112 bytes)
 pkts bytes target     prot opt in     out     source               destination         
  154 19429 MAILCOW    all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
 2846  654K MAILCOW    all  --  *      *       0.0.0.0/0            0.0.0.0/0           
19488 2661K DOCKER-USER  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
19488 2661K DOCKER-ISOLATION-STAGE-1  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
13642 2147K ACCEPT     all  --  *      br-623339d56dce  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
 1056 69456 DOCKER     all  --  *      br-623339d56dce  0.0.0.0/0            0.0.0.0/0           
 4790  445K ACCEPT     all  --  br-623339d56dce !br-623339d56dce  0.0.0.0/0            0.0.0.0/0           
 1000 66376 ACCEPT     all  --  br-623339d56dce br-623339d56dce  0.0.0.0/0            0.0.0.0/0           
 2573  524K ACCEPT     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
   63  3780 DOCKER     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0           
 2446 5360K ACCEPT     all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  docker0 docker0  0.0.0.0/0            0.0.0.0/0           

Chain OUTPUT (policy ACCEPT 177 packets, 32183 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.2           tcp dpt:12345
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.2           tcp dpt:4190
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.2           tcp dpt:995
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.2           tcp dpt:993
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.2           tcp dpt:143
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.2           tcp dpt:110
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.4           tcp dpt:587
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.4           tcp dpt:465
    3   140 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.4           tcp dpt:25
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.7           tcp dpt:3306
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.8           tcp dpt:443
    0     0 ACCEPT     tcp  --  !br-623339d56dce br-623339d56dce  0.0.0.0/0            172.22.1.8           tcp dpt:80

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 4790  445K DOCKER-ISOLATION-STAGE-2  all  --  br-623339d56dce !br-623339d56dce  0.0.0.0/0            0.0.0.0/0           
 2446 5360K DOCKER-ISOLATION-STAGE-2  all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
 187K   28M RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-ISOLATION-STAGE-2 (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       all  --  *      br-623339d56dce  0.0.0.0/0            0.0.0.0/0           
    0     0 DROP       all  --  *      docker0  0.0.0.0/0            0.0.0.0/0           
46891 9198K RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 187K   28M RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain MAILCOW (2 references)
 pkts bytes target     prot opt in     out     source               destination

jobidon on 20 Oct 2018

I can install it for you, just mail me.

Am 20.10.2018 um 18:15 schrieb paps notifications@github.com:

ok, here's what I did. First cleaning up:

docker rm $(docker ps -a -q)
docker volume prune
rm -Rf /opt/mailcow-dockerized/
then reinstall:

root@la:/opt# git clone https://github.com/mailcow/mailcow-dockerized
Cloning into 'mailcow-dockerized'...
remote: Enumerating objects: 140, done.
remote: Counting objects: 100% (140/140), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 18148 (delta 63), reused 109 (delta 61), pack-reused 18008
Receiving objects: 100% (18148/18148), 10.94 MiB | 0 bytes/s, done.
Resolving deltas: 100% (10586/10586), done.
root@la:/opt# cd mailcow-dockerized/
root@la:/opt/mailcow-dockerized# ./generate_config.sh
Press enter to confirm the detected value '[value]' where applicable or enter a custom value.
Hostname (FQDN): [mx.domain.tld]
Timezone [America/Los_Angeles]:
root@la:/opt/mailcow-dockerized# docker-compose up -d
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Creating volume "mailcowdockerized_vmail-vol-1" with default driver
Creating volume "mailcowdockerized_mysql-vol-1" with default driver
Creating volume "mailcowdockerized_mysql-socket-vol-1" with default driver
Creating volume "mailcowdockerized_redis-vol-1" with default driver
Creating volume "mailcowdockerized_rspamd-vol-1" with default driver
Creating volume "mailcowdockerized_postfix-vol-1" with default driver
Creating volume "mailcowdockerized_crypt-vol-1" with default driver
Creating mailcowdockerized_dovecot-mailcow_1 ...
Creating mailcowdockerized_dockerapi-mailcow_1 ... error
Creating mailcowdockerized_ipv6nat_1 ... done
Creating mailcowdockerized_postfix-mailcow_1 ...
Creating mailcowdockerized_sogo-mailcow_1 ...
Creating mailcowdockerized_dovecot-mailcow_1 ... done
Creating mailcowdockerized_unbound-mailcow_1 ...
Creating mailcowdockerized_clamd-mailcow_1 ...
Creating mailcowdockerized_postfix-mailcow_1 ... done
Creating mailcowdockerized_mysql-mailcow_1 ...
Creating mailcowdockerized_watchdog-mailcow_1 ...

ERROR: for mailcowdockerized_dockerapi-mailcow_1 Cannot start service dockerapi-mailcow: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused "process_linux.go:367: setting cgroup config for procHooks process caused Creating mailcowdockerized_sogo-mailcow_1 ... done
Creating mailcowdockerized_redis-mailcow_1 ... done
Creating mailcowdockerized_unbound-mailcow_1 ... done
Creating mailcowdockerized_clamd-mailcow_1 ... done
Creating mailcowdockerized_memcached-mailcow_1 ... done
Creating mailcowdockerized_mysql-mailcow_1 ... done
.oom_control: permission denied\""": unknown
Creating mailcowdockerized_php-fpm-mailcow_1 ... done
Creating mailcowdockerized_netfilter-mailcow_1 ... done
Creating mailcowdockerized_nginx-mailcow_1 ... done
Creating mailcowdockerized_rspamd-mailcow_1 ... done
Creating mailcowdockerized_acme-mailcow_1 ... done

ERROR: for dockerapi-mailcow Cannot start service dockerapi-mailcow: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused "process_linux.go:367: setting cgroup config for procHooks process caused \"failed to write 1 to memory.oom_control: write /sys/fs/cgroup/memory/docker/30accfbb9f5c9b3f20565805d804720ad6607367db34a46a1e101cd645266bb9/memory.oom_control: permission denied\""": unknown

ERROR: for watchdog-mailcow Cannot start service watchdog-mailcow: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused "process_linux.go:367: setting cgroup config for procHooks process caused \"failed to write 1 to memory.oom_control: write /sys/fs/cgroup/memory/docker/ddf5f74be5697d7d5fabb59d70f39df5bcec68ef022115077e43cbc5203f79db/memory.oom_control: permission denied\""": unknown
ERROR: Encountered errors while bringing up the project.
At this point, accessing sogo works, but the mailcow gui through https gives a strange error:

Connection to dockerapi container failed.

The following error was reported:
0 - php_network_getaddresses: getaddrinfo failed: Name does not resolve
Logs:

nginx-mailcow_1 nginx-mailcow_1 nginx-mailcow_1 ...
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 |
mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 mysql-mailcow_1 conf:103
| nginx: [emerg] host not found in upstream "rspamd" in /etc/nginx/conf.d/site.conf:103
| nginx: configuration file /etc/nginx/nginx.conf test failed
| Initializing database
| 2018-10-20 9:06:17 140427106609088 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
| PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
| To do so, start the server, then issue the following commands:
| '/usr/bin/mysqladmin' -u root password 'new-password'
| '/usr/bin/mysqladmin' -u root -h password 'new-password'
| Alternatively you can run:
| '/usr/bin/mysql_secure_installation'
| which will also give you the option of removing the test
| databases and anonymous user created by default. This is
| strongly recommended for production servers.
| See the MariaDB Knowledgebase at http://mariadb.com/kb or the
| MySQL manual for more instructions.
| Please report any problems at http://mariadb.org/jira
| The latest information about MariaDB is available at http://mariadb.org/.
| You can find additional information about the MySQL part at:
| http://dev.mysql.com
| Consider joining MariaDB's strong and vibrant community:
| https://mariadb.org/get-involved/
| Database initialized
| MySQL init process in progress...
| 2018-10-20 9:06:25 140050235230144 [Note] mysqld (mysqld 10.2.18-MariaDB-1:10.2.18+maria~bionic) starting as process 105 ...
| 2018-10-20 9:06:25 140050235230144 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Uses event mutexes
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Compressed tables use zlib 1.2.11
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Using Linux native AIO
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Number of pools: 1
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Using SSE2 crc32 instructions
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Completed initialization of buffer pool
| 2018-10-20 9:06:25 140049489954560 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Highest supported file format is Barracuda.
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: 128 out of 128 rollback segments are active.
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Creating shared tablespace for temporary tables
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
| 2018-10-20 9:06:25 140050235230144 [Note] InnoDB: Waiting for purge to start
| 2018-10-20 9:06:26 140050235230144 [Note] InnoDB: 5.7.23 started; log sequence number 1619996
| 2018-10-20 9:06:26 140049481561856 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
| 2018-10-20 9:06:26 140049481561856 [Note] InnoDB: Buffer pool(s) load completed at 181020 9:06:26
| 2018-10-20 9:06:26 140050235230144 [Warning] 'user' entry 'root@eb630873aa72' ignored in --skip-name-resolve mode.
| 2018-10-20 9:06:26 140050235230144 [Warning] 'proxies_priv' entry '@% root@eb630873aa72' ignored in --skip-name-resolve mode.
| 2018-10-20 9:06:26 140049922463488 [Note] Event Scheduler: scheduler thread started with id 6
| 2018-10-20 9:06:26 140050235230144 [Note] mysqld: ready for connections.
| Version: '10.2.18-MariaDB-1:10.2.18+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 0 mariadb.org binary distribution
| Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
| 2018-10-20 9:06:31 140049422505728 [Warning] 'proxies_priv' entry '@% root@eb630873aa72' ignored in --skip-name-resolve mode.
| 2018-10-20 9:06:31 140049422198528 [Note] mysqld (initiated by: unknown): Normal shutdown
| 2018-10-20 9:06:31 140049431205632 [Note] InnoDB: FTS optimize thread exiting.
| 2018-10-20 9:06:31 140049422198528 [Note] Event Scheduler: Killing the scheduler thread, thread id 6
| 2018-10-20 9:06:31 140049422198528 [Note] Event Scheduler: Waiting for the scheduler thread to reply
| 2018-10-20 9:06:31 140049422198528 [Note] Event Scheduler: Stopped
| 2018-10-20 9:06:31 140049422198528 [Note] Event Scheduler: Purging the queue. 0 events
| 2018-10-20 9:06:31 140049422198528 [Note] InnoDB: Starting shutdown...
| 2018-10-20 9:06:31 140049481561856 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
| 2018-10-20 9:06:31 140049481561856 [Note] InnoDB: Buffer pool(s) dump completed at 181020 9:06:31
| 2018-10-20 9:06:32 140049422198528 [Note] InnoDB: Shutdown completed; log sequence number 1620024
| 2018-10-20 9:06:32 140049422198528 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
| 2018-10-20 9:06:32 140049422198528 [Note] mysqld: Shutdown complete
| MySQL init process done. Ready for start up.
| 2018-10-20 9:06:34 140711976839104 [Note] mysqld (mysqld 10.2.18-MariaDB-1:10.2.18+maria~bionic) starting as process 1 ...
| 2018-10-20 9:06:34 140711976839104 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Uses event mutexes
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Compressed tables use zlib 1.2.11
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Using Linux native AIO
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Number of pools: 1
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Using SSE2 crc32 instructions
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Completed initialization of buffer pool
| 2018-10-20 9:06:34 140711232984832 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Highest supported file format is Barracuda.
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: 128 out of 128 rollback segments are active.
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Creating shared tablespace for temporary tables
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
| 2018-10-20 9:06:34 140711976839104 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
| 2018-10-20 9:06:35 140711976839104 [Note] InnoDB: 5.7.23 started; log sequence number 1620024
| 2018-10-20 9:06:35 140711064213248 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
| 2018-10-20 9:06:35 140711064213248 [Note] InnoDB: Buffer pool(s) load completed at 181020 9:06:35
| 2018-10-20 9:06:35 140711976839104 [Note] Server socket created on IP: '::'.
| 2018-10-20 9:06:35 140711976839104 [Warning] 'proxies_priv' entry '@% root@eb630873aa72' ignored in --skip-name-resolve mode.
| 2018-10-20 9:06:35 140711790589696 [Note] Event Scheduler: scheduler thread started with id 6
| 2018-10-20 9:06:35 140711976839104 [Note] mysqld: ready for connections.
| Version: '10.2.18-MariaDB-1:10.2.18+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
noopener" target="_blank" href="root@la">root@la:/opt/mailcow-dockerized# iptables -L -vn
INPUT (policy ACCEPT 149 packets, 19112 bytes)
prot opt in out source destination
all -- * * 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
2846 654K MAILCOW all -- * * 0.0.0.0/0 0.0.0.0/0
19488 2661K DOCKER-USER all -- * * 0.0.0.0/0 0.0.0.0/0
19488 2661K DOCKER-ISOLATION-STAGE-1 all -- * * 0.0.0.0/0 0.0.0.0/0
13642 2147K ACCEPT all -- * br-623339d56dce 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
1056 69456 DOCKER all -- * br-623339d56dce 0.0.0.0/0 0.0.0.0/0
4790 445K ACCEPT all -- br-623339d56dce !br-623339d56dce 0.0.0.0/0 0.0.0.0/0
1000 66376 ACCEPT all -- br-623339d56dce br-623339d56dce 0.0.0.0/0 0.0.0.0/0
2573 524K ACCEPT all -- * docker0 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
63 3780 DOCKER all -- * docker0 0.0.0.0/0 0.0.0.0/0
2446 5360K ACCEPT all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- docker0 docker0 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT 177 packets, 32183 bytes)
pkts bytes target prot opt in out source destination

Chain DOCKER (2 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.2 tcp dpt:12345
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.2 tcp dpt:4190
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.2 tcp dpt:995
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.2 tcp dpt:993
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.2 tcp dpt:143
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.2 tcp dpt:110
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.4 tcp dpt:587
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.4 tcp dpt:465
3 140 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.4 tcp dpt:25
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.7 tcp dpt:3306
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.8 tcp dpt:443
0 0 ACCEPT tcp -- !br-623339d56dce br-623339d56dce 0.0.0.0/0 172.22.1.8 tcp dpt:80

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
pkts bytes target prot opt in out source destination
4790 445K DOCKER-ISOLATION-STAGE-2 all -- br-623339d56dce !br-623339d56dce 0.0.0.0/0 0.0.0.0/0
2446 5360K DOCKER-ISOLATION-STAGE-2 all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0
187K 28M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0

Chain DOCKER-ISOLATION-STAGE-2 (2 references)
pkts bytes target prot opt in out source destination
0 0 DROP all -- * br-623339d56dce 0.0.0.0/0 0.0.0.0/0
0 0 DROP all -- * docker0 0.0.0.0/0 0.0.0.0/0
46891 9198K RETURN all -- * * 0.0.0.0/0 0.0.0.0/0

Chain DOCKER-USER (1 references)
pkts bytes target prot opt in out source destination
187K 28M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0

Chain MAILCOW (2 references)
pkts bytes target prot opt in out source destination

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

andryyy on 20 Oct 2018

I just sent you an email

jobidon on 20 Oct 2018

OpenVZ, needed remove oom_control.

andryyy on 20 Oct 2018

Same issue here with a Hetzner cloud server.

OpenVZ, needed remove oom_control.

@andryyy Could you explain it a little bit more in detail?

patrick0h on 10 Apr 2019

Hetzner does not use OpenVZ.

We cannot help without full logs.

andryyy on 10 Apr 2019

Sorry for my late reply - some business stuff to do...

I've the following setting:

Hetzner cloud server
Debian 9.8
Traefik as reverse proxy running in an own container (some different containers are working well behind this proxy e. g. whoami or a nginx containter)
Starting the Mailcow container using docker-compose up -d returns green "done" for every single item

Trying to access the mailcow website I get a 502 Bad Gateway error.

Below some logs and config files:

mailcow.conf

HTTP_PORT=8080
HTTP_BIND=127.0.0.1
HTTPS_PORT=8443
HTTPS_BIND=127.0.0.1

docker-compose.override.yml

version: '2.1'

services:
    nginx-mailcow:
      expose:
         - "80"
         - "8080"
         - "443"
         - "8443"
      labels:
        - "traefik.backend=mailcow"
        - "traefik.docker.network=traefik_proxy"
        - "traefik.enable=true"
        - "traefik.port=80"
        - "traefik.frontend.rule=Host:my.domain.tld"
      networks:
        web:

networks:
  web:
    external:
      name: traefik_proxy

Note: I commented out the two ports in the nginx-mailcow section in the docker-compose.yml file.

docker-compose logs nginx-mailcow

nginx-mailcow_1      | 2019/04/15 18:38:21 [error] 18#18: *5141 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx:8081"
nginx-mailcow_1      | 2019/04/15 18:38:21 [error] 18#18: *5141 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::3 - - [15/Apr/2019:18:38:21 +0200] "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2019/04/15 18:40:20 [error] 18#18: *5145 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.1.12, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx"
nginx-mailcow_1      | 2019/04/15 18:40:20 [error] 18#18: *5145 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.1.12, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx"
nginx-mailcow_1      | 172.22.1.12 - - [15/Apr/2019:18:40:20 +0200] "HEAD /forwardinghosts.php HTTP/1.1" 502 0 "-" "rspamd-1.9.0"
nginx-mailcow_1      | 2019/04/15 18:48:25 [error] 18#18: *5148 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx:8081"
nginx-mailcow_1      | 2019/04/15 18:48:25 [error] 18#18: *5148 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::3 - - [15/Apr/2019:18:48:25 +0200] "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2019/04/15 18:54:42 [error] 18#18: *5152 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /settings.php HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx"
nginx-mailcow_1      | 2019/04/15 18:54:42 [error] 18#18: *5152 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /settings.php HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::10 - - [15/Apr/2019:18:54:42 +0200] "HEAD /settings.php HTTP/1.1" 502 0 "-" "rspamd-1.9.0"
nginx-mailcow_1      | 2019/04/15 18:56:12 [error] 18#18: *5156 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx"
nginx-mailcow_1      | 2019/04/15 18:56:12 [error] 18#18: *5156 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::10 - - [15/Apr/2019:18:56:12 +0200] "HEAD /forwardinghosts.php HTTP/1.1" 502 0 "-" "rspamd-1.9.0"
nginx-mailcow_1      | 2019/04/15 18:58:47 [error] 18#18: *5159 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx:8081"
nginx-mailcow_1      | 2019/04/15 18:58:47 [error] 18#18: *5159 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::3 - - [15/Apr/2019:18:58:47 +0200] "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2019/04/15 19:08:14 [error] 18#18: *5163 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx"
nginx-mailcow_1      | 2019/04/15 19:08:14 [error] 18#18: *5163 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /forwardinghosts.php HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::10 - - [15/Apr/2019:19:08:14 +0200] "HEAD /forwardinghosts.php HTTP/1.1" 502 0 "-" "rspamd-1.9.0"
nginx-mailcow_1      | 2019/04/15 19:08:51 [error] 18#18: *5166 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx:8081"
nginx-mailcow_1      | 2019/04/15 19:08:51 [error] 18#18: *5166 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::3, server: _, request: "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx:8081"
nginx-mailcow_1      | fd4d:6169:6c63:6f77::3 - - [15/Apr/2019:19:08:51 +0200] "GET /forwardinghosts.php?host=141.98.10.36 HTTP/1.1" 502 150 "-" "curl/7.58.0"
nginx-mailcow_1      | 2019/04/15 19:12:01 [error] 18#18: *5170 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /settings.php HTTP/1.1", upstream: "fastcgi://[fd4d:6169:6c63:6f77::d]:9001", host: "nginx"
nginx-mailcow_1      | 2019/04/15 19:12:01 [error] 18#18: *5170 connect() failed (111: Connection refused) while connecting to upstream, client: fd4d:6169:6c63:6f77::10, server: _, request: "HEAD /settings.php HTTP/1.1", upstream: "fastcgi://172.22.1.9:9001", host: "nginx"

Docker-Compose for Sogo and PHP returns

sogo-mailcow_1       | Waiting for database to come up...
sogo-mailcow_1       | Waiting for database to come up...
php-fpm-mailcow_1    | Waiting for SQL...
php-fpm-mailcow_1    | Waiting for SQL...

Running a mysql_upgrade by using source mailcow.conf; docker-compose exec mysql-mailcow mysql_upgrade -uroot -p${DBROOT} returns

Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
FATAL ERROR: Upgrade failed

Do you have any ideas?
Edit: It's a clean install - also OS image

patrick0h on 15 Apr 2019

But if it's clean and fresh and perfect, every setup would be affected. :-/

andryyy on 15 Apr 2019

So you recommend a second try from scratch?

patrick0h on 15 Apr 2019

Getting this exact same error too when trying to put another container containing a reverse proxy in front of mailcow.

Seems to happen when exposing a non-mailcow container to the mailcow network.

p1u3o on 19 Apr 2019

Hm, after updating mailcow i have also this problem. I run mailcow admin behind hiawatha as reverse proxy and it worked well. I use debian 9 on a hetzner root server. Firewall seems to have no effect. I installed mailcow fresh in April 2019 and it was my first update ...

Both versions of command for updating database dont work.

Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
FATAL ERROR: Upgrade failed

From logs:

php-fpm-mailcow_1 | Waiting for SQL...

mysql-mailcow_1 | 2019-06-02 19:48:54 140447773824320 [Note] Server socket created on IP: '::'.
mysql-mailcow_1 | 2019-06-02 19:48:54 140447773824320 [Warning] 'proxies_priv' entry '@% root@9c61442b003e' ignored in --skip-name-resolve mode.
mysql-mailcow_1 | 2019-06-02 19:48:54 140447137552128 [Note] Event Scheduler: scheduler thread started with id 6
mysql-mailcow_1 | 2019-06-02 19:48:54 140447773824320 [Note] mysqld: ready for connections.

If I read about reinstalling mailcow: I just have some user data in my mailcow. I am not familar with docker so I dont know how to save and how to restore the user data in the database ... so I will try to use reinstall from my backup and wait until there is a solution for the update auf mailcow.

mamair on 2 Jun 2019

It can also take a while to update the db schema. Watchdog would tell you about this.

@mamair if you are happy with it, mail me and I will check it => [email protected]

andryyy on 2 Jun 2019

Thnks for quick answer. If I get a f"FATAL ERROR: Upgrade failed" I think the update process has stopped.

If I start update script again, the update process starts again. So it was uncomplete also from the messages I get It seemed the update was complete ... the error message comes after creating containers ...

remote: Enumerating objects: 33, done.
remote: Counting objects: 100% (33/33), done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 33 (delta 8), reused 18 (delta 7), pack-reused 0
Unpacking objects: 100% (33/33), done.
From https://github.com/mailcow/mailcow-dockerized
5f8dd69a..af46a93e master -> origin/master
…..
10 files changed, 50 insertions(+), 6 deletions(-)
create mode 100755 data/Dockerfiles/dovecot/clean_q_aged.sh
….
Fixing PHP-FPM worker ports for Nginx sites…
….
Creating mailcowdockerized_rspamd-mailcow_1 ... done
Creating mailcowdockerized_ipv6nat-mailcow_1 ... done
Collecting garbage...Found tag 1.37 for mailcow/phpfpm, which is older than the current tag 1.38 and should be deleted.
Found tag 1.77 for mailcow/dovecot, which is older than the current tag 1.78 and should be deleted.
Run the following command to delete unused image tags:

docker rmi mailcow/phpfpm:1.37 mailcow/dovecot:1.77

docker rmi mailcow/phpfpm:1.37 mailcow/dovecot:1.77

Error response from daemon: conflict: unable to remove repository reference "mailcow/dovecot:1.77" (must force) - container c8468be491f7 is using its referenced image a4ca4c97a85e

I think I will try a fresh installation and maybe some emails of weekend got lost. And I will make next update if i know enough about containerized mailcow.

mamair on 2 Jun 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] on 1 Aug 2019

Oooops, had not time for feedback: In my case problem solved. I change password in setting file - I wanted to change subdomain of the webinterface - and it seems that updating means to rebuild container with the current settings but "restaring" containers dont rebuild container with current settings. I didnt know the difference. Maybe a short note in settings file or elsewere would be usefull for people like me who are not firm with containers.

mamair on 9 Aug 2019

Thanks for your feedback. :)

andryyy on 9 Aug 2019

Was this page helpful?

0 / 5 - 0 ratings