Error Code
No data is returned if an API fails to be invoked. You can locate the cause of an error according to the error code of each API. When the API calling fails, HTTPS status code 4xx or 5xx is returned. The returned message body contains the specific error code and error information. If you fail to locate the cause of the error, contact customer service and provide the error code for troubleshooting.
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in Error Codes.
|
Status Code |
Error Code |
Error Message |
Measure |
|---|---|---|---|
|
400 |
CSS.0001 |
The parameter is incorrect. |
Check the parameter settings according to the returned information. |
|
500 |
CSS.0005 |
Server error. |
Contact customer service. |
|
400 |
CSS.0006 |
The request body is empty. Enter a request parameter. |
Enter the request parameters. |
|
202 |
CSS.0011 |
This operation cannot be performed because another operation is being performed on the instance or the instance is faulty. Please try again later. |
Try again later. |
|
403 |
CSS.0015 |
Resource not found or permission denied. |
Change the resource ID or check the access permission. |
|
404 |
CSS.0022 |
The instance does not exist or has been deleted. |
Change the instance ID. |
|
403 |
CSS.0032 |
The current user has no operation permissions. |
Check the permissions. |
|
400 |
CSS.0045 |
The token is incorrect. |
Obtain the token again. |
|
400 |
CSS.1112 |
The number of instances has reached the quota. |
Delete some clusters or increase the quota. |
|
400 |
CSS.3011 |
Invalid retention duration of the backup. |
Change the allowed retention duration. |
|
404 |
CSS.3027 |
The cluster does not exist. |
Check whether the cluster ID is correct. |
|
400 |
CSS.5007 |
The selected flavor does not exist. |
Check whether the specifications are correct. |
|
400 |
CSS.5009 |
The hard disk size is beyond the valid range. |
Change the disk size. |
|
400 |
CSS.5014 |
Invalid VPC ID. |
Check whether the VPC ID is correct. |
|
400 |
CSS.5015 |
Invalid subnet ID. |
Check whether the subnet ID is correct. |
|
400 |
CSS.5021 |
The VPC does not exist or does not belong to the user. |
Check whether the VPC is correct. |
|
400 |
CSS.5023 |
The security group does not exist or does not belong to the VPC. |
Check whether the security group is correct. |
|
400 |
CSS.5157 |
The CIDR does not exist or is invalid. |
Check whether there are subnets in the VPC. |
|
400 |
CSS.5036 |
The engine does not exist. |
Check whether the datastore parameter setting is correct. |
|
400 |
CSS.5047 |
The number of instances is beyond the valid range. |
Check whether the number of instances is within the range. |
|
409 |
CSS.5050 |
The cluster name already exists. |
Change the cluster name. |
|
400 |
CSS.5052 |
Invalid value of the AZ. |
Change the AZ. |
|
400 |
CSS.5055 |
Invalid flavor. |
Modify the specifications. |
|
400 |
CSS.5061 |
The hard disk type is invalid. |
Change the hard disk type. |
|
400 |
CSS.5071 |
The disk type does not match that in the XML configuration file. |
Change the hard disk type. |
|
400 |
CSS.5072 |
The security group ID is invalid. |
Change the security group ID. |
|
400 |
CSS.5074 |
The subnet does not belong to the VPC. |
Change the subnet ID. |
|
400 |
CSS.5077 |
Invalid cluster name. |
Change the cluster name. |
|
400 |
CSS.5078 |
The hard disk size is beyond the valid range. |
Change the disk size. |
|
400 |
CSS.5092 |
Invalid hard disk information. |
Modify the hard disk information. |
|
400 |
CSS.5093 |
Invalid specification information. |
Modify the specification information. |
|
412 |
CSS.5130 |
The agency name is invalid. |
Change the agency name. |
|
500 |
CSS.9999 |
Request processing failed. |
Contact customer service. |
Last Article: Status Code
Next Article: Change History
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.