- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
an hour ago
Nutanix Discovery Error – Troubleshooting Steps
1. No Nutanix Cluster is found
Primary cause: Prism Central address parameter passing error, causing the URL to become https://No Source.... Troubleshooting: In the "Serverless Execution Pattern", set "Use extended parameters" to false, forcing the use of the correctly configured PRISM_Address.
Secondary cause: The credentials do not have read-only API permissions for Prism Central and Prism Element, or the SSL certificate is not trusted, causing API calls to fail silently
2. HTTP 401 Unauthorized
This is the error you saw in your earlier logs, where authentication was rejected.
Troubleshooting: Verify that the Basic Auth account has read-only access to the API (such as /api/nutanix/v3/clusters/list). It is recommended to manually test the connection using Postman to confirm whether the credentials are valid.
3. Certificate Path Error
The MID Server cannot establish a trusted connection with Nutanix, and the logs will show certificate path errors.
Troubleshooting: Import the Nutanix Prism certificate into the MID Server's Java truststore (cacerts), and restart the MID Server service to take effect.
4. API connection timeout
Cause Firewall or network latency
Check whether Prism Element or Prism Central is reachable.
Prism Element: https://<Cluster-VIP>:9440
Prism Central: https://<Prism-Central-IP>:9440
Thank You
LinkedIn : https://www.linkedin.com/in/harish-baisla-8895aa22a/
ServiceNow Community Rising Star 2024 , 2025 and 2026