Error: "Failed to get the status for VC log collection configuration" when configuring Log Collection for vCenter in VCF 9.0.2

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Configuring Log Collection in VCF Operations 9.0.2 for a vCenter in Configurations > Log Collection show the below error:

Failed to get the status for VC log collection configuration

• In the Cloud Proxy log forwarder logs, the below error is observed

2026-06-18 06:13:08 [pool-8-thread-1] ERROR c.v.l.l.c.u.LogConfigUtil:126 - Failed to push configuration due to exception encountered while generating access key
com.vmware.loginsight.logcollection.config.exception.AuthTokenGenerationException: Failed to generate access key
        at com.vmware.loginsight.logcollection.config.VcLogCollectionConfigApplier.generateAccessKey(VcLogCollectionConfigApplier.java:444)
        at com.vmware.loginsight.logcollection.config.VcLogCollectionConfigApplier.updateSession(VcLogCollectionConfigApplier.java:465)
        at com.vmware.loginsight.logcollection.config.VcLogCollectionConfigApplier.getSession(VcLogCollectionConfigApplier.java:455)
        at com.vmware.loginsight.logcollection.config.VcLogCollectionConfigApplier.getSyslogConfigStatus(VcLogCollectionConfigApplier.java:242)
Caused by: java.util.concurrent.ExecutionException: javax.net.ssl.SSLException: org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46)
        at org.apache.http.concurrent.BasicFuture.getResult(BasicFuture.java:71)
        at org.apache.http.concurrent.BasicFuture.get(BasicFuture.java:84)
        at org.apache.http.impl.nio.client.FutureWrapper.get(FutureWrapper.java:70)
        at com.vmware.loginsight.logcollection.config.VcLogCollectionConfigApplier.generateAccessKey(VcLogCollectionConfigApplier.java:433)
        ... 19 common frames omitted
Caused by: javax.net.ssl.SSLException: org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46)

Environment

• VCF Operations 9.0.2 
• VCF Operations for Logs 9.0.2 

Resolution

• To resolve the issue, restart the Log Forwarder service on the Cloud Proxy.

docker restart vcf-log-forwarder

• Retry configuring Log Collection on the affected vCenter again.