After an convergence of live recovery from version 9.0.2 to 9.0.4, there are these errors: Cannot establish a TCP connection to server at 'xxx.xxx.xxx.xxx:443'. Details: 'Error resolving version'

Products

• VMware Live Recovery

Issue/Introduction

After the administrator has completed the Recovery convergence from 9.0.2 to 9.0.4 there are errors reported

Environment

VLR 9.0.4

Cause

The hms logs on the VLR appliance shows entries like:

2025-08-28 19:06:21.515 ERROR [hms-main-thread-592] (..net.impl.PersistentConnection) {operationID=###-#######-HMS} [task=HTID-########-####-####-####-############] | Failed to connect to server xxx.xxx.xxx.xxx:443/hbr
com.vmware.vim.vmomi.client.exception.InternalException: Error resolving version
        at com.vmware.vim.vmomi.client.http.impl.HttpClient.getVersion(HttpClient.java:156) ~[vlsi-client-9.0.3.0.jar:?]
        at com.vmware.hms.net.impl.hbr.ConnectionHandlerImpl.createContext(ConnectionHandlerImpl.java:75) ~[hms.jar:?]
        at com.vmware.hms.net.impl.hbr.ConnectionHandlerImpl.doConnect(ConnectionHandlerImpl.java:114) ~[hms.jar:?]
        at com.vmware.hms.net.impl.hbr.ConnectionHandlerImpl.doConnect(ConnectionHandlerImpl.java:1) ~[hms.jar:?]
        at com.vmware.jvsl.sessions.net.impl.VmomiPingConnectionHandler.connect(VmomiPingConnectionHandler.java:93) ~[jvsl-sessions-9.0.3.0.jar:?]
        at com.vmware.jvsl.sessions.net.impl.PersistentConnection.start(PersistentConnection.java:166) ~[jvsl-sessions-9.0.3.0.jar:?]
        at com.vmware.hms.net.impl.hbr.HbrServerViewImpl.start(HbrServerViewImpl.java:114) ~[hms.jar:?]
        at com.vmware.hms.net.impl.hbr.HbrServerGatewayImpl.start(HbrServerGatewayImpl.java:241) ~[hms.jar:?]
        at com.vmware.hms.net.impl.hbr.HbrServerGatewayImpl.start(HbrServerGatewayImpl.java:222) ~[hms.jar:?]
        at com.vmware.hms.remote.SiteManagerImpl.registerHbrServerWithTask(SiteManagerImpl.java:705) ~[hms.jar:?]
        at com.vmware.hms.remote.SiteManagerImpl$3.go(SiteManagerImpl.java:554) ~[hms.jar:?]
        at com.vmware.hms.task.TaskRunnable.run(TaskRunnable.java:90) ~[hms.jar:?]
        at com.vmware.hms.HmsTaskManager.lambda$0(HmsTaskManager.java:260) ~[hms.jar:?]
        at com.vmware.hms.util.executor.LoggerOpIdConfigurator$RunnableWithDiagnosticContext.run(LoggerOpIdConfigurator.java:146) ~[hms.jar:?]
        at com.vmware.hms.util.executor.LoggerOpIdConfigurator$2.run(LoggerOpIdConfigurator.java:106) ~[hms.jar:?]
        at com.vmware.jvsl.sessions.net.impl.TlsPreservingWrapper$2.run(TlsPreservingWrapper.java:47) ~[jvsl-sessions-9.0.3.0.jar:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
        at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.util.concurrent.ExecutionException: (vmodl.fault.SystemError) {
   faultCause = null,
   faultMessage = null,
   reason = Host is in maintenance mode
}
        at java.util.concurrent.CompletableFuture.reportGet(Unknown Source) ~[?:?]
        at java.util.concurrent.CompletableFuture.get(Unknown Source) ~[?:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpClient.getVersion(HttpClient.java:154) ~[vlsi-client-9.0.3.0.jar:?]
        ... 18 more

Resolution

Take the hosts in the vCenter out of maintenance mode to resolve