Skip to main content

VM backups fails with Invalid VCenter/ESXi host credentials

VM backups fails with Invalid VCenter/ESXi host credentials

Problem description

This issue occurs when the Vcenter or ESXI account used for backups is a domain account and the password is not updated in the VMware console identity provider section

Cause

Password changed and not updated on VMware console identity provider section.

Traceback

  • Error Code: ERROR 65535 / VMWARE65535

  • Message:

    • Failed to authenticate with vCenter/ESXi host: incorrect user name or password

  • Log Signature:

    [ERROR] Error <class 'apps.phoenix.vmware.exceptions.VMwareError'>: Failed to connect to vCenter/ESXi host: [Errno 65535] Incorrect user name or password. [ERROR] Failed to authenticate user 'druva_backup_user' to vSphere API. 

Resolution

  1. Locate the Disconnected vCenter/ESXi Target:Identify host/vCenter target.

    In the Druva Cloud Console, navigate to Enterprise Workloads > Protect > VMware and check the status of your configured vCenter or standalone ESXi hosts to identify which host is failing authentication.

  2. Verify Credentials Directly in vSphere:Test vSphere access.

    Attempt to log into the target vCenter Server Appliance (VCSA) or ESXi host UI directly using the identical service account credentials configured in Druva.

    Verification: Ensure the service account password has not expired, locked out, or changed in Active Directory / vCenter Local SSO.

  3. Update Credentials in the Druva Console:Update console settings.

    1. In the Druva Console, go to Protect > VMware > Configured vCenters / ESXi Hosts.

    2. Click on the affected host, select Edit, and re-enter the updated Username and Password.

    3. Reference article: Update vCenter/ESXi credentials in the Druva console.

    4. Also, manually update the Vcenter/Esxi credentials by logging in to the proxy(s) as mentioned in the below article

  4. Verify User Permissions & Privileges:Required RBAC rights.

    1. Ensure the account assigned to Druva possesses all required vSphere permissions (e.g., Datastore > Allocate space, Virtual Machine > State / Snapshot management, and vStore API / VADP access).

See also

Did this answer your question?