Backup Server keeps becoming "Untrusted" after upgrade 13.0.1.180, jobs fail

[davemann]

Hello -

After upgrading to 13.0.1.180, my backup server keeps getting marked as "Untrusted" in the console, and once that happens, jobs begin to fail. The fingerprint of the certificate is not changing.



It happens every day. I "Trust" the server in the morning, and at some point during the evening, it goes "Untrusted" again, and jobs that are running start to fail, and future jobs all fail with:

Code: Select all

Processing <vm name redacted> Error: One or more errors occurred. (The remote certificate was rejected by the provided RemoteCertificateValidationCallback.)
Error: One or more errors occurred. (The remote certificate was rejected by the provided RemoteCertificateValidationCallback.)
Processing finished with errors at 12/17/2025 10:33:47 PM

I have logged case 07925631 and submitted a few log bundles, but I don't think anyone has any ideas yet on this.

Anyone else having the same issue?

[Dima P.]

Hello Dave,

Thank you for your report! Could you please confirm whether the machine listed is actually a backup server? If so, could you also let me know if the backup server is deployed as a virtual machine and whether there’s any chance it has been added to any jobs?

[Dima P.]

Dave, we’ve run several tests with the QA team and couldn’t confirm this behavior. Please continue working with the support team to pinpoint the issue.

[davemann]

Hello Dave,

Thank you for your report! Could you please confirm whether the machine listed is actually a backup server? If so, could you also let me know if the backup server is deployed as a virtual machine and whether there’s any chance it has been added to any jobs?

Yes, the server shown is a VM and backup server, and yes - it is part of a job, I have had one for a long time to backup the server itself and my Veeam One/Enterprise Manager VM's as well. This has never been a problem in the past.

I thought that this may have been the issue, so I re-ran all my failed jobs after re-trusting the server, and then re-ran the job this VM was on, expecting it to go to an Untrusted state, but it did not. Perhaps it has something to do with concurrence with other jobs, but generally - Veeam recognizes that it's a backup server, and is not processed in parallel with other tasks (it says so in the job status).

[Dima P.]

Thank you for the details! We will look into logs!

[logixcom]

Not sure if related, we are working on another issue, but I was told that Certs need to be updated after installing v13, there is a change in them that requires certs to be renewed if they have not been since v11. v12 was compatible, but v13 needs a new one, I think it was the Cert Usage attribute, can't remember. Again not sure if related or helps. I too did have a host popup as Untrusted, but did the trust and it accepted it. For what its worth, may help....