Unable to edit DRS cluster settings with the error "Failed to log into [uri=http://localhost:1080/wcp"
search cancel

Unable to edit DRS cluster settings with the error "Failed to log into [uri=http://localhost:1080/wcp"

book

Article ID: 435214

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When attempting to edit the DRS cluster settings in the vSphere Client, the following error message is displayed:

    Error Loading Data
    An error occurred while trying to load data. This could be due to temporary outage. You can retry the operation by clicking retry button.
    Error Details
    Failed to log into [uri=http://localhost:1080/wcp, sessionMgr=SessionManagerInfo [_sessionMgrSvcId=com.vmware.cis.session, _loginOpId=create, _logoutOpId=delete], ssoDomain=vsphere.local(########-####-####-####-############)]: com.vmware.vapi.std.errors.unauthenticated => {data=<unset>, error_type=UNAUTHENTICATED, messages=[com.vmware.vapi.std.localizable_message => {args=[], default_message=Unable to authenticate user, localized=<unset>, id=vapi.security.authentication.invalid, params=<unset>}]}




  • Errors similar to the following are recorded in the /var/log/vmware/wcp/wcpsvc.log file:

    YYYY-mm-ddTHH:MM:SS.xxxZ error wcp [ssolib/sts.go:115] [opID=lsKeepAliveHandlerFunc] STS Issue HOK request failed; err: Post "https://<VC FQDN>:443/sts/STSService": x509: certificate has expired or is not yet valid: current time YYYY-mm-ddTHH:MM:SSZ is after YYYY-mm-ddTHH:MM:SSZ

    YYYY-mm-ddTHH:MM:SS.xxxZ error wcp [lshelper/keepalive_handler.go:23] [opID=lsKeepAliveHandlerFunc] Failed to get HOK signer: Post "https://<VC FQDN>:443/sts/STSService": x509: certificate has expired or is not yet valid: current time YYYY-mm-ddTHH:MM:SSZ is after YYYY-mm-ddTHH:MM:SSZ

    YYYY-mm-ddTHH:MM:SS.xxxZ error wcp [lshelper/keepalive_handler.go:70] [opID=lsKeepAliveHandlerFunc] Invalid login in keepalive handler: %vPost "https://<VC FQDN>:443/sts/STSService": x509: certificate has expired or is not yet valid: current time YYYY-mm-ddTHH:MM:SSZ is after YYYY-mm-ddTHH:MM:SSZ

     

Cause

This issue occurs when the Machine SSL certificate of the vCenter Server has expired.

To check the validity of the Machine SSL certificate, please refer to the following KB article:

Determining expired SSL certificates in vCenter Server

Resolution

To resolve this issue, renew the Machine SSL certificate of the vCenter Server.

The Machine SSL certificate renewal can be executed by running the vCert script and selecting [3. Manage certificates] > [1. Machine SSL certificate].

For more details on utilizing the vCert tool, please refer to the following KB article:

vCert - Scripted vCenter expired certificate replacement