Hello, I'm installing Mailcow in a test environment using a fresh install of Ubuntu Server 22.04.5. I then followed the instructions over here: docs.mailcow.email/getstarted/install Only other thing I did with this operating system was to install Neofetch, Network Manager, and some other service to get a static IP working. I also installed SSH on it. The rest is whatever the default is for the Ubuntu Server. When using the 'docker compose up -d' command, everything goes up except for the Unbound-Mailcow-1 container. It appears to be not be able to connect to anything using the 'docker compose logs --tail=whatever' command. Screenshot below: [upl-image-preview uuid=c9b0f0c0-1360-4c4a-8677-f4f3b0c5c629 url=https://community.mailcow.email/assets/files/2024-12-30/1735588492-985555-image.png alt={TEXT?}] I did have ICMP blocked by the firewall, but I removed it. Despite that, the above issue still occurs. Screenshot below to prove that I can ping and resolve domain names from the same server: [upl-image-preview uuid=a83f74e0-a28b-4173-b602-6e51a88ff4bb url=https://community.mailcow.email/assets/files/2024-12-30/1735588779-825911-image.png alt={TEXT?}] My suspicion is that a default gateway needs to be set up proper. Please see the below screenshot after using the 'ip a' command [upl-image-preview uuid=529dc7c7-a01b-4602-8425-ca3a71b286ee url=https://community.mailcow.email/assets/files/2024-12-30/1735588887-119276-image.png alt={TEXT?}] There's a lot more virtual Ethernet addresses than that, which I'm not sure what they are for. Anyway, the IP that the br-mailcow interface is taking is what should be the default gateway. I looked through the mailcow.conf and the docker-compose.yml files to see where I can configure this interface, assuming that the unbound container is using this interface to connect to the outside world, but I am unable to find it. My guess is that it is trying to ask itself where 1.1.1.1 is instead of asking my router. I've tried manually adding an ipv4_address field for that interface, but it didn't like my formatting. Below is the default config for that br-mailcow interface. Let me know if it needs to be changed. [upl-image-preview uuid=eefac0e0-b5c7-4164-a7a0-2d92fc898808 url=https://community.mailcow.email/assets/files/2024-12-30/1735590324-84800-image.png alt={TEXT?}] FYI, I'm not very experienced in Linux, so giving any commands is more helpful then telling me to 'do something', if that makes sense. Also, from looking at other threads, folks commonly ask for the watchdog logs. I don't know where it is. I don't see it under /var/log or in the mailcow directory. Please guide me to it if you need it. I appreciate any assistance. The matter is not urgent.

Unbound-Mailcow-1 is unhealthy

DENMON

Hello,

I’m installing Mailcow in a test environment using a fresh install of Ubuntu Server 22.04.5. I then followed the instructions over here: docs.mailcow.email/getstarted/install

Only other thing I did with this operating system was to install Neofetch, Network Manager, and some other service to get a static IP working. I also installed SSH on it. The rest is whatever the default is for the Ubuntu Server.

When using the ‘docker compose up -d’ command, everything goes up except for the Unbound-Mailcow-1 container. It appears to be not be able to connect to anything using the ‘docker compose logs –tail=whatever’ command.

Screenshot below:

I did have ICMP blocked by the firewall, but I removed it. Despite that, the above issue still occurs. Screenshot below to prove that I can ping and resolve domain names from the same server:

My suspicion is that a default gateway needs to be set up proper. Please see the below screenshot after using the ‘ip a’ command

There’s a lot more virtual Ethernet addresses than that, which I’m not sure what they are for. Anyway, the IP that the br-mailcow interface is taking is what should be the default gateway. I looked through the mailcow.conf and the docker-compose.yml files to see where I can configure this interface, assuming that the unbound container is using this interface to connect to the outside world, but I am unable to find it. My guess is that it is trying to ask itself where 1.1.1.1 is instead of asking my router.

I’ve tried manually adding an ipv4_address field for that interface, but it didn’t like my formatting. Below is the default config for that br-mailcow interface. Let me know if it needs to be changed.

FYI, I’m not very experienced in Linux, so giving any commands is more helpful then telling me to ‘do something’, if that makes sense. Also, from looking at other threads, folks commonly ask for the watchdog logs. I don’t know where it is. I don’t see it under /var/log or in the mailcow directory. Please guide me to it if you need it.

I appreciate any assistance. The matter is not urgent.

D4niel

It looks like you manually changed something in your docker networking config. The ip address of br-mailcow should be within the 172.22.1.0/24 range, but yours shows 192.168.1.0/24.
This will obviously not work if your actual ip addresses and the ip addresses in your config don’t match.

I think you could change the IP in that config snippet, but it would be better if you reverted whatever you changed.

DENMON

Yes, I forgot I did change that in the conf file. I assumed the IPv4 range had to match my VLAN but that was incorrect!

After reverting that change, it is now healthy, and I can access it via HTTPS.

Thanks!