Error "Service Unavailable" observed when accessing VMware Aria Automation Orchestrator (vRO) UI
search cancel

Error "Service Unavailable" observed when accessing VMware Aria Automation Orchestrator (vRO) UI

book

Article ID: 439044

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite) VMware Telco Cloud Platform VMware vSphere ESXi

Issue/Introduction

  • Storage capacity is healthy (no partitions are at 100% capacity df -h)
  • The issue persists across different browsers and jump servers.
  • The vco-server-app.log file displays the following errors:

WARN vco [host='vco-app-ABC-CDE' thread='localhost-startStop-1' user='' org='' trace=''] {} com.vmware.o11n.security.auth.sso.ComponentManagerLookupService - Could not get Sso Endpoint information through service call. Fall back to local settings.
com.1n.cis.CisException: com.1n.cis.CisException: com.1n.cis.CisException: javax.net.ssl.SSLHandshakeException: Certificate is not in CA store or is invalid.
Caused by: com.vmware.o11n.cis.CisException: com.vmware.o11n.cis.CisException: javax.net.ssl.SSLHandshakeException: Certificate is not in CA store or is invalid.
        at com.vmware.o11n.cis.CisUtil.getSsoAdminUri(CisUtil.java:162) ~[o11n-cis-integration-8.14.1.jar:?]

Environment

  • vRO Version:  8.14.1, 8.18.1
  • TCP 5

Cause

  • This issue typically occurs when a certificate change is made on the authenticating vCenter Server, and the new certificate is not added to the vRO appliance's trust store.
  • Because the backend connection to the authentication provider is broken, the Orchestrator services cannot validate the Single Sign-On (SSO) endpoint, resulting in UI failures.

Resolution

Prerequisite: Ensure you have a valid backup or offline snapshot of the Orchestrator appliance before making configuration changes.

 

Import the new Certificate via CLI :

1. SSH into the Orchestrator appliance using root credentials.

2. Verify the status of the vco-app pods to confirm they are running and not degraded due to auth failures:

    # kubectl describe pod -n prelude $(kubectl get pods -n prelude | grep vco-app | awk '{print $1}')

3. Run the vRO authentication wizard to fetch and re-sync the certificates:

    # vracli vro authentication wizard

4.Provide the requested vCenter Server details and administrative credentials when prompted. This will automatically pull and import the new vCenter certificate into the Orchestrator trust store.

5. Apply the new configuration and restart the Orchestrator services:

    #/opt/scripts/deploy.sh

6. After the deployment script completes, wait a few minutes for the pods to initialize, and then attempt to access the vRO UI again.

7. If the UI is fails to load and notice the following screen, re-authenticate 

 

 

 

Steps to re-authenticate via Control Center :


If the certificates import successfully but the standard UI remains inaccessible, the authentication provider binding must be manually refreshed.

  1. Navigate to the Control Center UI: https://<vRO-FQDN>/vco-controlcenter

  2. Log in using your root credentials.

  3. Navigate to Configure Authentication Provider. If the status shows as disconnected or throws a certificate error, re-enter your configuration details and save. This forces a binding refresh.