Symptoms:
1) When using custom machine certificates, and accessing administration -> certificate management
and we see below error:
2) When reviewing vsphere_client_virgo.log
2021-09-10T14:34:01.466Z] [ERROR] http-nio-5090-exec-905 com.vmware.vise.mvc.exception.GlobalExceptionHandler Exception handled while processing request for /ui/certificate-ui/ctrl/certificates/vmca-root?endPoint=vCENTER_FQDN: com.vmware.vapi.std.errors.Unauthenticated: Unauthenticated (com.vmware.vapi.std.errors.unauthenticated) => {
messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
id = com.vmware.vapi.endpoint.method.authentication.required,
defaultMessage = Authentication required.,
args = [],
params = <null>,
localized = <null>
}],
data = <null>,
errorType = UNAUTHENTICATED,
challenge = Basic realm="VAPI endpoint",SIGN realm=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,service="VAPI endpoint",sts="https://vCENTER_FQDN/sts/STSService/vsphere.local"
Take offline snapshots of vCenter prior to proceeding. If this is an ELM configured vCenter take offline snapshots of all vCenter participating in ELM.
fixsts.sh
script This script can be downloaded from KB Ref: "Signing certificate is not valid" or "No healthy upstream" error in vCenter Server Appliancefixsts.sh
script to vCenter Server /tmp folder using WinScp.cd /tmp
chmod +x fixsts.sh
./fixsts.sh
service-control --stop --all
service-control --start --all
watch service-control --status --all
Please Note: After running fixsts.sh successfully, it might take time to sync all certificates and if we check certificate management from vCenter web console we might see below error:
Under such condition it is recommended to reboot the vcenter server once.