Initiating a file upload to either a content library or datastore, or attempting to deploy an OVF or OVA template, might result in the operation failing with an error:

The operation failed for an undetermined reason. Typically this problem occurs due to certificates that the browser does not trust. If you are using self-signed or custom certificates, open the URL below in a new browser tab and accept the certificate, then retry the operation.

https://target-ip

VMware vSphere ESXi 6.5
VMware vCenter Server 6.7.x
VMware vSphere ESXi 6.7
VMware vCenter Server 6.5.x
VMware vCenter Server 7.0.x

To resolve this issue follow the solutions below as per the scenario.

Solution 1: 

1. From a client system Web browser, go to the base URL of the vCenter Server system or the vCenter Server Virtual Appliance without appending port numbers or 'vsphere-client' extension.
   For example:
   https://vcenter.domain.com/  Enter your vCenter FQDN details on a Web browser 
2. Click the Download trusted root CA certificates link at the bottom of the grey box on the right and download the file. 

 

note: if you receive a new tab with a lot of text by clicking on Download trusted root CA, open the same link on a different browser or do a right-click and select the option Save as...

3. Change the extension of the file to .zip. The file is a ZIP file of all root certificates and all CRLs in the VMware Endpoint Certificate Store (VECS).
4. Extract the contents of the  ZIP file. The result is a .certs folder that contains two types of files. Files with a number as the extension (.0, .1, and so on) are root certificates. Files with an extension that starts with an r (.r0,. r1, and so on) are CRL files associated with a certificate.
5. Install the certificate files as trusted certificates by following the process that is appropriate for your operating system.
   For most Microsoft Windows systems, you can follow the instructions at Manage trusted root certificates.

 

Solution 2: 

In some cases the Serenity database becomes corrupt, reset Serenity DB to resolve the issue.

The impact of resetting the Serenity database is very tiny -- when you next connect to the vCenter through the web client, it will take a few seconds longer than usual while the system rebuilds that database.

Follow the below steps:

• The below path is applicable for prior to vSphere 6.0 version appliance:
  # service vsphere-client stop
  rm -rf /etc/vmware-vsphere-client/SerenityDB/serenity/*
  # service vsphere-client start
• For vSphere 6.5.x and vSphere 6.7.x follow the below path
  # service-control --stop vsphere-client
  rm -rf /storage/vsphere-client/SerenityDB/serenity/*
  # service-control --start vsphere-client
• In Windows:
  # cd <C:\Program Files\VMware\vCenter Server\bin>
  # service-control --stop vspherewebclientsvc
• Delete the contents of the folders below.
  <C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity>
  #service-control --start vspherewebclientsvc 

 

 

If the issue persists despite these resolutions, file a Support Request with VMware Support and note this KB article ID (2147256) in the problem description. For more information, see Filing a Support Request in Customer Connect (2006985).

VMware Skyline Health Diagnostics for vSphere - FAQ

How to download and install vCenter Server root certificates to avoid Web Browser certificate warnings
Deploying vSphere Replication 6.5.x fails with Error: "The operation failed for an undetermined reason. Typically the problem occurs due to certificates that the browser does not trust."