Email reports in Veeam Backup for AWS v9 have stopped sending.

[claudiohipolito]

Hello everyone,

Since July 31, 2025, email reports in VBAWS have suddenly stopped working.

We opened a support case (No. 07783506), where we were instructed to:

Install the email server’s root certificate on the appliance.

Apply the fix using the package Veeamawsbackup_9.0.1.6_amd64.deb.

Both procedures were unsuccessful. The public cloud engineer informed us that this is a known bug, and the permanent fix is expected only in version 9.1 of the appliance.

Error message:

An error occurred while attempting to establish an SSL or TLS connection. This usually means that the SSL certificate presented by the server is not trusted by the system for one or more of the following reasons:

The server is using a self-signed certificate which cannot be verified.

The local system is missing a Root or Intermediate certificate needed to verify the server's certificate.

A Certificate Authority CRL server for one or more of the certificates in the chain is temporarily unavailable.

The certificate presented by the server is expired or invalid.

The set of SSL/TLS protocols supported by the client and server do not match.
See: https://github.com/jstedfast/MailKit/bl ... -exception for possible solutions.

The customer urgently needs these reports, as they are used for audit evidence.

Is anyone else experiencing this issue?

Thanks.

Cláudio Hipólito

[nielsengelen]

Hi,

I think this can potentially be resolved by running "apt update && apt install -y ca-certificates". Have you tried this already by any chance?

[claudiohipolito]

Hi Nielsen,

We have already tried, but this procedure did not resolve the issue. I received a response from the engineer stating that this is a bug. Please, is there any other workaround for this issue? The report delivery was working until July 31, and the appliance has not had any component updates.

Thank you very much.

Best Regards,

Cláudio Hipólito

[nielsengelen]

Hi,

Sadly I can't provide an alternative solution but please continue working with support to see how this can be resolved. The next update will be available soon but I don't have a date yet for it.