Login Failure to Live Recovery Interface with "Unable to Authorize Access" Error

Products

• VMware Live Recovery

Issue/Introduction

Users may experience an inability to log into the Live Recovery UI via https://liverecovery.local/dr. Despite entering correct credentials, the system denies access. Investigation of the internal logs reveals that the appliance has reached its maximum connection threshold, preventing new sessions from being established.

Environments with high frequency of API calls or large-scale infrastructures can easily run into this issue.

Environment

VMware Live Recovery 9.0.4, 9.0.5 and later

Cause

This issue is caused by the exhaustion of the default client connection pool. By default, the appliance is configured with a maximum of 50 concurrent connections. When this limit is reached, often due to heavy API automation or high-density environment monitoring, the vmware-dr.log will report:

Cannot increment number of connections to <address> as max connections (50) already in use

Because the connection pool is full, the dr-client cannot communicate with the backend services, resulting in an "Unable to authorize access!" error in the dr.log.

Resolution

To resolve this issue, the connection pool limits must be increased manually within the appliance configuration.

1. Log into the Live Recovery Appliance via SSH or Console as root.

2. Navigate to the configuration directory: cd /opt/vmware/etc/va-configurator/

3. Back up the existing configuration file: cp va-configurator.xml va-configurator.xml.bak

4. Edit va-configurator.xml and locate the connection pool parameters. Update them to the following values:

   • <defaultClientPoolConnectionsPerServer>200</defaultClientPoolConnectionsPerServer>

   • <defaultClientPoolSize>500</defaultClientPoolSize>

5. Save the changes and exit the editor.

6. Reconfigure the Live Recovery Appliance through the management interface or command line to commit the new settings.

Additional Information

Customers utilizing extensive third-party integrations or custom scripting that triggers frequent API calls are more susceptible to this limitation. Increasing these values provides a larger buffer for simultaneous operations without impacting authentication.