Troubleshooting ZStack Cloud API and SDK call issues
Issue/Introduction
This article applies to access failures, authentication failures, unexpected response codes, polling timeouts, insufficient permissions, and parameter errors when you call ZStack Cloud APIs through curl, Postman, a Java or Python SDK, or a third-party system. These issues are usually related to the request address, port, HTTP method, password encryption, asynchronous API polling, proxy mapping, or account permissions.
Symptoms
- A Java SDK call returns 405 and reports an incorrect request method.
- An asynchronous API returns a polling address, but subsequent calls to that address return
Request timed out. - A subaccount call to a quota, IPsec, or enterprise-management API reports a permission or session issue.
- An API returns status code 202, 503, or 404, and the caller incorrectly treats the response as an API failure.
Sign in to view the rest of this article, plus more troubleshooting and solution know-how.
Sign in