错误码
更新时间：2025-08-21
当用户访问BLB出现错误时，BLB会返回给用户相应的错误码和错误信息，便于用户定位问题，并做出适当的处理。 请求发生错误时通过Response Body返回详细错误信息，遵循如下格式：
| 参数名 | 类型 | 说明 |
|---|---|---|
| code | String | 错误码 |
| message | String | 错误描述 |
| requestId | String | 本次请求的requestId |
示例：
JSON
1{
2 "requestId" : "ae2225f7-1c2e-427a-a1ad-5413b762957d",
3 "code" : "NoSuchKey",
4 "message" : "The resource you requested does not exist"
5}BCE公共错误码
| 错误码 | 错误描述 | HTTP状态码 | 语义 |
|---|---|---|---|
| AccessDenied | Access denied. | 403 Forbidden | 无权限访问对应的资源 |
| InappropriateJSON | The JSON you provided was well-formed and valid, but not appropriate for this operation. | 400 Bad Request | 请求中的JSON格式正确，但语义上不符合要求。如缺少某个必需项，或者值类型不匹配等。出于兼容性考虑，对于所有无法识别的项应直接忽略，不应该返回这个错误。 |
| InternalError | We encountered an internal error. Please try again. | 500 Internal Server Error | 所有未定义的其他错误。在有明确对应的其他类型的错误时（包括通用的和服务自定义的）不应该使用。 |
| InvalidAccessKeyId | The Access Key ID you provided does not exist in our records. | 403 Forbidden | Access Key ID不存在 |
| InvalidHTTPAuthHeader | The HTTP authorization header is invalid. Consult the service documentation for details. | 400 Bad Request | Authorization头域格式错误 |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. | 400 Bad Request | HTTP body格式错误。例如不符合指定的Encoding等 |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request | URI形式不正确。例如一些服务定义的关键词不匹配等。对于ID不匹配等问题，应定义更加具体的错误码，例如NoSuchKey。 |
| MalformedJSON | The JSON you provided was not well-formed. | 400 Bad Request | JSON格式不合法 |
| InvalidVersion | The API version specified was invalid. | 404 Not Found | URI的版本号不合法 |
| OptInRequired | A subscription for the service is required. | 403 Forbidden | 没有开通对应的服务 |
| PreconditionFailed | The specified If-Match header doesn't match the ETag header. | 412 Precondition Failed | ETag不匹配 |
| RequestExpired | Request has expired. Timestamp date is XXX. | 400 Bad Request | 请求超时 |
| IdempotentParameterMismatch | The request uses the same client token as a previous, but non-identical request. | 403 Forbidden | clientToken对应的API参数不一样。 |
| SignatureDoesNotMatch | The request signature we calculated does not match the signature you provided. Check your Secret Access Key and signing method. Consult the service documentation for details. | 400 Bad Request | Authorization头域中附带的签名和服务端验证不一致 |
BLB业务错误码
| 错误码 | 错误描述 | HTTP状态码 | 语义 |
|---|---|---|---|
| InstanceNotFound | The specified BLB instance does not exist. | 404 | 指定的LoadBalancer实例不存在 |
| ListenerNotFound | The specified listener does not exist. | 404 | 指定的监听器不存在 |
| BackendServerNotFound | The specified backend server does not exist. | 404 | 指定的后端服务器不存在 |
| ListenerAlreadyExist | Listener already exists. | 400 | 要创建的监听器已存在 |
| BackendServerAlreadyExist | Backend server already exists. | 400 | 要绑定的后端服务器已存在 |
| LastOperationNotFinished | Last operation has not finished. | 409 | 上一个LoadBalancer请求还未处理完成 |
| RealNameAuthenticationRequired | You need to pass real-name authentication. | 403 | 当前用户未通过实名认证 |
| QuotaExceeded | You have exceeded current quota. | 413 | BLB数量超过用户配额限制 |
| ServerRequired | You must have at least one bcc, dcc or bbc to create BLB. | 404 | 创建BLB时必须先拥有BCC，DCC或BBC实例 |
| ListenerExceeded | You can create at most 20 listeners per BLB instance. | 413 | 每个BLB实例最多可以创建20个监听器 |
| ServiceBlocked | Your BLB service is blocked, please contact technical support for assistance. | 403 | BLB服务被封禁，请联系技术支持 |
| InstanceCreationFailed | Fail to create blb instance. | 400 | 创建BLB实例失败，通常是由于资源不足，用户金额不足等 |
| MissingParameter | A required parameter 'parameterName' is not supplied. | 400 | 该请求缺少必要的参数"parameterName" |
| InvalidParameter | The parameter 'parameterName' is invalid. | 400 | "parameterName"参数不合法 |
| EipUnbindFailed | Fail to unbind EIP | 400 | 解绑EIP失败 |
| RedirectPortNotFound | The specified redirect port does not exist. | 404 | 指定的HTTPS监听器不存在 |
| CertificateNotFound | The specified certificate does not exist. | 404 | 指定的证书不存在 |