Error Code Description v2.0
Background Information
- An error code returned by an API does not correspond to one error message. The following table lists only common error messages.
- Most NAT Gateway APIs are asynchronous. Some error codes are displayed in the returned messages for task viewing requests. HTTP status codes may not be accurate.
- The NAT Gateway service is strongly dependent on other services, such as network and storage. When error messages are provided for the NAT Gateway-depended services, contact technical support for troubleshooting.
Error Codes
Module | HTTP Status Code | Error Code | Description | Error Message | Solution |
---|---|---|---|---|---|
Public | 400 | VPC.0002 | The AZ is left blank. | Availability zone Name is null. | Verify whether the availability_zone field in the request body for creating a subnet is left blank. |
404 | VPC.0003 | The VPC does not exist. | VPC does not exit. | Check whether the VPC ID is correct or whether the VPC exists under the tenant. | |
400 | VPC.0004 | The status of the VPC is abnormal. | VPC is not active, please try later. | Try again later or contact technical support. | |
400 | VPC.0007 | Inconsistent tenant IDs. | urlTenantId is not equal tokenTenantId | The tenant ID in the URL is different from that parsed in the token. | |
401 | VPC.0008 | Invalid token. | Invalid token in the header. | Check whether the token in the request header is valid. | |
401 | VPC.0009 | Real-name authentication failed. | real-name authentication failed. | Contact technical support. | |
403 | VPC.2701 | You do not have permission to perform this operation, or your account balance is insufficient. | Token not allowed to do this action. | Check whether the account balance is insufficient or whether your account has been frozen. | |
403 | VPC.0010 | Insufficient permissions to make calls to the underlying system. | Rules on xx by ** disallowed by policy | Obtain the required permissions. | |
403 | VPC.2201 | Insufficient fine-grained permissions. | Policy does not allow <x:x:x> to be performed | Obtain the required permissions. | |
400 | VPC.0014 | The enterprise project is unavailable. | This enterpriseProject status is disabled. | Use the ID of another available enterprise project. | |
400 | VPC.0011 | Invalid enterprise project ID. | EnterpriseProjectId is invalid | Enter a valid enterprise project ID. | |
400 | VPC.2048 | Invalid timestamp. | Invalid value for created_at %(timestamp)s. | Enter the time in the correct format. | |
400 | VPC.2002 | Invalid request parameters. | Invalid parameters. | Enter the correct parameter. | |
400 | VPC.2010 | The default route already exists. | The router %(router_id)s has default route. | The router has a default route. Delete the default route and then create a NAT gateway. | |
400 | VPC.2011 | The router does not exist. | The router %(router_id)s does not exist. | Check whether the entered router ID is correct. | |
400 | VPC.2009 | The network does not exist. | Network %(network_id)s does not exist. | Enter a valid network ID. | |
400 | VPC.2016 | The rule has not been deleted. | Rule has not been deleted. | Contact technical support. | |
400 | VPC.2049 | The database is abnormal. | DB Error | Contact technical support. | |
400 | VPC.2013 | The subnet is not connected to the virtual router. | Router %(router)s has no port for subnet %(subnet)s. | Add the subnet to the router port. | |
400 | VPC.2019 | The resource is in use. | Resource %(res_type)s %(res)s is used by %(user_type)s %(user)s | Contact technical support. | |
400 | VPC.2008 | The subnet does not exist in the VPC. | Network %(network)s does not contain any IPv4 subnet | Contact technical support. | |
400 | VPC.2012 | The VPC already has a NAT gateway. | The router %(router_id)s already has nat gateway. | Select another VPC. | |
NAT Gateway | 400 | VPC.2000 | NAT gateway request error. | Lack of user authority. //request is null. //endpoint is empty. // resource type is invalid. //create natgateway request is null. //update natgateway request is null | Contact technical support. |
400 | VPC.2030 | The system is busy. Please try again later. | The system is busy. Please try again later. | Try again later. | |
400 | VPC.2001 | Incorrect NAT gateway parameter. | Request is invalid. //NatGateway id invalid. // the enterprise project id is unsupported. // the enterprise project id in request is invalid. //parameter is null. // tags is invalid. // get natgateways error limit is invalid. //get natgateways error marker is invalid. //Only admin user can do this action. //Parameters are invalid, check them and try. | Enter the correct parameter or contact technical support. | |
400 | VPC.2004 | The NAT gateway is not activated. | NatGateway %(nat_gateway_id)s is not ACTIVE. | Check the gateway status. If the gateway is not in the running state for a long time, contact technical support. | |
400 | VPC.2005 | The NAT gateway is not in the UP state. | NatGateway %(nat_gateway_id)s is not UP. | The gateway may be frozen due to arrears. | |
400 | VPC.2006 | The NAT gateway is frozen. | NatGateway %(nat_gateway_id)s is frozen.cannot update | The gateway may be frozen due to arrears and cannot be updated. | |
400 | VPC.2007 | The NAT gateway does not exist. | NatGateway %(nat_gateway_id)s does not exist. | The NAT gateway does not exist. | |
400 | VPC.2050 | Concurrent operation conflicts. | Concurrent conflict requests found | Contact technical support. | |
400 | VPC.2051 | Failed to create the internal port of the NAT gateway. | Create NG Port failed. | Internal error. Contact technical support. | |
400 | VPC.2052 | Failed to bind the internal port to the NAT gateway. | NG Port %(port)s is unbound. | Internal error. Contact technical support. | |
400 | VPC.2053 | The NAT gateway does not support IPv6. | NatGateway does not support IPv6. | The NAT gateway cannot be bound to an IPv6 EIP. | |
400 | VPC.2045 | An error occurred when selecting the gateway node. | Get Nat gateway host failed | Contact technical support. | |
400 | VPC.2046 | Failed to obtain the IP address of the gateway node. | Get Nat gateway agent local_ip failed | Contact technical support. | |
400 | VPC.2047 | Failed to obtain the VPC route table. | Get RouteTable %(router_id)s failed. | Contact technical support. | |
400 | VPC.2012 | The router already has a NAT gateway. | The router %(router_id)s already has nat gateway. | Select a router that has not been bound to a NAT gateway. | |
SNAT Rule | 400 | VPC.2014 | Incorrect SNAT rule parameter. | Endpoint is null or empty. //Endpoint is Invalid. //Request is null. //natGatewayId is invalid. //SnatRule id invalid. //NatGatewayId is invalid. //Invalid value for public ip id. //Endpoint is null. //request is null. //Query SnatRules list error marker is invalid. | Enter the correct parameter or contact technical support. |
400 | VPC.2031 | The CIDR of the SNAT rule conflicts with the network. | Either network_id or cidr must be specified.Both cannot be specified at the same time | Do not specify the Cidr and Network_id fields at the same time when configuring an SNAT rule. | |
400 | VPC.2032 | Invalid CIDR block. | cidr is invalid, make sure its format is correct. | Enter a valid CIDR block, for example, 192.168.0.0/24. | |
400 | VPC.2033 | Invalid rule type. | source_type and network_id is incompatible. | If an SNAT rule is configured for a VPC, the parameter Source_Type is optional or set its value to 0. If an SNAT rule is configured for a Direct Connect connection, Source_type must be set to 1. | |
400 | VPC.2034 | The CIDR block must be a subset of the VPC subnet CIDR block. | cidr must be a subset of subnet's cidr. | If an SNAT rule is configured for a VPC, the CIDR block must be the VPC subnet CIDR block. For example, if the subnet is 192.168.0.0/24, the CIDR block can be 192.168.0.0/25. | |
400 | VPC.2035 | The CIDR block conflicts with the subnet CIDR block. | cidr conflicts with subnet's cidr. | If an SNAT rule is configured for a Direct Connect connection, the CIDR block cannot conflict with the VPC subnet CIDR block. | |
400 | VPC.2036 | The CIDR block conflicts with the existing one. | cidr in the request conflicts with cidrs of existing rules. | Enter a CIDR block that does not conflict with existing ones. | |
400 | VPC.2018 | The rule already exists. | Snat rule for network %(network)s exists. | Select a subnet that is not configured with an SNAT rule. | |
400 | VPC.2042 | The EIP has been used by the SNAT rule. | There is a duplicate EIP %(fips)s in SNAT rule. | Select another EIP. | |
400 | VPC.2044 | The public IP address UUID of the SNAT rule is invalid. | Invalid input for floating_ip_id. Reason: \'%(fip)s\' is not a valid UUID. | Enter a valid UUID. | |
400 | VPC.2040 | The public IP address ID of an SNAT rule cannot be left blank. | Invalid value for public ip id. | Enter a valid ID. | |
400 | VPC.2039 | The number of EIPs associated with the SNAT rule exceeds the upper limit. | %(limit)s EIP has been associated to this SNAT rules' EIP pool, no more is allowed. | The number of EIPs associated with the SNAT rule exceeds the upper limit. For details, see the NAT Gateway API Reference. | |
DNAT Rule | 400 | VPC.2020 | Incorrect DNAT rule parameter. | get dnatRules error limit is invalid. //get dnatrules error marker is invalid. //endpoint is empty. //DnatRule id invalid. //VPC ID is invalid. //Request is null. //DnatRule id invalid. //DnatRule natGatewayId id invalid. | Enter the correct parameter or contact technical support. |
400 | VPC.2054 | Invalid DNAT rule protocol. | Dnat rule protocol %(protocol)s not supported.Only protocol values %(values)s and integer representations [6, 17, 0] are supported. | Configure a valid protocol. The value range can be 6, 17, or 0, corresponding to protocols TCP, UDP, and ANY, respectively. | |
400 | VPC.2069 | Invalid DNAT rule port. | Invalid value for port %(port)s | Configure a valid internal port and external port. The value ranges from 0 to 65535. | |
400 | VPC.2023 | The internal network information of the DNAT rule conflicts with the existing one. | The port_id, private_ip, internal port, and protocol specified have been occupied. | Enter the VM port ID, private IP address, or internal port that does not conflict with the existing one. | |
400 | VPC.2024 | The external network information of the DNAT rule conflicts with the existing one. | The floating ip, external port and protocol specified have been occupied. | Enter the floating IP address ID, external port, or protocol that does not conflict with the existing one. | |
400 | VPC.2070 | The request information of the DNAT rule is incorrect when Port Type is set to All ports. | The external port equals 0 and internal port equals 0 and protocol equals any must satisfied at the same time. | Set both the internal port and the external port to 0 and the protocol is ANY. | |
400 | VPC.2027 | The port ID of the DNAT rule conflicts with that of an existing DNAT rule. | The port_id already existing dnat allport rules or dnat_rules, can no longer create dnat rules or dnat allport rules. | Change the VM port ID to create or modify the DNAT rule. | |
400 | VPC.2028 | The private IP address of the DNAT rule conflicts with that of an existing DNAT rule. | The private_ip already existing dnat allport rules or dnat rules, can no longer create dnat rules or dnat allport rules. | The private IP address conflicts with the existing DNAT rule. Change the private IP address or modify the DNAT rule. | |
400 | VPC.2029 | The DNAT rule has been frozen and cannot be modified. | DNAT rule is frozen, can no longer update. | Check whether the floating IP address bound to the DNAT rule is in arrears or whether the user account is in arrears. | |
400 | VPC.2038 | The maximum number of DNAT rules allowed to be bound has been reached. | %(limit)s DNAT rules has been associated to this NAT Gateway, no more is allowed | The maximum number of DNAT rules allowed to be associated with the NAT gateway has been reached. | |
400 | VPC.2055 | The DNAT rule contains mutually exclusive parameters. | The port_id and private_ip exist at the same time and value is not empty, but at least one value is empty. | The VM port ID and private IP address cannot be configured at the same time. | |
400 | VPC.2056 | The DNAT rule does not have required parameters configured. | The port_id and private_ip values are both empty, at least one value is not empty. | Configure the VM port ID and private IP address. | |
400 | VPC.2071 | Invalid private IP address of the DNAT rule. | The private ip address is not legal. | Configure a valid private IP address. | |
400 | VPC.2037 | This virtual IP address is not supported. | The virtual IP address is not supported. | Configure a valid private IP address. | |
400 | VPC.2026 | The maximum number of DNAT rules allowed to be bound has been reached. | %(limit)s DNAT rules has been associated to this Floating IP, no more is allowed | The maximum number of DNAT rules allowed to be associated with a floating IP address has been reached. | |
400 | VPC.2057 | The maximum number of DNAT rules allowed to be created in batches exceeds the upper limit. | batch create dnat rules max limit: %(limit)s | The maximum number of DNAT rules allowed to be created in batches exceeds the upper limit. | |
400 | VPC.2022 | Invalid VM port ID of the DNAT rule. | Port %(port)s is not a valid port. | Configure a valid VM port ID. | |
400 | VPC.2058 | The value of VtepIp must be specified. | Vtep_ip is Null. | Contact technical support. | |
400 | VPC.2075 | The description contains more than 255 characters. | Enter a maximum of 255 characters. | Enter a maximum of 255 characters. | |
EIP | 400 | VPC.2059 | The EIP is frozen. | Floating Ip %(fip)s is frozen. | Select an EIP that has not been frozen. |
400 | VPC.2060 | The EIP has been associated with a port. | Floating Ip %(fip)s has associated with port %(port)s. | Select an EIP that has not been bound to any other object. For example, if an EIP has been bound to an ECS, it cannot be bound to a NAT gateway. | |
400 | VPC.2061 | The EIP has been associated with a NAT gateway. | Floating Ip %(fip)s has used by nat gateway %(nat_gateway)s. | The EIP has been bound to a NAT gateway. Select another one. | |
400 | VPC.2062 | The EIP is in use. | Floating Ip %(fip)s has been occupied. | The EIP has been bound to a NAT gateway. Select another one. | |
400 | VPC.2074 | An EIP cannot be associated with an SNAT rule and a DNAT rule with Port Type set to All ports at the same time. | Floating Ip %(fip)s cannot be associated with both SNAT rule and DNAT all port rule. | Do not associate an EIP with an SNAT rule and a DNAT rule with Port Type set to All ports at the same time. | |
400 | VPC.2073 | An EIP cannot be associated with a DNAT rule and a DNAT rule with Port Type set to All ports at the same time. | Floating Ip %(fip)s cannot be associated with both DNAT rule and DNAT all port rule. | Do not associate an EIP with a DNAT rule and a DNAT rule with Port Type set to All ports at the same time. | |
400 | VPC.2043 | The EIP has been associated with a rule. | Floating Ip %(fip)s is used by other rules | Select an EIP that is not in use. |
- Background Information
- Error Codes