Unable to connect to Site Recovery Manager Server at https. Reason 30,000 milliseconds timeout on connection http-outgoing

Products

• VMware Live Recovery

Issue/Introduction

Symptom:

• SRM UI throws this error. 

ERROR
Unable to connect to Site Recovery Manager Server at https://srm.broadcom.com:443/drserver/vcdr/vmomi/sdk. Reason: https://srm.broadcom.com:443/drserver/vcdr/vmomi/sdk c-116570 [ACTIVE]"
30,000 milliseconds timeout on connection http-outgoing-116570 [ACTIVE]
Operation ID: c7445536-0143-4fb4-b7c8-de9b558e156b
6/17/25, 11:58:41 AM -0400

When you click on Recovery steps underneath a recovery plan, it throws the error above. 

• Alert on SRM UI display error during pairing as,
  
  ERROR
Unable to connect to Site Recovery Manager Server at https://srm.broadcom.com:443/drserver/vcdr/vmomi/sdk.
Reason:java.net.ConnectException: Timeoutconnecting to [srm.broadcom.com/##.###.##.###:443]Timeout connecting to [srm.broadcom.com/##.###.##.###:443]
  
  Also, displays error as below,
  
  ERROR
Unable to connect to Site Recovery Manager Server at https://MZ-VV-AP-415.corp.bradesco.com.br:443/drserver/vcdr/vmomi/sdk.
Reason:java.net.NoRouteToHostException: No route to host
No route to host

Environment

VMware Site Recovery Manager 8.x

VMware Live Site Recovery 9.x

Cause

• Port 443 needs to be open from SRM to local and remote VC.
  Refer - Network Ports for Site Recovery Manager
  
  
• vCenter was updated to the latest patch but SRM appliance wasn't reconfigured. 

From the /opt/vmware/support/logs/dr-client/dr.log:

com.vmware.vim.vmomi.client.exception.ConnectionException: Unable to connect to Site Recovery Manager Server at https://srm.broadcom.com:443/drserver/vcdr/vmomi/sdk. Reason: https://srm.broadcom.com:443/drserver/vcdr/vmomi/sdk invocation
failed with "java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-41894 [ACTIVE]"
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:261)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.setResponseError(HttpExchangeBase.java:356)
        at com.vmware.vim.vmomi.client.http.impl.HttpAsyncExchange$1$1.invokeWithinScope(HttpAsyncExchange.java:131)
        at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:24)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.lambda$wrap$1(ThreadContext.java:55)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.execute(ThreadContext.java:209)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.execute(ThreadContext.java:185)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.setupContext(ThreadContext.java:76)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.setupContext(ThreadContext.java:105)
        at com.vmware.dr.ui.tools.utilities.ExecutorUtils.lambda$wrap$1(ExecutorUtils.java:36)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-41894 [ACTIVE]
        at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.timeout(HttpAsyncRequestExecutor.java:387)
        at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:98)
        at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:40)
        at org.apache.http.impl.nio.reactor.AbstractIODispatch.timeout(AbstractIODispatch.java:175)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.sessionTimedOut(BaseIOReactor.java:261)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.timeoutCheck(AbstractIOReactor.java:506)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:211)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
        at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591)
        ... 1 more

Port connectivity check fails to connect remote and target SRM on port 443

Unsuccessful connection,

root [ /####/#### ]# curl -v telnet: //##.##.###.##: 443
Trying ##.###.##.###:443 ...
connect to ##.###.##.### port 443 failed: Connection timed out
Failed to connect to ##.###.##.### port 443 after 129230 ms: Couldn't connect to server
* Closing connection 0 curl: (28) Failed to connect to ##.###.##.### port 443 after 129230 ms: Couldn't connect to server

Resolution

It's essential to re-register external and third-party solutions with vCenter after the SSL certificate has been refreshed following an upgrade or migration.

• Allow port 443 across the sites, Bi-directional communication between Site Recovery Manager servers.
  Refer Network Ports for Site Recovery Manager
   
• Reconfigure the Site Recovery Manager Appliance
  
  
• Reconnect the site pair.

This should resolve the issue, if it doesn't and you still need assistance, submit a case with Broadcom Support.