Error Message |
Solution |
APIs |
Reference |
Cannot specify duplicate network_id.
|
Set a unique network ID in interfaces. |
|
|
Invalid network_ids '{network_id list}'. Cannot specify the Common Function Gateway network.
|
The network ID must be for a network not already attached to the Common Function Gateway. |
|
|
Invalid network_id: '{network_id}'. The network's plane must be 'data'.
|
Set the network ID for the network where the plane is "data". |
|
|
|
|
The IP addresses of the attached interfaces cannot be changed directly. To change these IP addresses, please follow the steps below:
Delete the interface you wish to modify. Apply the configurations changes to remove the interface from the load balancer. Add the interface again with the desired IP addresses. Apply the configurations changes to add the interface to the load balancer.
|
|
|
Cannot specify this network (0.0.0.0/8) address '{virtual_ip_address / reserved_fixed_ips[].ip_address}' for [virtual_ip_address / reserved_fixed_ips].
Cannot specify shared space (100.64.0.0/10) address '{virtual_ip_address / reserved_fixed_ips[].ip_address}' for [virtual_ip_address / reserved_fixed_ips].
Cannot specify loopback (127.0.0.0/8) address '{virtual_ip_address / reserved_fixed_ips[].ip_address}' for [virtual_ip_address / reserved_fixed_ips].
Cannot specify link local (169.254.0.0/16) address '{virtual_ip_address / reserved_fixed_ips[].ip_address}' for [virtual_ip_address / reserved_fixed_ips].
Cannot specify multicast (224.0.0.0/4) address '{virtual_ip_address / reserved_fixed_ips[].ip_address}' for [virtual_ip_address / reserved_fixed_ips].
Cannot specify reserved (240.0.0.0/4) address '{virtual_ip_address / reserved_fixed_ips[].ip_address}' for [virtual_ip_address / reserved_fixed_ips].
|
|
|
|
Cannot specify duplicate ip_address.
|
Set a unique IP address in virtual_ip_address and reserved_fixed_ips[].ip_address. |
|
|
Invalid network_id: subnet overlap exists.
|
|
|
|
virtual_ip_address '{virtual_ip_address}' does not belong to the network '{network_id}'.
virtual_ip_address '{virtual_ip_address}' and fixed ip_address '{reserved_fixed_ips[].ip_address}' must belong to the same subnet '{subnet.cidr}' of network '{network_id}'
|
The specified virtual_ip_address must be within the address range of the interface's network. The virtual_ip_address and reserved_fixed_ips[].ip_address within the interface must be assigned from the same subnet.
|
|
|
|
|
Set an IP address that is neither a network address nor a broadcast address. |
|
|
Cannot specify duplicate syslog_server.
|
IP address and port combinations must be unique within syslog_servers . |
|
|
Cannot specify different syslog_server protocol.
|
Set the same protocol for all items in syslog_servers . |
|
|
Too many interfaces. Max number of interfaces is {4 (50M/200M plan) / 7 (1000M/3000M plan)} per load balancer.
|
Ensure that the number of interfaces does not exceed the maximum number defined in the load balancer's plan. |
|
|
Exceeded the maximum number of instances.
|
You have exceeded the maximum number of instances allowed per tenant. Please delete unnecessary instances before creating new ones. |
|
|
The specified network does not have enough unused IP addresses for reserved_fixed_ips
|
|
|
|
|
|
Specify an enabled plan ID. |
Create Load Balancer |
|
Invalid health_monitor '{health_monitor.id}': path must be empty.
|
If the protocol is "http" or "https", must not set path or set "". |
|
|
Invalid health_monitor '{health_monitor.id}': http_status_code must be empty.
|
If the protocol is "http" or "https", must not set http_status_code or set "". |
|
|
|
|
If the protocol is "icmp", must set health_monitor.port to 0. If the protocol is not "icmp", must not set health_monitor.port to 0.
|
|
|
Invalid health_monitor '{health_monitor.id}': timeout must be less than or equal to interval.
|
Set the timeout to a value that is less than or equal to the interval. |
|
|
Too many health_monitors. Max number of health_monitors is 50 per load balancer.
|
Ensure that the number of interfaces does not exceed the maximum number defined in the load balancer's plan. |
|
|
Invalid listener: cannot specify ip_address '{ip_address}' of interfaces.
|
During listener configuration, set an IP address that is not within the virtual_ip_address or reserved_fixed_ips[].ip_address of the load balancer interface to which the listener is attached. During load balancer configuration, set an IP address that is not within any attached listener's IP address.
|
Create Listener Create Staged Listener Configurations Update Staged Listener Configurations Cancel Staged Listener Configurations Create Staged Load Balancer Configurations Update Staged Load Balancer Configurations Cancel Staged Load Balancer Configurations
|
|
Cannot specify this network (0.0.0.0/8) address '{ip_address}' for listener IP address.
Cannot specify shared space (100.64.0.0/10) address '{ip_address}' for listener IP address.
Cannot specify loopback (127.0.0.0/8) address '{ip_address}' for listener IP address.
Cannot specify link local (169.254.0.0/16) address '{ip_address}' for listener IP address.
Cannot specify multicast (224.0.0.0/4) address '{ip_address}' for listener IP address.
Cannot specify reserved (240.0.0.0/4) address '{ip_address}' for listener IP address.
|
|
|
|
Cannot specify duplicate combination of ip '{ip_address}' , port '{port}' and protocol '{protocol}' for listeners.
|
Ensure that the IP address, port and protocol combinations are unique for all listeners which belong to the same load balancer. |
Create Listener Create Staged Listener Configurations Update Staged Listener Configurations Cancel Staged Listener Configurations
|
|
Too many listeners. Max number of listeners is 50 per load balancer.
|
Ensure that the number of listeners does not exceed the maximum number defined in the load balancer's plan. |
|
|
Cannot specify duplicate route.destination_cidr.
|
|
Create Route |
|
route.destination_cidr '{destination_cidr}' cannot match any network specified in interfaces
|
Set a CIDR which is not included in the subnets of the interface's network that the (static) route belongs to. |
Create Route |
|
route.destination_cidr '{destination_cidr}' cannot specify this network (0.0.0.0/8) address cidr
route.destination_cidr '{destination_cidr}' cannot specify shared space (100.64.0.0/10) address cidr
route.destination_cidr '{destination_cidr}' cannot specify loopback (127.0.0.0/8) address cidr
route.destination_cidr '{destination_cidr}' cannot specify link local (169.254.0.0/16) address cidr
route.destination_cidr '{destination_cidr}' cannot specify multicast (224.0.0.0/4) address cidr
route.destination_cidr '{destination_cidr}' cannot specify reserved (240.0.0.0/4) address cidr
Cannot be specified '{destination_cidr}' as route.destination_cidr
|
|
Create Route |
|
route.next_hop_ip_address '{next_hop_ip_address}' does not belong to any network specified in interfaces
|
Set the next_hop_ip_address to an IP address within the subnets of the interface's network. |
|
|
route.next_hop_ip_address '{next_hop_ip_address}' must not be network-address or broadcast-address
|
Set an IP address that is neither a network address nor a broadcast address. |
|
|
Too many routes. Max number of routes is 25 per load balancer.
|
Ensure that the number of routes does not exceed the maximum number defined in the load balancer's plan. |
|
|
Cannot specify this network (0.0.0.0/8) address '{members[].ip_address}' for target_group.members[].ip_address.
Cannot specify shared space (100.64.0.0/10) address '{members[].ip_address}' for target_group.members[].ip_address.
Cannot specify loopback (127.0.0.0/8) address '{members[].ip_address}' for target_group.members[].ip_address.
Cannot specify link local (169.254.0.0/16) address '{members[].ip_address}' for target_group.members[].ip_address.
Cannot specify multicast (224.0.0.0/4) address '{members[].ip_address}' for target_group.members[].ip_address.
Cannot specify reserved (240.0.0.0/4) address '{members[].ip_address}' for target_group.members[].ip_address.
|
|
|
|
Invalid target_group: cannot specify ip_address '{virtual_ip_address / reserved_fixed_ips[].ip_address}' of interfaces.
|
During target group configuration, set an IP address that is not within the virtual_ip_address or reserved_fixed_ips[].ip_address of the load balancer interface to which the target group is attached. During load balancer configuration, set an IP address that is not within any attached target group's IP address.
|
Create Target Group Create Staged Target Group Configurations Update Staged Target Group Configurations Cancel Staged Target Group Configurations Create Staged Load Balancer Configurations Update Staged Load Balancer Configurations Cancel Staged Load Balancer Configurations
|
|
Invalid target_group: cannot specify ip_address '{ip_address}' of listener.
|
During target group configuration, set an IP address that is not within the ip_address of any listener associated with the load balancer to which the target group is attached. During listener configuration, set an IP address that is not within any attached target group's IP address.
|
Create Target Group Create Staged Target Group Configurations Update Staged Target Group Configurations Create Listener Create Staged Listener Configurations Update Staged Listener Configurations Cancel Staged Listener Configurations
|
|
Invalid target_group: cannot specify duplicate combination of ip_address '{member[].ip_address}' and port '{member[].port}' for members.
|
Ensure that the IP address and port combinations are unique for all target group members which belong to the same load balancer. |
|
|
Invalid target_group: cannot specify different weight for combination of ip_address '{member[].ip_address}' and port '{member[].port}'.
|
Set same weight for the combination of IP address and port in all members which belong to the same load balancer. |
Create Target Group Create Staged Target Group Configurations Update Staged Target Group Configurations Cancel Staged Target Group Configurations
|
|
Too many members. Max number of members is 100 per target group.
|
Ensure that the number of members does not exceed the maximum number defined in the load balancer's plan. |
|
|
Too many target_groups. Max number of target_groups is 50 per load balancer.
|
Ensure that the number of target_groups does not exceed the maximum number defined in the load balancer's plan. |
|
|
Cannot delete target_group '{target_group.id}' because it is referenced as target_group by following rule: '{rule.id}'
Cannot delete target_group '{target_group.id}' because it is referenced as backup_target_group by following rule: '{rule.id}'
|
The target group cannot be deleted because it is referenced by a rule. Remove the target group settings from the rule. |
|
|
Unable to load certificate. The content data may be in an incorrect format.
Unable to load certificate. The file format before encoding must be PEM.
Could not deserialize key data. The data may be in an incorrect format or it may be encrypted with an unsupported algorithm.
|
Please verify the combination of the certificate type and content you are trying to upload, or the content format. |
Upload Certificate |
|
Bad decrypt. Incorrect password?
|
Ensure the passphrase for the ssl-key is correct. |
Upload Certificate |
|
|
|
If the private key is encrypted, please specify the passphrase. If the private key is not encrypted, do not specify the passphrase or set it to "".
|
Upload Certificate |
|
The content must be a {key-algorithm} in RSA (1024, 2048, 3072, or 4096 bits) or ECDSA (P-256, P-384, or P-521) format.
|
|
Upload Certificate |
|
The public key in the content of request body does not match the public key in the uploaded [ssl-cert / ssl-key].
|
Ensure that the public key from the ssl-cert content is the same as the public key in the ssl-key. |
Upload Certificate |
|
The passphrase can be set when 'type' is 'ssl-key'.
|
The passphrase can only be specified when uploading an ssl-key. |
Upload Certificate |
|
|
|
Please ensure the content to be Base64 decodable, and ensure the MIME type after Base64 decoding is text/plain. |
Upload Certificate |
|
Not more than 16,777,215 characters can be specified for content.
|
The maximum file size of content which could be uploaded is 16KB. |
Upload Certificate |
|
ca-cert has already been uploaded.
ssl-cert has already been uploaded.
ssl-key has already been uploaded.
|
The certificate file could be uploaded only once for each type. If you need to re-upload, please delete the existing certificate and create a new one. |
Upload Certificate |
|
Cannot specify the certificate that belong to the policy
|
Deletion of certificates associated with policies is not allowed. Remove certificate settings from the policy. |
Delete Certificate |
|
Exceeded the maximum number of certificates.
|
You have exceeded the maximum number of certificates allowed per tenant. Please delete unnecessary certificates before creating new ones. |
Create Certificate |
|
policy refers to the listener '{listener_id}' that does not exist.
policy refers to the health_monitor '{health_monitor_id}' that does not exist.
policy refers to the default_target_group '{default_target_group_id}' that does not exist.
policy refers to the backup_target_group '{backup_target_group_id}' that does not exist.
Cannot delete listener '{listener.id}' as it is referenced by following policy: {policy.id}
Cannot delete health_monitor '{health_monitor.id}' as it is referenced by following policy: {policy.id}
Cannot delete target_group '{target_group.id}' as it is referenced by following policy: {policy.id}
|
During policy creation or update, the resource ID with configuration_status of DELETE_STAGED is specified.
During policy configuration change rollback, the configuration_status of the resource associated with the current configuration of the policy is DELETE_STAGED.
During resource deletion, the resource being deleted is associated with the policy.
|
Create Policy Create Staged Policy Configurations Update Staged Policy Configurations Cancel Staged Policy Configurations Delete Health Monitor Delete Listener Delete Target Group
|
|
Cannot specify duplicate listener_id '{listener.id}' for policies.
|
Set the listener ID which is not associated with any policy. |
Create Policy Create Staged Policy Configurations Update Staged Policy Configurations Cancel Staged Policy Configurations
|
|
Invalid policy '{policy.id}': sorry_page_url must be empty.
|
If the protocol of the policy's listener is neither "http" nor "https", must not set sorry_page_url or set "". |
|
|
|
|
If the protocol of the policy's listener is "https", set certificate_id. If the protocol of the policy's listener is not "https", must not set certificate_id or set "".
|
|
|
Invalid policy '{policy.id}': tls_policy_id must be empty.
|
If the protocol of the policy's listener is not "https", must not set tls_policy_id or set "". |
|
|
Invalid policy '{policy.id}': Cannot belong rules because protocol of the assigned listener is not http or https.
|
If the policy is currently configured, there is a rule associated with the target policy.
Please specify the listener protocol as either "http" or "https". If you want to change the listener protocol, please delete the rule or delete and recreate the policy.
If the listener is currently configured, it cannot be changed because the target listener has a policy associated with it, and that policy has a rule associated with it.
|
Create Staged Policy Configurations Update Staged Policy Configurations Cancel Staged Policy Configurations Create Staged Listener Configurations Update Staged Listener Configurations Cancel Staged Listener Configurations
|
|
Invalid policy '{policy.id}': Cannot specify same target group to default_target_group and backup_target_group.
|
The default target group ID and the backup target group ID must be assigned unique values. |
Create Policy Create Staged Policy Configurations Update Staged Policy Configurations Cancel Staged Policy Configurations
|
|
Invalid policy '{policy.id}': Cannot specify same member ({member}) in default_target_group and backup_target_group.
|
If a policy is being configured, designate target groups with distinct members for the default and backup target groups. If you are canceling policy configuration modifications, check the target group member settings to ensure the current default and backup target groups' members remain distinct.
|
Create Policy Create Staged Policy Configurations Update Staged Policy Configurations Cancel Staged Policy Configurations
|
|
Invalid policy '{policy.id}': persistence_timeout must be 0 for persistence 'none'.
Invalid policy '{policy.id}': persistence_timeout must be between 1 and 2000 for persistence 'source-ip'.
Invalid policy '{policy.id}': persistence_timeout must be between 0 and 525600 for persistence 'cookie'.
|
If persistence is "none", must not set persistence_timeout or set "". If persistence is "source-ip", must set persistence_timeout between 1 and 2000. If persistence is "cookie", must set persistence_timeout between 0 and 525600.
|
|
|
Invalid policy '{policy.id}': Cannot specify 'cookie' to persistence because protocol of the assigned listener is not http or https.
|
If the protocol of the policy's listener is neither "http" nor "https", specify "none" or "source-ip" for persistence . If you wish to specify "cookie" for persistence , use a listener with a protocol of "http" or "https".
|
Create Policy Create Staged Policy Configurations Update Staged Policy Configurations Cancel Staged Policy Configurations
|
|
Too many certificates. Max number of certificates is 50 per load balancer.
|
|
Create Policy Create Staged Policy Configurations Update Staged Policy Configurations Cancel Staged Policy Configurations
|
|
Invalid certificate '{certificate.id}': [ca_cert / ssl_cert / ssl_key] is not uploaded.
|
Confirm that ca_cert, ssl_cert, and ssl_key are uploaded for all certificate IDs specified in the policy and the policy's server_name_indications. |
|
|
|
|
If the protocol of the policy's listener is "https", you must specify a certificate_id. If the protocol of the policy's listener is not "https", either do not specify a certificate_id or set it to ""
|
|
|
Too many server_name_indications. Max number of server_name_indications is 50 per policy.
|
Ensure that the number of server_name_indications per policy does not exceed the maximum number defined in the load balancer's plan. |
|
|
Cannot specify duplicate priority.
|
Priority values must be unique across all server_name_indications w |
|
|
Cannot specify duplicate server_name.
|
The server_name value must be unique across all server_name_indications within the policy. |
|
|
server_name_indications must be empty
|
If the protocol of the policy's listener is not "https", server_name_indications cannot be specified. |
|
|
Too many policies. Max number of policies is 50 per load balancer.
|
Ensure that the number of policies does not exceed the maximum number defined in the load balancer's plan. |
|
|
Too many policies and rules. Max number of policies and rules is 100 per load balancer.
|
|
Create Policy Create Rule
|
|
Too many rules. Max number of rules is 50 per policy.
|
Ensure that the number of rules does not exceed the maximum number defined in the load balancer's plan. |
|
|
Too many conditions. Max number of conditions is 5 per rule.
|
Ensure that the number of path conditions does not exceed the maximum number defined in the load balancer's plan. |
|
|
Number of conditions must not be 0
|
At least one path condition must be set. |
|
|
Cannot specify the same target group as target_group_id and backup_target_group_id.
|
The target group ID and the backup target group ID must be assigned unique values. |
|
|
Cannot specify same member ({member}) in target_group and backup_target_group.
|
If a Rule is being configured, designate target groups with distinct members for the target group and backup target group. If you are canceling rule configuration modifications, check the target group member settings to ensure the current target group and backup target group' members remain distinct.
|
|
|
Cannot specify the policy which protocol of the assigned listener is not http or https.
|
Set the listener protocol, the rule's designated policy, to "http" or "https". |
Create Rule |
|
Cannot specify the same priority from same policy rules
|
Priority values must be unique for every rule within the same policy. |
Create Rule Create Staged Rule Configurations Update Staged Rule Configurations Cancel Staged Rule Configurations
|
|
Cannot specify the same path patterns from same policy rules
|
Path patterns must be unique for every rule within the same policy. |
Create Rule Create Staged Rule Configurations Update Staged Rule Configurations Cancel Staged Rule Configurations
|
|
|
|
Please set a resource ID that is not in the DELETE_STAGED state. |
|
|
|
|
Operations are restricted based on the configuration_status and operation_status values. Please refer to the link in the Reference column for details. |
All APIs |
|