i already tried looking around existing threads and issues on github, but i wasn't able to find a solution for my issue unbound logs `root@mail:/opt/mailcow-dockerized# docker logs mailcowdockerized-unbound-mailcow-1 -f Setting console permissions... Receiving anchor key... Receiving root hints... curl: (6) Could not resolve host: www.internic.net # # # # setup in directory /etc/unbound Certificate request self-signature ok subject=CN = unbound-control removing artifacts Setup success. Certificates created. Enable in unbound.conf file to use [1705793606] unbound[1:0] notice: init module 0: validator [1705793606] unbound[1:0] notice: init module 1: iterator [1705793606] unbound[1:0] info: start of service (unbound 1.19.0). ` `root@mail:/opt/mailcow-dockerized# docker compose up -d [+] Running 13/19 ⠴ Network mailcowdockerized_mailcow-network Created 52.6s ✔ Container mailcowdockerized-solr-mailcow-1 Started 0.5s ✔ Container mailcowdockerized-memcached-mailcow-1 Started 0.9s ✔ Container mailcowdockerized-olefy-mailcow-1 Started 0.8s ✔ Container mailcowdockerized-redis-mailcow-1 Started 0.4s ✘ Container mailcowdockerized-unbound-mailcow-1 Error 52.4s ✔ Container mailcowdockerized-sogo-mailcow-1 Started 0.8s ✔ Container mailcowdockerized-dockerapi-mailcow-1 Started 0.9s ⠴ Container mailcowdockerized-clamd-mailcow-1 Created 52.5s ✔ Container mailcowdockerized-mysql-mailcow-1 Started 1.3s ✔ Container mailcowdockerized-php-fpm-mailcow-1 Started 1.0s ✔ Container mailcowdockerized-nginx-mailcow-1 Started 1.5s ✔ Container mailcowdockerized-dovecot-mailcow-1 Started 1.9s ⠼ Container mailcowdockerized-postfix-mailcow-1 Created 52.5s ⠼ Container mailcowdockerized-acme-mailcow-1 Created 52.5s ✔ Container mailcowdockerized-rspamd-mailcow-1 Started 2.2s ✔ Container mailcowdockerized-ofelia-mailcow-1 Started 2.2s ⠼ Container mailcowdockerized-netfilter-mailcow-1 Created 52.5s ⠼ Container mailcowdockerized-watchdog-mailcow-1 Created ` if you need any other information let me know

Maybe this thread can help: https://github.com/mailcow/mailcow-dockerized/issues/5649

@"ULLLUPOLLLLO"#p12743 - How did you solve it? Same problem here, after updating Mailcow Dockerized to the current january'24 release. Never had problems with updating, poked a bit around but didn't find any clues as to why oubund was unhealthy. Decided to revert back to old state saved in snapshot, to keep downtime low.

@"MascHman"#p12761 https://docs.mailcow.email/troubleshooting/debug-common_problems/#container-xy-is-unhealthy this may help but in your case it could be different you should ask or look for the answer in the forum

@"MascHman"#11081 please have a look at this thread, maybe you ran into the problem with the new ICMP check as well and have to allow it in your firewall? https://community.mailcow.email/d/2977-container-unbound-unhealthy/9

@"DocFraggle"#p12779 Thank you for your help! Since I'm unable to allow ICMP replies from the Internet past our firewall, I've disabled the unbound healthcheck with the recently intruduced variable SKIP_UNBOUND_HEALTHCHECK in mailcow.conf . Now the current release is installed and everything is working again.

It's the other way round, allow ICMP to the Internet, because the health check is pinging the Google DNS servers...

@"DocFraggle"#p12786 I know, but I'm not able to do this for now. Need to talk to some people to allow that, will revert the settings afterwards.

I have the same problem with my Mailcow Server on the Hetzner Cloud. Outbound all ports are enabled with Any IPv4 and IPv6 but Unbound is still unhealthy. I have also read the documentation that certain ports must be enabled for Unbound especially on the Hetzner Cloud but this still does not work.

@"J0K3R"#p12928 My mailcow is running in the Hetzner cloud as well, everything working fine here. Back in the days I created these firewall rules: [upl-image-preview url=https://community.mailcow.email/assets/files/2024-01-28/1706465134-232635-screenshot-20240128-190336.png] That's for outgoing traffic

mailcowdockerized-unbound-mailcow-1 is unhealthy

DocFraggle

Ah OK, jetzt hab ich den Satz kapiert: SOBALD man eine Regel hinzufügt bei “Ausgehend” ist alles was NICHT definiert ist blockiert! Darum ging ICMP nach aussen nicht bei Dir

J0K3R

DocFraggle
Ja genau.
Komisch aber wenn ich doch alle Ports TCP / UDP freigebe.
Aber ja ICMP ist ja einzeln wiederum definiert bei Hetzner.

DocFraggle

Ja, ICMP ist weder TCP noch UDP 😉

@others: Sorry for the German part, problem was a Firewall rule

« Previous Page