Enhanced Replication Mappings shows Connection Errors 'Connect: bad base64 decode (PEM routines)' when running Tests.

Products

• VMware Live Recovery
• VMware vSphere ESXi

Issue/Introduction

• Enhanced Replication Mappings shows Error "Fault occurred while performing health check. Details: 'Connect: bad base64 decode (PEM routines)'"
• Synchronization between sites is working and no operational problems have been found.
• In the hms.log, you see a error message similar to:
  
  2025-xx-xx xx:xx:xx.xxx DEBUG com.vmware.hms.net.HbrAgentHealthMonitorService [hms-main-thread-9] (..hms.net.HbrAgentHealthMonitorService) [] | Ping test execution result for host 'host-27', group 'PING-GID-26bd5909-74aa-4851-8525-ec245d1ce38b', hbrBroker: '(hms.HbrBrokerEndpoint) {
dynamicType = null,
dynamicProperty = null,
ipAddress = <IP address>,
lwdPort = 31031,
lwdsPort = 32032,
certificate = -----BEGIN CERTIFICATE-----

...

-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----

...

-----END CERTIFICATE-----
}' is: '{"group":"PING-GID-26bd5909-74aa-4851-8525-ec245d1ce38b","endpoints":{"broker":{"address":"<IP address>","port":32032,"connectivity":{"tcp":true,"ssl":false},"latency":{"tcp":{"value":19557,"units":"us"}},"failReason":"Connect: bad base64 decode (PEM routines)"},"targets":[]},"sourceHostId":"host-27","sourceHostName":"<Hostname>","targetHostId":"host-27","targetHostName":"<Hostname>"}'.

Environment

vSphere Replication 9.0.2.1

Cause

If there is a certificate chain with more than 1 certificate, health check returns ssl false.

Resolution

This error can be ignored since the replication traffic is not affected by this problem.
Broadcom is aware of this issue and is working on a fix.