containers use IPv6 after update

NicolaiVdS commented 3 years ago

Prior to placing the issue, please check following: (fill out each checkbox with an X once done)

[x] I understand that not following or deleting the below instructions will result in immediate closure and/or deletion of my issue.
[x] I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
[x] I have understood that answers are voluntary and community-driven, and not commercial support.
[x] I have verified that my issue has not been already answered in the past. I also checked previous issues.

Summary

When updating to the latest version all containers apart from the NGINX are using IPv6. resulting that some cant comunicate with eachoter and that porst arent publish (closed

Logs

Reproduction

System information

Question	Answer
My operating system	Debian 10
Is Apparmor, SELinux or similar active?	not present
Virtualization technlogy (KVM, VMware, Xen, etc - LXC and OpenVZ are not supported	KVM
Server/VM specifications (Memory, CPU Cores)	4GB Ram, 2 Core
Docker Version (`docker version`)	Docker version 20.10.2, build 2291f61
Docker-Compose Version (`docker-compose version`)	docker-compose version 1.27.3, build 4092ae5d
Reverse proxy (custom solution)	NGINX-Proxy

Output of git diff origin/master, any other changes to the code? If so, None only cert Files.
All 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:
DNS problems? :
- None that i know of docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254.

Adorfer commented 3 years ago

please explain why "ipv6 is working" is a problem. in other works: "Nonworking ipv6" is what you would expect? why?

NicolaiVdS commented 3 years ago

please explain why "ipv6 is working" is a problem. in other works: "Nonworking ipv6" is what you would expect? why?

so basicly i updated an nothing is working any more. when doing a port scan all ports are closed apart from the webpage ports.

when going to the web page i get this screen WEB UI

after checking the log its waiting for the SQL Server

and this is the SQL Server log

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

andryyy commented 3 years ago

What's in the other containers logs?

NicolaiVdS commented 3 years ago

Bellow are all the log of the docker containers.

acme its desabled i use my own cert rspamd netfilter Nginx postfix dovecot php-fpm mysql redis solr watchdog olefy memcached clamd dockerapi sogo unbound

andryyy commented 3 years ago

Looks like the mailcow.conf SQL credentials do not match the SQL volume. Never change this file please... make sure the mailcow.conf file links to .env

This probably came up when updating because the vars were newly applied to the containers then.

Never change the config credentials and keep the sym link. We never change these things with any routine we use.

Check the docs for resetting SQL. It will most likely work then.

NicolaiVdS commented 3 years ago

Looks like the mailcow.conf SQL credentials do not match the SQL volume. Never change this file please... make sure the mailcow.conf file links to .env

This probably came up when updating because the vars were newly applied to the containers then.

Never change the config credentials and keep the sym link. We never change these things with any routine we use.

Check the docs for resetting SQL. It will most likely work then.

ok now i can access the ui again but cant send/recive any mails postfix log: http://paste.debian.net/1181371/

docker-compose.yml : http://paste.debian.net/1181372/ mailcow.conf : http://paste.debian.net/1181374/

NicolaiVdS commented 3 years ago

found the issue with postfix the container was missing the - MAILCOW_HOSTNAME=${MAILCOW_HOSTNAME} in the yml file

mailcow / mailcow-dockerized