Skip to main content
Question

AHV Cluster and Proxy Configuration issue

  • January 6, 2026
  • 4 comments
  • 124 views
G

Hi team

This is my first attempt at this and seeing some issues.

I am deploying an AHV cluster. I am doing the proxy\backup appliance install as part of this process.
I point to the name of Prism Element cluster, not Prism Central
I get a warning that says failed to register Nutanix AHV Cluster: Failed to refresh entities.

The process completes, cluster appears and I can open the Nutanix console from the VBR console.
I verify that the specified account works

The proxy appears as unavailable. I open the Veeam backup for Nutanix AHV console.
This logs in with same account as specified.

Under Administration > Infrastructure the cluster shows its state as unavailable. But it allows me to open the cluster console from here.


When I rescan the proxy I do not get any errors.

When I rescan the AHV cluster, I see the following

Failed to scan VMs: Unknow Socket Error
Failed to scan PDs: Unknown socket Error
Failed to scan Volume Groups: Unknown socket Error
Failed to scan Protection Domains: Unknown socket Error

I am in process of verifying firewall but I believe this is something else. None of the systems use signed certificates.
I am not sure where to look next. Can someone give me some pointers re logs etc?


AOS 7.3
VBR 12.3.2

4 comments

lukas.k
Forum|alt.badge.img+13
  • lukas.k
  • Influencer
  • January 6, 2026

Hi ​@gravelrider,

To start with I’d recommend checking all required firewall ports to all required components which can be found here: https://helpcenter.veeam.com/docs/vbahv/userguide/used_ports.html?ver=9

Please make sure that any internal and external firewalls allow all required ports shown in the KB article.

 

If that’s validated please check all required permissions as shown here: https://helpcenter.veeam.com/docs/vbahv/userguide/permissions.html?ver=9#nutanix-ahv-cluster-administrator-account

 

If that also doesn’t lead to a solution I’d recommend reaching out to Veeam support to let them check what’s going on.

 

Those certificate issues are normally not a big deal - the same comes with vSphere, except you have dedicated internal / external CAs and you use signed certs. In case you don’t the behavior mentioned above is totally normal.

 

Please keep in mind that with the v13 of Veeam (should be v13.0.1 specifically) you don’t need AHV appliances anymore. You can deploy the workers directly from the VBR console. Maybe you can consider an upgrade to that version if it fits for you.

 

Best

Lukas

LK | Enterprise Architect @ Veeam Software | Former Veeam Vanguard | Security Specialist
PeteSteven
Forum|alt.badge.img+5
  • PeteSteven
  • Veeam Vanguard
  • January 7, 2026

As ​@lukas.k  already wrote, it could very well be due to firewall rules or permissions.

 

I had a similar problem recently.

Which Nutanix user did you use to add the cluster?

With the help of support, we were able to determine that a dedicated user with insufficient rights (only backup) is not sufficient, as the APIs must be accessed and the predefined rights from Nutanix are not sufficient.

Peter Steffan - My Blog: petersvirtualworld.de - Veeam Vanguard 2025
G
  • gravelrider
  • Author
  • Comes here often
  • January 7, 2026

Hi team

The issue here was that the AHV backup proxy could not resolve short names, only FQDN.
I re-added the Nutanix cluster to VBR with FQDN and it came right.
Not sure as to why that was as the other entities in domain are able to resolve with short name.

    lukas.k
    Forum|alt.badge.img+13
    • lukas.k
    • Influencer
    • January 8, 2026

    Hi team

    The issue here was that the AHV backup proxy could not resolve short names, only FQDN.
    I re-added the Nutanix cluster to VBR with FQDN and it came right.
    Not sure as to why that was as the other entities in domain are able to resolve with short name.

    Just a quote: It’s always DNS! 😊

    Depending on your config I recommend explicitly setting dns suffixes on every component (VBR Windows / Appliance and all sub-components both Windows and Linux) to avoid this.

    LK | Enterprise Architect @ Veeam Software | Former Veeam Vanguard | Security Specialist
    Terms & ConditionsAccessibility statement