After vSphere 6.0 upgrade - remote certificate is invalid

[Ultramaroon]

Thank you for this post, Craig. I have 3 vCenter servers and a PSC, and have just created a new cert for the VMCA as an intermediate CA using the Microsoft Root CA for our Forest. Then the backups blew up. The procedure you wrote up fixed it!

[snillocecurb]

Thanks so much. This fixed my issue.

[jmauser@fau.edu]

This worked for me as well. Very fast fix. Thanks a lot

[chrometop]

Thank you this just saved me a ton of time on a Friday.

[bhnelson]

Also I'm not sure I understand why this is happening.
we have PKI issued certificates and the windows servers where B&R runs trust the certificate issued to vcenter.
is there any to add the root CAs to Veeam certificate store or something?

Same here. I replaced my fully-trusted cert with another fully-trusted cert and Veeam choked on it. Only fixed it by inadvertently clicking through the properties dialog before I found this thread. No warnings or prompts in there related to trust or certificate. Sigh.

I suspect Veeam saves a copy of vCenter's cert any any time it even changes Veeam will throw a fit, regardless of validity. Stupid.

[timothyjl]

Dec 2020 calling and thanking my Veeam ancestors for this.

[exarch]

Just posting this here for people looking for solutions to certificate issues.

I had the same error message after having changed the management network on the ESX to separate adapters, but didn't get a certificate pop-up when selecting my vSphere server in Veeam B&R and updating properties.
However, it turns out in all the backup jobs the option to make backups from storage snapshots was checked (i.e. using the Nimble storage as a backup source instead of the vSphere, if I understand correctly). This means changing the management network probably also changed something on the Nimble side which altered the certificates.
When going to the Storage Infrastructure option (not Backup Infrastructure) and editing the storage, I *DID* finally get the certificate pop-up allowing me to trust it, and after that things got moving again.

[dorr]

I experienced a similar problem related to certificates used for the storage backend. Logs showed exact same error message reported here, and the symptoms matched. [except on one point: When re-asserting configuration for vSphere, no alert regarding vSphere cert was given. vSphere cert was not the problem in my case.] Although storage-cert problem doesn't match the problem title here, I guess someone else may see this and land here.

Resolution is similar:

Browse to Storage Infrastructure
Right-click storage device
Select Edit Storage
Next through options
On Credentials page, View and install new certificate, then continue and finish
After finish, storage will be re-scanned [patience is required]

[wizdude]

many thanks for this. i had a client that has an external CA signed SSL certificate for their vCenter (they don't run an internal CA) and I just completed a certificate renewal which was fine on the vCenter side, but when i went to do a test with VEEAM it failed.

the root cause is that VEEAM was originally configured with the hostname of the vCenter server only and not the fully qualified name.

went through this procedure and now everything is rosy.

cheers

[elena.kostadinova]

Thank you very much.

[Novox]

@Craigb, thank you! Saved my bacon (I'm sure Veeam support would have advised something similar, but it was great of you to post the problem and the solution). +1 and Like from me!