DerLinkman
commented
1 year ago Cannot reproduce that...
Update process works as intended
Closed vigorio closed 1 year ago
DerLinkman
commented
1 year ago Cannot reproduce that...
Update process works as intended
vigorio
commented
1 year ago Dear DerLinkman, thank you for your answer. The update works but the installation doesn't work resulting in container being unhealthy. There have been no changes since April 2023 to the configs on my side, docker-compose.override.yml etc. I must admit that I use pfsense as resolver and I put the DNS values into the docker-compose.override.yml.
After struggling with my version and new version I found out that the container is unhealthy due to: "DNS resolution is not working correctly...\Maybe check your outbound firewall, as it needs to resolve DNS over TCP AND UDP!"
I don't have any firewall in the mailcow VM.
I tried to change the version of unbound to 1.18 in docker-compose.yml of 2023-09, it pulled 1.18 and started without any issues. I assume that somehow 2023-10a disrespects the DNS settings in docker-compose.override.yml and this is why the container becomes unhealthy.
DerLinkman
commented
1 year ago Could you tell me what you added to the docker compose override dns wise?
You use pfsense (externally I think) as dns resolver?
It needs to be added in the unbound config as well.
Maybe (but I can't say that without seeing what you've added) it is a faulty setup...
vigorio
commented
1 year ago version: '2.1' services:
clamd-mailcow:
dns:
- 192.168.3.1
rspamd-mailcow:
dns:
- 192.168.3.1
php-fpm-mailcow:
dns:
- 192.168.3.1
sogo-mailcow:
dns:
- 192.168.3.1
volumes:
- ./data/conf/sogo/custom-theme.css:/usr/lib/GNUstep/SOGo/WebServerResources/css/theme-default.css:z
dovecot-mailcow:
dns:
- 192.168.3.1
postfix-mailcow:
dns:
- 192.168.3.1
nginx-mailcow:
dns:
- 192.168.3.1
acme-mailcow:
dns:
- 192.168.3.1
watchdog-mailcow:
environment:
- CHECK_UNBOUND=0
dns:
- 192.168.3.1
dockerapi-mailcow:
dns:
- 192.168.3.1Tested. Yes, I needed to add following to unbound.conf
forward-zone: name: "." forward-addr: 192.168.3.1
The official documentation is inconsistent, since it mentions to use either Method A or B and not to do both! Please review and edit it. Thank you for your help!
https://docs.mailcow.email/manual-guides/Unbound/u_e-unbound-fwd/
vigorio
commented
1 year ago Closed
DerLinkman
commented
1 year ago Hm. i cannot confirm either that you need todo have both. It worked on my setup doing only once.
vigorio
commented
1 year ago Dear DerLinkman, I have tested it on a fresh VM Ubuntu 22.04 LTS with a fresh setup of mailcow. As soon as I add the unbound.conf section everything works as expected. BTW it works als with unbound.conf only. I assume that the override.yml method/file is being partially "ignored" (in terms of DNS) by the installation.
masterjanic
commented
10 months ago I also encountered this exact issue when restarting my instance of mailcow after updating to the latest version. Same error, using version 1.17.1 instead of 1.18. I also pulled the latest image of unbound and it did not work even after re-installing mailcow itself.
After some search I found out that this issue was caused by the network settings of my VM. I had disabled IPv6 in /etc/sysctl.conf which somehow caused unbound to stop working.
I don't know the exact cause of this error, but I also had IPv6 disabled in docker-compose.yml, which was working fine before...
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Operating System:
Ubuntu 22.04 LTS
Server/VM specifications:
20GB RAM, 4 cores xeon 2699v4
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
esxi
Docker version:
24.0.6
docker-compose version or docker compose version:
v2.21.0
mailcow version:
2023-10a
Reverse proxy:
HAproxy
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: