Unable to fetch key provider details on host.get provider info error, please check the health logs.
VMware vSAN 7.x
VMware vSAN 8.x
VMware vSAN 9.x
The issue is seen when there is a connectivity issues between vCenter and ESXi host when there is Native Key Provider used for encryption.
Upon checking the ESXi logs /var/log/kmxa.log shows the below events.
2025-07-16T06:38:06.822Z info kmxa[2099193] [Originator@6876 sub=Default opID=opId-vmcrypt-vapi-2025-07-16T06:38:06.475157Z-9f] Invoke-MethodId: com.vmware.esx.trusted_infrastructure.kms.providers.list2025-07-16T06:38:06.856Z info kmxa[2099190] [Originator@6876 sub=Default opID=opId-vmcrypt-vapi-2025-07-16T06:38:06.475157Z-9f] Invoke-MethodId: com.vmware.esx.trusted_infrastructure.kms.providers.create2025-07-16T06:38:06.856Z error kmxa[2099190] [Originator@6876 sub=Default opID=opId-vmcrypt-vapi-2025-07-16T06:38:06.475157Z-9f] MethodResult [FAIL] (MethodId:com.vmware.esx.trusted_infrastructure.kms.providers.create),Error:--> com.vmware.vapi.std.errors.unauthorized--> No messages!
/var/log/vmware/vpxd/vpxd.log the events would be reported.2025-07-16T06:38:06.843Z info vpxd[52504] [Originator@6876 sub=vpxLro opID=sps-Main-217991-924-218018-c9] [VpxLRO] -- FINISH lro-6741697182025-07-16T06:38:06.860Z error vpxd[26140] [Originator@6876 sub=CryptoManager opID=SWI-3162604f] Failed to call vAPI to create native key provider with provider ID NKP-Key on host [vim.HostSystem:host-1625,esxi.example.com]:--> {--> "ERROR": {--> "com.vmware.vapi.std.errors.unauthorized": {--> "data": {--> "OPTIONAL": null--> },--> "error_type": {--> "OPTIONAL": "UNAUTHORIZED"--> },--> "messages": []--> }--> }--> }2025-07-16T06:38:06.860Z error vpxd[26140] [Originator@6876 sub=CryptoManager opID=SWI-3162604f] Failed to invoke "Providers.Create" on host esxi.example.com.--> Error:--> com.vmware.vapi.std.errors.unauthorized--> No messages!
In order to resolve the issue, the communication issues between the vCenter and ESXi should be fixed.
Check for the network communication issues between vCenter and host.
Disconnect the host from vCenter and reconnect.
Once the host show in disconnected state, reconnect the host back on vCenter server.
Also, we can restart the vCenter services and check for the issue. refer: Stop, Start or Restart Services on vCenter Server 7.x/8.x