- 动态与公告
- 产品简介
- 购买指南
- 快速入门
- 操作指南
- 实践教程
- 运维指南
- 故障处理
- API 文档
- History
- Introduction
- API Category
- Instance APIs
- Listener APIs
- Backend Service APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- DescribeClsLogSet
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- DescribeLoadBalancerListByCertId
- DescribeQuota
- ModifyLoadBalancersProject
- ReplaceCertForLoadBalancers
- SetLoadBalancerClsLog
- SetLoadBalancerSecurityGroups
- SetLoadBalancerStartStatus
- SetSecurityGroupForLoadbalancers
- CreateClsLogSet
- CreateTopic
- DescribeLoadBalancerTraffic
- DescribeResources
- DescribeTaskStatus
- InquiryPriceCreateLoadBalancer
- InquiryPriceModifyLoadBalancer
- InquiryPriceRenewLoadBalancer
- Classic CLB APIs
- Making API Requests
- Load Balancing APIs
- Data Types
- Error Codes
- CLB API 2017
- 常见问题
- 服务等级协议
- 联系我们
- 词汇表
- 动态与公告
- 产品简介
- 购买指南
- 快速入门
- 操作指南
- 实践教程
- 运维指南
- 故障处理
- API 文档
- History
- Introduction
- API Category
- Instance APIs
- Listener APIs
- Backend Service APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- DescribeClsLogSet
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- DescribeLoadBalancerListByCertId
- DescribeQuota
- ModifyLoadBalancersProject
- ReplaceCertForLoadBalancers
- SetLoadBalancerClsLog
- SetLoadBalancerSecurityGroups
- SetLoadBalancerStartStatus
- SetSecurityGroupForLoadbalancers
- CreateClsLogSet
- CreateTopic
- DescribeLoadBalancerTraffic
- DescribeResources
- DescribeTaskStatus
- InquiryPriceCreateLoadBalancer
- InquiryPriceModifyLoadBalancer
- InquiryPriceRenewLoadBalancer
- Classic CLB APIs
- Making API Requests
- Load Balancing APIs
- Data Types
- Error Codes
- CLB API 2017
- 常见问题
- 服务等级协议
- 联系我们
- 词汇表
Note：
This is a legacy API and may be deprecated in the future. We recommend using CLB API 3.0. The updated version is more standardized with significantly reduced access latency.
Features
The code (error code) in the response body indicates the result of the call to a TencentCloud API. It is a common error code applicable to all APIs. If code is 0, the call succeeded; otherwise, the call failed, and you can determine the cause of the error and take corresponding actions based on the list of common error codes.
Sample:
{
"code": "5100"
}Common Error Codes
| Error Code | Description | Action |
| 4000 | Invalid request parameter | A required parameter is missing or the parameter value is incorrectly formatted. For error message, see the `message` field in error description. |
| 4100 | Identity verification failed | Identity verification error. It’s usually caused by errors in signature calculation. |
| 4101 | Unauthorized API calls | The sub-account is not authorized by the root account to use this API. Please contact the root account admin for the permission. |
| 4102 | Unauthorized access to resources | The sub-account is not authorized by the root account to access the specified resource. Please contact the root account admin for the permission. |
| 4103 | Unauthorized access to resources under the current API | The sub-account is not authorized by the root account to access the specified resource operated on by this API. Please contact the root account admin for the permission. |
| 4104 | The key does not exist | The key used for the request does not exist. Please check and try again. |
| 4105 | Incorrect token | The token is incorrect. |
| 4106 | MFA authentication failed | MFA authentication failed. |
| 4110 | Other CAM authentication failed | Other CAM authentication failed./td> |
| 4300 | Access denied | The account is blocked or unauthorized to use the API. |
| 4400 | Quota exceeded | The number of requests exceeded the quota limit. Please submit a ticket for assistance. |
| 4500 | Replay attack | The `Nonce` and `Timestamp` parameters ensure that each request will be executed only once on the server. The `Nonce` value must be unique, and the difference between `Timestamp` and the Tencent server time should not be greater than 5 minutes. |
| 4600 | Unsupported protocol | The protocol is not supported. The current API only supports HTTPS protocol and does not support HTTP protocol. |
| 5000 | The resource does not exist | The instance corresponding to the resource ID does not exist, or the instance has been returned, or resource accessed belongs to other users. |
| 5100 | Resource operation failed | The operation performed on the resource failed. For error message, see the `message` field in error description. Try again later or contact customer service. |
| 5200 | Resource purchase failed | Failed to purchase the resource. This may be caused by unsupported instance configuration or insufficient resources.. |
| 5300 | Insufficient balance | Failed to purchase or upgrade the resource due to insufficient balance. |
| 5400 | Partially executed | The batch operation was successful on some resources. For more information, see the returned value of the function. |
| 5500 | User qualification review failed | Failed to purchase the resource due to user qualification review failure. |
| 6000 | Internal server error | An internal error occurred with the server. Try again later or contact customer service. |
| 6100 | Unsupported version | The API version is not supported or is under maintenance. Note: when this error occurs, first check whether the domain name of the API is correct, as the domain name may vary by module. |
| 6200 | API temporarily inaccessible | The current API is under maintenance and not in service. Please try again later. |
是
否
本页内容是否解决了您的问题？