Aria Orchestrator UI 404 Error or Service Unavailable
search cancel

Aria Orchestrator UI 404 Error or Service Unavailable

book

Article ID: 318465

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Symptoms:

  • The VMware Aria Orchestrator web interface fails to load and returns an HTTP ERROR 404 or a "Service Unavailable" message.
  • Accessing the individual nodes directly or via the Load Balancer VIP results in the same error.
  • Running vracli service status shows all services (including vco and ui) as Started and Healthy.
  • The following error is observed in /var/log/services-logs/prelude/vco-app/file-logs/vco-server-app.log:

    com.vmware.o11n.platform.PlatformContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vcoApplicationContext' ... javax.net.ssl.SSLHandshakeException: No trusted certificate found

  •  



Environment

VMware vRealize Orchestrator 8.x

Cause

The application context fails to initialize because the Orchestrator service cannot establish a trust relationship with its configured Authentication Provider (vCenter Server or Workspace ONE Access). This typically occurs following a certificate renewal or a change in the authentication provider's FQDN/SAN that has not been synced to the Orchestrator trust store.

Resolution

Follow these steps to reset the security context and re-establish the authentication trust:

    1. Reset Authentication via CLI:

      • Log in to the Orchestrator appliance as root via SSH.
      • Execute the reset command:
        /var/lib/vco/tools/configuration-cli/bin/vro-configure.sh reset-authentication
      • Restart the configurator service:
        service vco-configurator restart
    2. Re-register the Provider in Control Center:

      • Navigate to the Control Center: https://<Your-Orchestrator-FQDN>:8283/vco-controlcenter.
      • Select Configure Authentication Provider.
      • Click Unregister to clear the existing configuration.

      • Enter the details for your Authentication Provider (vCenter or vIDM) and click Register.
      • When prompted, verify and Accept the SSL certificate to import it into the trust store.
    3. Verify Service Health:

      • Wait 2–5 minutes for the pods to re-initialize.
      • Verify the application logs no longer show "Context initialization failed."
      • Confirm the UI is accessible via https://<Your-Orchestrator-FQDN>/vco.
 
  1. Verify in vRO Control Center that after successful authentication registration, the vCenter certificate is correctly imported.