Updated on 2025-07-25 GMT+08:00

Error Codes

If an error occurs in API calling, no result is returned. Identify the error cause based on the error codes of each API. If an error occurs in API calling, HTTP status code 4xx or 5xx is returned. The response body contains the error code and additional information. If you are unable to identify the cause of an error, contact customer service and provide the error code so that we can help you solve the problem as soon as possible.

Format of an Error Response Body

If an error occurs during API calling, the system returns an error code and message to you. The following shows the format of an error response body:

{ 
    "error_msg": "The format of message is error", 
    "error_code": "AS.0001" 
}

In the preceding information, error_code is an error code, and error_msg describes the error.

Error Code Description

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.

Table 1 Common error codes

Status Code

Error Code

Error Message

Description

Solution

400

iMetal.0001

A request parameter contains invalid or unsupported value: %s

The request contains invalid or unsupported parameters.

Check the request body based on the returned error message.

400

iMetal.0002

Missing required parameters: %s

Required parameters are missing in the request.

Check the request body based on the returned error message.

401

iMetal.0003

Unauthorized

The request is not authenticated.

Authenticate the request again and try again.

403

iMetal.0004

Insufficient permissions

Insufficient permission.

Contact technical support to check the account permissions.

429

iMetal.0005

Too many requests

The request is overloaded.

Try again later.

Table 2 Physical server error codes

Status Code

Error Code

Error Message

Description

Solution

404

iMetal.0100

Physical servers ID not found: [{id}, ...]

The physical server ID is not found.

Check the validity of the physical server ID.

400

iMetal.0101

Physical servers state is not ready: [{id}, ...]

The physical server is not ready.

Try again later.

400

iMetal.0102

Physical servers ID already exist: [{id}, ...]

The physical server already exists.

Check parameters.

400

iMetal.0110

Inspect Physical servers error: [{id}, ...], {error details}

Hardware collection failed.

Rectify the fault based on the returned message or contact technical support engineers.

Table 3 iMetal instance error codes

Status Code

Error Code

Error Message

Description

Solution

404

iMetal.0200

Instances not found: [{id}, ...]

The iMetal instance does not exist.

Check the instance ID validity.

400

iMetal.0201

Insufficient server resources

Insufficient iMetal server resources.

Check the Max Count validity.

400

iMetal.0202

Action conflicts with instance's current state

The operation conflicts with the instance status, for example, changing the password of an instance that is being deleted.

Rectify the fault based on the returned message or contact technical support engineers.

400

iMetal.0203

Max Count is less than Min count

The value of Max count is smaller than that of Min count.

Check the validity of Max count and Min count.

400

iMetal.0204

Image not found

The image does not exist.

Check the validity of the image parameters.

400

iMetal.0205

Invalid password

Incorrect password.

Check the password validity.

400

iMetal.0206

User data exceeds size limits

The user data exceeds 32 KB.

Reduce the length of the custom script.

400

iMetal.0207

Invalid metadata configuration

Too many or too large metadata configurations.

Check the validity of the number and length of instance metadata.

404

iMetal.0230

Subnet not found: [{id}, ...]

The subnet does not exist.

Check the subnet validity.

400

iMetal.0231

Subnet unavailable: [{id}, ...]

The subnet is unavailable.

Ensure that the subnet status is ACTIVE.

400

iMetal.0232

Insufficient IP addresses in subnet

Insufficient subnet IP addresses.

Check the subnet availability.

400

iMetal.0233

Specified IP conflict in subnet

IP address conflict.

Check the validity of the IP address configuration.

400

iMetal.0234

IP specification prohibited in batch creation

IP addresses cannot be specified during batch creation.

Remove the IP address configuration parameter.

400

iMetal.0235

Create VPC ports overload

Too many VPC ports created in a batch.

Retry.