If the SSL certificate of the management site service expires, or you started with a self-signed certificate and site policies require a different one, you can replace the certificate.

You are allowed to reuse the certificate used by the vRealize Automation service on port 443, or use a different one. If you are requesting a new CA-issued certificate to update an existing certificate, a best practice is to reuse the Common Name from the existing certificate.


The vRealize Automation appliance uses lighttpd to run its own management site. You secure the management site service on port 5480.


  • The certificate must be in PEM format.

  • The certificate must include both of the following, in order, together in one file:

    1. RSA private key

    2. Certificate chain

  • The private key cannot be encrypted.

  • The default location and file name is /opt/vmware/etc/lighttpd/server.pem.

See Extracting Certificates and Private Keys for more information about exporting a certificate and private key from a Java keystore to a PEM file.


  1. Log in by using the appliance console or SSH.
  2. Back up your current certificate file.
    cp /opt/vmware/etc/lighttpd/server.pem /opt/vmware/etc/lighttpd/server.pem-bak
  3. Copy the new certificate to your appliance by replacing the content of the file /opt/vmware/etc/lighttpd/server.pem with the new certificate information.
  4. Run the following command to restart the lighttpd server.

    service vami-lighttp restart

  5. Run the following command to restart the haproxy service.

    service haproxy restart

  6. Log in to the management console and validate that the certificate is replaced. You might need to restart your browser.

What to do next

Update all management agents to recognize the new certificate.

For distributed deployments, you can update management agents manually or automatically. For minimal installations, you must update agents manually.