Email has not been working for about a week

[SirFiChi]

Hello Cloudron Team,
perhaps you have a solution. My Cloudron instance seems to have had problems with the mail server for about a week.
I have been getting backup errors for a while now. Then a week ago the server hung up and I had to hard reboot the server.
I think since then the installation is no longer able to receive or send mails.

I get a lot of red exclamation marks in the DNS status.
In the email event logs DNS lookup errors, delivery errors to the MXs and messages with “Connection denied” for the host.

The domains and settings for the DNS are at 1blu.de.
The Cloudron installation is at contabo.de.
The configuration has run without any problems so far.

Do you have a solution for this problem?
Many thanks for your support.

Floh

[fbartels]

On the server there is a file called ‘box.log’, check it if there are any errors when your backup is running and the dns settings of your mailserver get checked.

[girish]

@SirFiChi said in Email has not been working for about a week:

I think since then the installation is no longer able to receive or send mails.

Is Email server running in Services ? Otherwise, restart and try.

I get a lot of red exclamation marks in the DNS status.

Is the DNS server (unbound) running in Services ? Otherwise, restart and try.

[girish]

You can also run cloudron-support --troubleshoot on the server to check for obvious/common issues.

[SirFiChi]

Thanks for the replies.
There is no Service for the DNS?

I'll try to connect to my server and try the troubleshoot...

[SirFiChi]

:~# cloudron-support --troubleshoot
[OK] node version is correct
[OK] docker is running
[OK] MySQL is running
[OK] nginx is running
[OK] box is running
[OK] unbound is running
[FAIL] Could not load dashboard domain.
Hairpin NAT is not working. Please check if your router supports it
:~#

[nebulon]

Can you go through https://docs.cloudron.io/troubleshooting/#hairpin-nat since Hairpin NAT seems to be the issue then.

[SirFiChi]

Interesting.
I contacted the provider and told about the problem. They wanted screenshots. After another test all works fine again.
Thanks for your help!