Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.
"No Nutanix Cluster is found" error typically occurs because the Discovery pattern can reach the Prism Central endpoint (since port 9440 is open) but cannot successfully retrieve data from the specific API endpoints it needs to populate the CMDB.
Troubleshooting Steps:
Verify Credential Permissions:
Ensure the account used for Basic Auth has at least Read-Only access to the Prism Central API.
Crucially, if you are discovering via Prism Central, the same credentials must often be valid on the individual Prism Element instances that the central management points to.
Validate API Response via Postman:
From a machine on the same network as your MID Server, try a GET request to: https://<Prism_Central_IP>:9440/PrismGateway/services/rest/v2.0/clusters
If you get a 401 Unauthorized error, the credential lacks sufficient API permissions.
If you get a 404 Not Found, you may be targeting the wrong management endpoint or version.
Check SSL Trust on the MID Server:
Even if the port is open, the pattern may fail silently or with vague errors if the Nutanix SSL certificate is not trusted by the MID Server's Java keystore.
Import the Nutanix Prism certificate into the MID Server's /jre/lib/security/cacerts file and restart the MID Server service.
