I have been running mailcow now for a couple of months and last night i did a update and now nothing works. after somedigging found out that the Mailcow containers only bind on IPv6 and not IPv4 `root@nvds:/opt/mailcow-dockerized# netstat -tulpn | grep LISTEN tcp 0 0 127.0.0.1:7654 0.0.0.0:* LISTEN 19961/docker-proxy tcp 0 0 127.0.0.1:18983 0.0.0.0:* LISTEN 19782/docker-proxy tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 21693/docker-proxy tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 447/sshd tcp 0 0 127.0.0.1:19991 0.0.0.0:* LISTEN 20984/docker-proxy tcp 0 0 127.0.0.1:13306 0.0.0.0:* LISTEN 20695/docker-proxy tcp 0 0 127.0.0.1:8443 0.0.0.0:* LISTEN 21661/docker-proxy tcp6 0 0 :::993 :::* LISTEN 21073/docker-proxy tcp6 0 0 :::995 :::* LISTEN 21022/docker-proxy tcp6 0 0 :::9000 :::* LISTEN 859/docker-proxy tcp6 0 0 :::587 :::* LISTEN 21036/docker-proxy tcp6 0 0 :::110 :::* LISTEN 21161/docker-proxy tcp6 0 0 :::143 :::* LISTEN 21121/docker-proxy tcp6 0 0 :::80 :::* LISTEN 16937/docker-proxy tcp6 0 0 :::465 :::* LISTEN 21087/docker-proxy tcp6 0 0 :::22 :::* LISTEN 447/sshd tcp6 0 0 :::8088 :::* LISTEN 12512/docker-proxy tcp6 0 0 :::25 :::* LISTEN 21139/docker-proxy tcp6 0 0 :::443 :::* LISTEN 16925/docker-proxy tcp6 0 0 :::4190 :::* LISTEN 21010/docker-proxy tcp6 0 0 :::8000 :::* LISTEN 916/docker-proxy tcp6 0 0 :::2368 :::* LISTEN 733/docker-proxy ` Ports 8080 and 8443 are the mailcow-nginx when going to the webpage i get following message: ![502](https://i.imgur.com/bTv0Vz7.png) is there a new config option since the update that i am missing ?

Did you also update docker? There was a change few days ago about that, maybe it break if you don't have acutal docker version: https://github.com/mailcow/mailcow-dockerized/commit/64c12d50bc99a4d00e2603e9155ebd93f2c08f03

Containers bind only to IPv6 and not IPv4

NicolaiVdS

I have been running mailcow now for a couple of months and last night i did a update and now nothing works.
after somedigging found out that the Mailcow containers only bind on IPv6 and not IPv4

root@nvds:/opt/mailcow-dockerized# tcp 0 0 127.0.0.1:7654 tcp 0 0 127.0.0.1:18983 tcp 0 0 127.0.0.1:8080 tcp 0 0 0.0.0.0:22 tcp 0 0 127.0.0.1:19991 tcp 0 0 127.0.0.1:13306 tcp 0 0 127.0.0.1:8443 tcp6 0 0 :::993 tcp6 0 0 :::995 tcp6 0 0 :::9000 tcp6 0 0 :::587 tcp6 0 0 :::110 tcp6 0 0 :::143 tcp6 0 0 :::80 tcp6 0 0 :::465 tcp6 0 0 :::22 tcp6 0 0 :::8088 tcp6 0 0 :::25 tcp6 0 0 :::443 tcp6 0 0 :::4190 tcp6 0 0 :::8000 tcp6 0 0 :::2368 netstat -tulpn | grep LISTEN 0.0.0.0:* LISTEN 19961/docker-proxy 0.0.0.0:* LISTEN 19782/docker-proxy 0.0.0.0:* LISTEN 21693/docker-proxy 0.0.0.0:* LISTEN 447/sshd 0.0.0.0:* LISTEN 20984/docker-proxy 0.0.0.0:* LISTEN 20695/docker-proxy 0.0.0.0:* LISTEN 21661/docker-proxy :::* LISTEN 21073/docker-proxy :::* LISTEN 21022/docker-proxy :::* LISTEN 859/docker-proxy :::* LISTEN 21036/docker-proxy :::* LISTEN 21161/docker-proxy :::* LISTEN 21121/docker-proxy :::* LISTEN 16937/docker-proxy :::* LISTEN 21087/docker-proxy :::* LISTEN 447/sshd :::* LISTEN 12512/docker-proxy :::* LISTEN 21139/docker-proxy :::* LISTEN 16925/docker-proxy :::* LISTEN 21010/docker-proxy :::* LISTEN 916/docker-proxy :::* LISTEN 733/docker-proxy

Ports 8080 and 8443 are the mailcow-nginx when going to the webpage i get following message:
502

is there a new config option since the update that i am missing ?

omexlu

Did you also update docker?

There was a change few days ago about that, maybe it break if you don’t have acutal docker version:
mailcow/mailcow-dockerized64c12d5

NicolaiVdS

omexlu yes i did still the same result i even disabled ipv6 and yet the mysql still binds to ipv6 localhost

2021-01-15 8:18:33 0 [Note] mysqld (mysqld 10.4.17-MariaDB-1:10.4.17+maria~focal) starting as process 1 ... 2021-01-15 8:18:33 0 [Note] InnoDB: Using Linux native AIO 2021-01-15 8:18:33 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2021-01-15 8:18:33 0 [Note] InnoDB: Uses event mutexes 2021-01-15 8:18:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-01-15 8:18:33 0 [Note] InnoDB: Number of pools: 1 2021-01-15 8:18:33 0 [Note] InnoDB: Using SSE2 crc32 instructions 2021-01-15 8:18:33 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2021-01-15 8:18:33 0 [Note] InnoDB: Initializing buffer pool, total size = 24M, instances = 1, chunk size = 24M 2021-01-15 8:18:33 0 [Note] InnoDB: Completed initialization of buffer pool 2021-01-15 8:18:33 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2021-01-15 8:18:33 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2021-01-15 8:18:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-01-15 8:18:33 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-01-15 8:18:33 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2021-01-15 8:18:33 0 [Note] InnoDB: Waiting for purge to start 2021-01-15 8:18:33 0 [Note] InnoDB: 10.4.17 started; log sequence number 15525315; transaction id 198457 2021-01-15 8:18:33 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2021-01-15 8:18:33 0 [Note] Server socket created on IP: '::'. 2021-01-15 8:18:33 0 [Warning] 'proxies_priv' entry '@% root@218733fae528' ignored in --skip-name-resolve mode. 2021-01-15 8:18:33 0 [Note] mysqld: ready for connections. Version: '10.4.17-MariaDB-1:10.4.17+maria~focal' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 2021-01-15 8:18:33 6 [Note] Event Scheduler: scheduler thread started with id 6 2021-01-15 8:18:33 0 [Note] InnoDB: Buffer pool(s) load completed at 210115 8:18:33

omexlu

Run to be sure and reboot to see if the problem is solved:

sudo apt-get update && sudo apt-get upgrade
sudo apt-get autoremove && sudo apt-get autoclean && sudo apt-get clean

omexlu

Then I’m afraid I’m out of my depth, sorry, maybe someone can help you more.

NicolaiVdS

omexlu np 😃