VAMI page is not responsive or loads with incorrect details "cap.manage.update.label.username" after upgrading to Usage Meter 9.0
search cancel

VAMI page is not responsive or loads with incorrect details "cap.manage.update.label.username" after upgrading to Usage Meter 9.0

book

Article ID: 399539

calendar_today

Updated On:

Products

VMware Usage Meter

Issue/Introduction

  • After upgrading Usage Meter to 9.0, the VAMI page is unresponsive and doesn't load at all. You see 'This site cannot be reached on the browser'

In the cap-lighttpd.log (/var/log/vmware), you see the below: 

2025-05-23 07:05:24: (mod_openssl.c.1223) SSL: building cert chain for TLS server name um: error:00000000:lib(0)::reason(0)
2025-05-23 07:05:24: (mod_openssl.c.3510) SSL: 1 error:0A000179:SSL routines::cert cb error (::ffff:x.x.x.x)
2025-05-23 07:08:40: (mod_openssl.c.1223) SSL: building cert chain for TLS server name : error:00000000:lib(0)::reason(0)

When running the below openssl command on UM appliance, you see: 'No client certificate CA names sent' even though it shows CONNECTED

echo | openssl s_client -connect localhost:5480
  • VAMI UI page loads with incorrect details "cap.manage.update.label.username".

Environment

Usage Meter 9.0 

Cause

This issue occurs when the certificate chain does not include the intermediate certificate(s) and/or root certificate

Resolution

To resolve this issue, please follow the below steps:

  • Obtain all of the intermediate and root certificates
  • Concatenate them in the right order:

Intermediate certs first (in the correct order), then finally - the root certificate

Example

cat intermediate1.crt intermediate2.crt ... intermediateN.crt root.crt > ssl-ca-file.crt

 

  • Transfer the certificate file from the previous step into 
/opt/vmware/etc/lighttpd

 

  • Login as root to UM as root and open /opt/vmware/etc/lighttpd/cap-applmgmt-lighttpd.conf
  • Find the following property: ssl.ca-file and replace it's value with
/opt/vmware/etc/lighttpd/ssl-ca-file.crt

 

  • Reboot the appliance from the vCenter

You should be able to login to the VAMI page now