Error Codes¶
Status Code | Error Codes | Error Message | Description | Solution |
|---|---|---|---|---|
400 | ELB.0002 | The request body is null or empty. The request is invalid. | The request body is empty. | Configure the parameters by following the instructions in the Elastic Load Balance API Reference. |
400 | ELB.0004 | The API response is null or invalid. | The response is empty. | Ensure that the backend server is healthy. |
400 | ELB.0230 | Tenant_id is empty. | The project ID is left blank. | Correct the project ID. |
400 | ELB.1000 | The loadbalancer URL is too long. | The URL length exceeds the limit. | Correct the URL. |
400 | ELB.1001 | Request parameters invalid. | Invalid parameters. | Enter valid parameters. |
400 | ELB.1003 | The load balancer does not exist. | The load balancer does not exist. | Check the load balancer ID. |
400 | ELB.1004 | The query condition is invalid. | Invalid query condition. | Change the query condition. |
400 | ELB.1005 | Invalid update request parameters. | Failed to modify the load balancer. | Check the parameters. |
400 | ELB.1007 | Querying the internal load balancer failed. | Failed to query the details of the private network load balancer. | Contact customer service. |
400 | ELB.1008 | This load balancer has members associated. | Failed to delete the load balancer. | Change the parameter settings. |
400 | ELB.1010 | Querying the load balancer quota failed. | Failed to query the quota. | Contact customer service. |
400 | ELB.1011 | Invalid private key or certificate content. | Invalid private or public key of the server certificate. | Enter a valid private or public key. |
400 | ELB.1012 | Failed to create the relationship between resources and the user. | Failed to create the relationship between resources and the user. | Contact customer service. |
400 | ELB.1013 | Quota modification failed. The quota set in the Cloud Eye alarm rule is excessively high. | The quota modification failed due to an excessively high quota setting in the Cloud Eye alarm rule. | Contact customer service. |
400 | ELB.1014 | Failed to query the relationship between resources and the user. | Failed to query the relationship between resources and the user. | Contact customer service. |
400 | ELB.1015 | Updating the load balancer failed. | Failed to modify the load balancer. | Check the parameters. |
400 | ELB.1018 | This load balancer has members associated. | Failed to delete the load balancer because it has backend servers associated. | Remove the backend servers from the associated backend server group and delete the backend server group first. |
400 | ELB.1020 | Incorrect load balancer ID. | Incorrect load balancer ID. | Change the parameter settings. |
400 | ELB.1021 | Invalid request parameters. Invalid load balancer name. | Invalid load balancer name. | Change the name. |
400 | ELB.1025 | Invalid update request parameters. The load balancer name is too long. | The load balancer name exceeds the length limit. | Change the name. |
400 | ELB.1031 | Invalid request parameters. The load balancer description is too long. | The load balancer description exceeds the length limit. | Change the description. |
400 | ELB.1035 | Invalid update request parameters. Invalid load balancer name. | Invalid load balancer name. | Change the name. |
400 | ELB.1041 | Invalid request parameters. Invalid load balancer type. | Invalid load balancer type. | Change the parameter settings. |
400 | ELB.1045 | Invalid update request parameters. The load balancer description is too long. | The load balancer description exceeds the length limit. | Change the description. |
400 | ELB.1051 | Invalid request parameters. Invalid load balancer bandwidth. | Invalid bandwidth configured for the load balancer. | Modify the bandwidth. |
400 | ELB.1061 | Invalid request parameters. Parameters vip_address and vip_subnet_id are null. | The EIP or subnet ID is left blank. | Enter a valid EIP or subnet ID. |
400 | ELB.1071 | Invalid request parameters. vip_address is not valid. | Invalid EIP. | Enter a valid EIP. |
400 | ELB.1081 | Invalid request parameters. vpc_id is empty. | The VPC ID is left blank. | Enter a valid VPC ID. |
400 | ELB.1101 | The EIP already exists. | The EIP already exists. | Enter another EIP. |
400 | ELB.1110 | The API version could not be found. | The API version does not exist. | Contact customer service. |
400 | ELB.1201 | Obtaining the token failed. | Failed to obtain the token. | Contact customer service. |
400 | ELB.1202 | enterprise_project_id cannot be empty. | Verification of the enterprise project ID failed. | Check the enterprise project ID. |
400 | ELB.1204 | Binding failed. | Failed to associate the load balancer with the enterprise project. | Contact customer service. |
400 | ELB.2002 | Invalid request parameters for removing the backend server. | Failed to remove the backend server because the parameters are invalid. | Change the parameter settings. |
400 | ELB.2003 | Querying the member failed. | Failed to query the backend server. | Contact customer service. |
400 | ELB.2005 | Updating the member failed. | Failed to update the backend server. | Contact customer service. |
400 | ELB.2010 | Invalid listener ID length. | The listener ID exceeds the length limit. | Change the listener ID. |
400 | ELB.2011 | The listener does not exist. | The listener does not exist. | Ensure that the listener exists. |
400 | ELB.2012 | The member does not exist. | The backend server does not exist. | Ensure that the backend server exists. |
400 | ELB.2020 | Invalid listener ID. | Invalid listener ID. | Change the listener ID. |
400 | ELB.2021 | Invalid request parameters. The member IP address is null. | Invalid backend server IP address. | Check the backend server IP address. |
400 | ELB.3001 | Creating the EIP failed. | Failed to assign the EIP. | Contact customer service. |
400 | ELB.3002 | Deleting the EIP failed. | Failed to release the EIP. | Contact customer service. |
400 | ELB.3003 | Querying the EIP failed. | Failed to query the EIP. | Contact customer service. |
400 | ELB.3004 | Querying EIPs failed. | Failed to query EIPs. | Contact customer service. |
400 | ELB.4001 | Creating the EIP failed. | Failed to assign the EIP. | Contact customer service. |
400 | ELB.4002 | Deleting the EIP failed. | Failed to release the EIP. | Contact customer service. |
400 | ELB.4003 | Querying the EIP failed. | Failed to query the EIP. | Contact customer service. |
400 | ELB.4004 | Querying EIPs failed. | Failed to query EIPs. | Contact customer service. |
400 | ELB.4005 | Updating the EIP failed. | Failed to update the EIP. | Contact customer service. |
400 | ELB.5002 | Failed to delete the certificate. | Failed to delete the certificate. | Contact customer service. |
400 | ELB.5003 | Querying the bandwidth failed. | Failed to query the bandwidth. | Contact customer service. |
400 | ELB.5004 | Invalid search criteria. | Invalid query condition. | Change the query condition. |
400 | ELB.5005 | Updating the bandwidth failed. | Failed to modify the bandwidth. | Contact customer service. |
400 | ELB.5013 | Invalid private key or certificate content. | Invalid public or private key of the server certificate. | Enter a valid public or private key. |
400 | ELB.5020 | The certificate ID must be 32 characters long. | The certificate ID is not a 32-character string. | Enter a valid certificate ID. |
400 | ELB.5033 | Failed to update the certificate. | Failed to modify the certificate. | Contact customer service. |
400 | ELB.5040 | The certificate does not exist. | The certificate does not exist. | Ensure that the certificate exists. |
400 | ELB.5051 | CA certificate content is not valid. | Invalid CA certificate body. | Enter a valid certificate body. |
400 | ELB.5053 | CA certificate content is not valid. | Invalid CA certificate body. | Enter a valid certificate body. |
400 | ELB.5131 | Failed to query the certificate quota. | Failed to query the certificate quota. | Contact customer service. |
400 | ELB.5141 | Failed to query the used certificate quota. | Failed to query the used certificate quota. | Contact customer service. |
400 | ELB.5151 | The certificate quantity exceeds the quota. | The certificate quota has been used up. | Delete the certificates that are no longer used or request a higher quota. |
400 | ELB.6010 | Invalid listener ID. | Invalid listener ID. | Change the listener ID. |
400 | ELB.6011 | Invalid request parameters. The listener name is too long. | The listener name exceeds the length limit. | Change the name. |
400 | ELB.6015 | The listener property cannot be updated. | The listener property cannot be modified. | Select a property that can be modified. |
400 | ELB.6021 | Invalid request parameters. Invalid listener name. | Invalid listener name. | Change the name. |
400 | ELB.6025 | Invalid update request parameters. The listener name is too long. | The listener name exceeds the length limit. | Change the name. |
400 | ELB.6030 | The listener has not been associated with any load balancer. | The listener does not belong to any load balancer. | Check the listener ID. |
400 | ELB.6031 | Invalid request parameters. The listener description is too long. | The listener description exceeds the length limit. | Change the description. |
400 | ELB.6035 | Invalid update request parameters. Invalid listener name. | Invalid listener name. | Change the name. |
400 | ELB.6040 | The load balancer that the listener is associated with does not exist. | The load balancer that the listener is associated with does not exist. | Check the load balancer ID. |
400 | ELB.6041 | Invalid request parameters. The listener port must be within the range of 1 to 65535. | Invalid port number. | Change the port number. |
400 | ELB.6045 | Invalid update request parameters. The listener description is too long. | The listener description exceeds the length limit. | Change the description. |
400 | ELB.6051 | Invalid request parameters. Invalid load balancing algorithm. | Invalid load balancing algorithm. | Change the load balancing algorithm. |
400 | ELB.6061 | Invalid request parameters. Invalid listener protocol. | Invalid listener protocol. | Change the protocol. |
400 | ELB.6071 | Invalid request parameters. Invalid backend protocol. | Invalid backend protocol. | Change the protocol. |
400 | ELB.6200 | Load balancer *** already has a listener with protocol_port of ***. | The port number is in use. | Change the port number. |
400 | ELB.7000 | The listener ID must not be null. | The listener ID is left blank. | Change the listener ID. |
400 | ELB.7001 | Invalid health check interval. | Invalid update condition. | Change the update condition. |
400 | ELB.7002 | Invalid health check deletion condition. | Invalid deletion condition. | Change the deletion condition. |
400 | ELB.7004 | Invalid health check query condition. | Invalid query condition. | Change the query condition. |
400 | ELB.7010 | The health check listener does not exist. | The listener with which the health check is associated does not exist. | Change the listener ID. |
400 | ELB.7014 | The health check does not exist. | The health check does not exist. | Check the health check ID. |
400 | ELB.7020 | The health check does not exist. | The health check does not exist. | Change the health check ID. |
400 | ELB.8001 | Creating the security group failed. | Failed to create the security group. | Contact customer service. |
400 | ELB.8101 | Creating the VPC failed. | Failed to create the VPC. | Contact customer service. |
400 | ELB.8102 | Deleting the VPC failed. | Failed to delete the VPC. | Contact customer service. |
400 | ELB.8103 | Querying the VPC failed. | Failed to query the VPC. | Contact customer service. |
400 | ELB.8201 | Creating the subnet failed. | Failed to create the subnet. | Contact customer service. |
400 | ELB.8202 | Deleting the subnet failed. | Failed to delete the subnet. | Contact customer service. |
400 | ELB.8203 | Querying the subnet failed. | Failed to query the subnet. | Contact customer service. |
400 | ELB.8902 | Invalid input for '%s'. | Invalid input parameters. | Check input parameters. |
400 | ELB.8909 | Certificates with multiple domains are not supported by dedicated load balancers. | Certificates with multiple domains are not supported by dedicated load balancers. | Check input parameters. |
400 | ELB.8934 | The number of available IP addresses in the subnet on the downstream plane is insufficient. | The number of available IP addresses in the subnet on the downstream plane is insufficient. | Check your request based on the error message. |
400 | ELB.8938 | The IP member is supported only when the pool protocol is %s. | Invalid input parameters. | Add members to supported pools or pass parameter subnet_cidr_id. |
400 | ELB.8939 | The load balancer's ip_target_enable must be true when adding IP members. | Invalid input parameters. | Set ip_target_enable to false or pass parameter subnet_cidr_id. |
400 | ELB.8950 | Resources cannot be allocated to the load balancer. | Resources cannot be allocated to the load balancer. | Contact customer service. |
400 | ELB.8959 | The %s flavor field does not support update from %s to %s. | Invalid input parameters when updating the flavor. | Check input parameters. |
400 | ELB.9001 | Creating the VM failed. | Failed to create the VM. | Contact customer service. |
400 | ELB.9002 | Deleting the VM failed. | Failed to delete the VM. | Contact customer service. |
400 | ELB.9003 | Querying the VM failed. | Failed to query details of the VM. | Contact customer service. |
400 | ELB.9006 | Updating the VM port failed. | Failed to update the port bound to the VM. | Contact customer service. |
400 | ELB.9007 | Binding the VM port failed. | Failed to bind the port to the VM. | Contact customer service. |
400 | ELB.9023 | Querying the image failed. | Failed to query the image. | Contact customer service. |
400 | ELB.9033 | Querying the VM flavor failed. | Failed to query the VM specifications. | Contact customer service. |
400 | ELB.9043 | Querying the VM port failed. | Failed to query the port bound to the VM. | Contact customer service. |
400 | ELB.9061 | Querying the SMN topic failed. | Failed to query the SMN topic. | Contact customer service. |
400 | ELB.9062 | Creating the SMN topic failed. | Failed to create the SMN topic. | Contact customer service. |
400 | ELB.9063 | Querying the SMN subscription failed. | Failed to query the SMN subscription. | Contact customer service. |
400 | ELB.9064 | Creating the SMN subscription failed. | Failed to create the SMN subscription. | Contact customer service. |
400 | ELB.9800 | The resource could not be found. | The specified load balancer does not exist when ep_id is queried. | Ensure that the load balancer belongs to the enterprise project. |
400 | ELB.9801 | enterprise_project_id must not be null. | In fine-grained authorization, the enterprise ID is not passed in the request for querying load balancers. | Ensure that the parameters in the request for querying load balancers are correct. |
400 | ELB.9805 | Listener protocol in the request body is null. This is a required parameter. | ep_id in the URI is not a valid UUID. | Check the enterprise project ID. |
400 | ELB.9807 | Quota exceeded for resources: %s | Not enough resource quotas. | Contact customer to expand quotas. |
400 | ELB.9899 | Invalid parameter. For details about the error, see the returned information. | Invalid parameter. For details about the error, see the returned information. | Please check parameters. |
401 | ELB.1103 | Token invalid | Invalid token. | Contact customer service. |
401 | ELB.1104 | Token invalid | Invalid token. | Contact customer service. |
401 | ELB.1105 | Token invalid | Invalid token. | Contact customer service. |
401 | ELB.1109 | Authentication failed. | Real-name authentication failed. | Contact customer service. |
403 | ELB.1091 | The number of load balancers exceeds the quota. | The number of load balancers exceeds the quota. | Request a higher quota or delete load balancers that are no longer needed. |
403 | ELB.1102 | Invalid token. Authentication required. | The token is empty. | Enter a valid token that has not expired. |
403 | ELB.2001 | Creating the member failed. The total number of members exceeds the upper limit. | Failed to add the backend server because the number of backend servers reaches the limit. | Check the maximum number of backend servers. |
403 | ELB.6091 | The number of listeners reaches the limit. | The number of listeners reaches the limit. | Request a higher quota or delete listeners that are no longer needed. |
403 | ELB.8962 | The feature is not supported. | The feature is not supported. | Contact customer service. |
403 | ELB.9802 | elb:logtanks:create is not obtained. | Authentication failed. | Ensure that you have the permission to perform this operation. |
403 | ELB.9803 | elb:loadbalancers:list is not obtained. | Authentication failed. | Ensure that you have the permission to perform this operation. |
403 | ELB.9804 | elb:loadbalancers:list is not obtained. | Authentication failed. | Ensure that you have the permission to perform this operation. |
404 | ELB.1002 | The load balancer is not found. | The load balancer does not exist. | Change the load balancer ID. |
404 | ELB.8904 | %s %s could not be found. | The resource could not be found. | Please check the parameters. |
409 | ELB.8905 | Quota exceeded for resources: %s | Not enough resource quotas. | Contact customer service. |
409 | ELB.8907 | Data conflict. For details about the error, see the returned information. | Data conflict. For details about the error, see the returned information. | Check your request based on the error message. |
500 | ELB.8906 | Internal server error. | Internal error. For details about the error, see the returned information. | Contact customer service. |