2026-03-25 16:31:14,524 [srm-reactive-thread-138146] WARN com.vmware.dr.client.shared.taskMonitor.WsTaskProgressHandler #########-####-####-####-############ - Task finished with error!(dr.storage.fault.CommandFailed) { faultCause = (dr.storage.fault.SimpleAdapterFault) { faultCause = null, faultMessage = null, description = Connection to storage system "Replication_Appliance_FQDN" failed. Error : x509: certificate signed by unknown authority., fixHint = Make sure you have entered correct storage system details, port & storage system type and system is up and running. Please make sure valid certificate is available in the system. }, faultMessage = null, commandName = discoverDevices}VMware Live Recovery 9.x
The Storage Replication Adapter (SRA) Docker container retains a stale storage array certificate within its isolated filesystem cache (/srm/sra/certs/).
This cached certificate prevents the SRA from fetching the updated array certificate and validating it against the appliance OS trust store during the TLS handshake.
Log in to the Site Recovery Manager (SRM) appliance as root via SSH.
Identify the active SRA Docker container ID(s) by executing the following command:
docker ps | grep -i sra
Access the interactive shell of the identified SRA container:
docker exec -it <CONTAINER_ID> /bin/sh
Navigate to the SRA certificate cache directory:
cd /srm/sra/certs
Contact the storage system vendor to verify the currently cached certificate and remove any outdated certificate file. Once confirmed, delete the stale cached certificate files:
rm *.pem
Exit the container shell:
exit
Restart the SRM server service to force a fresh certificate retrieval during the next discovery attempt:
systemctl restart srm-server
Repeat steps 1 through 7 on the paired Site Recovery Manager appliance at the remote site.
Log in to the vSphere Client, navigate to Site Recovery, and execute the Add Array Pair wizard.