| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2019-05-28 |
error, message, API, limitations, rias, support |
vpc-on-classic |
{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:tip: .tip} {:important: .important} {:new_window: target="_blank"} {:DomainName: data-hd-keyref="DomainName"}
{: #rias-error-messages}
When you receive an error message from the {{site.data.keyword.cloud}} Virtual Private Cloud APIs, you can use the message ID to find more information about how to resolve the problem. {:shortdesc}
Message: You must have a Pay-As-You-Go account to provision a Virtual Private Cloud.
Your account must be on a Pay-As-You-Go plan to provision VPCs. You can find more details about upgrading your account here: Upgrade Your Account
Message: The network ACL cannot be deleted because it is attached to resources.
The network ACL cannot be deleted because it is attached to a subnet or VPC.
To see if a subnet is using the network ACL, use the GET /v1/subnets?version=2019-01-01&generation=1 API. Equivalent CLI command: ibmcloud is subnets. To update the network ACL used by a subnet use the PATCH /v1/subnets/{subnet_id}?version=2019-01-01&generation=1 -d '{ "network_acl":{ "id": “{network_acl_id}” } }’ API or ibmcloud is subnet-update CLI.
To see if a VPC is using the network ACL, use the GET /v1/vpcs?version=2019-01-01&generation=1 API. Equivalent CLI command: ibmcloud is vpcs. It is not possible to update or delete the default network ACL used by a VPC. The default network ACL is deleted automatically when the VPC gets deleted.
Message: The address prefix with this CIDR is in use.
The CIDR for the requested address prefix conflicts with an existing address prefix.
To view the list of address prefixes for a VPC, use the GET /vpcs/{vpc-id}/address_prefixes API and check that the requested CIDR address is not in use by the cidr field of another address prefix.
Equivalent CLI command: ibmcloud is vpc-address-prefix
Message: Cannot delete an address prefix in use.
One or more subnets are using the address prefix. To determine which subnets are using the address prefix, use the GET /v1/subnets?version=2019-01-01&generation=1 API command and check the ipv4_cidr_block field. Equivalent CLI command: ibmcloud is subnets and check the Subnet CIDR column. You must delete all the subnets using the address prefix before the address prefix can be deleted.
Message: The backend service is unavailable.
A backend cloud service that is used by VPC failed to respond. VPC uses multiple IBM Cloud services, such as:
- Identity and Asset Management (IAM)
- Global Catalog
- Resource Controller
- Resource Manager
You can check status of IBM Cloud services and try again in a few minutes. If this problem persists, contact support.
Message: Correct instance UUID should be provided
One of the values provided in the request is incorrect. Check the target value in the error returned for clues as to which parameter was incorrect. In some cases, the UUID or volume in the request cannot be found. Provide a valid value and try again.
Refer to the API documentation{: new_window} for additional help. If this problem persists, contact support.
Message: The information given was invalid, malformed, or missing a required field.
The request was not what we expected. Use the API documentation{: new_window} to help you format the request.
If you are following the specification but still get the error, contact support.
Message: Only one VPC with Classic Access can be created per region.
Only one VPC with Classic Access can be created per region. To list the VPC with Classic Access, run ibmcloud is vpcs --classic-access. The existing VPC with Classic Access must be deleted before another one with Classic Access can be created.
Message: Account must be VRF-enabled to create a classic access VPC.
The linked classic account is not VRF-enabled. A classic access VPC requires the linked classic account to be VRF-enabled. To enable your account for VRF, please refer to VRF on IBM Cloud.
Message: Default address prefix not found.
You may see this error message when the default address prefix is not found.
Message: The input provided already exists.
The resource specified already exists. Try using a different name for the resource you want to create. For example, when creating a new VPC, you can list existing VPCs by running ibmcloud is vpcs. Choose a name that does not conflict.
Message: The floating IP is in use.
This floating IP is associated with a virtual server instance or public gateway.
To see where the floating IP is used, use the GET /v1/floating_ips/e6e4850d-123e-43a9-a224-ea10a287770e?version=2019-03-12 API and look at the "target" values. Equivalent CLI command: ibmcloud is floating-ip FLOATINGIP_ID.
Message: Can only have one public gateway per zone in a VPC.
Only one public gateway per zone is allowed in a VPC but the one public gateway can be attached to multiple subnets in the zone. To find the public gateway for a zone, run the GET public_gateways API and look at the "vpc" and "zone" values. If using the CLI, you can run the ibmcloud is public-gateways command and see the "VPC" and "Zone" value.
Use the public gateway's ID to attach it to a subnet, see an example in our API examples. If using the CLI, you can use the subnet update command to attach it to a public gateway, for example, ibmcloud is subnet-update SUBNET_ID --public-gateway-id PUBLIC_GATEWAY_ID.
Message: The specified health monitor delay <health_monitor_delay> is invalid
Provide a value between 2 and 60 for the parameter health monitor delay.
Message: The specified health monitor max retries <health_monitor_max_retries> is invalid
Provide a value between 1 and 10 for health max retries.
Message: The specified health monitor timeout <health_monitor_timeout> is invalid.
Provide a value between 1 and 59 for health timeout. The selected value must be less than the value of health monitor delay.
Message: The specified health URL path <health_monitor_url> is invalid.
Provide a valid URL for the health monitor. The URL may contain alphanumeric characters, hyphens, and periods. No spaces or backslashes are allowed. The maximum length of the URL path is 255 characters.
Message: The specified health monitor protocol <health_monitor_protocol> is invalid.
Provide a valid value for the health monitor protocol. Acceptable values are http and tcp.
Message: Health monitor protocol is missing
Health monitor protocol is a required field. In your request, specify the health monitor protocol. The acceptable values are http and tcp.
Message: Health monitor URL path is missing. It is required for a HTTP type health monitor.
For a health monitor using HTTP protocol, health monitor URL path is required field. Provide a valid URL path.
Message: Health Monitor timeout <health_monitor_timeout> should not be greater than or equal to delay <health_monitor_delay>.
The value of the parameter health monitor delay must be greater than the value of health monitor timeout.
Message: The HTTP request is too large.
This problem occurs when the payload you have sent in your request has too many characters. Please try again with a smaller payload. For example, instead of trying to do everything in a single request, try creating a minimal resource in one request, and then appending state to it incrementally in several subsequent requests.
Refer to the API documentation{: new_window} for additional help. If this problem persists, contact support.
Message: None
A failure has occurred in the IAM service, verifying authentication or authorization. The outage of the IAM service may be temporary. Retry the request after few minutes. If this problem persists, contact support.
Message: The IKE policy cannot be created because your account has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view current IKE policies, use the GET /ike_policies API.
Equivalent CLI command: ibmcloud is ike-policies
Message: The name <ike_policy_name> is in use already by IKE policy <ike_policy_id>.
Provide a different IKE policy name. Try again in a few minutes. If this problem persists, contact support.
Message: The IKE policy <ike_policy_id> is in use by one or more connections.
An IKE policy cannot be deleted if it is in use by one or more connections.
To see which connections are using the IKE policy, use the GET /ike_policies/<ike_policy_id>/connections API.
Equivalent CLI command: ibmcloud is ike-policy-connections IKE_POLICY_ID
Message: The name <ike_policy_name> is not a valid IKE policy name.
A valid IKE policy name starts with a letter, followed by letters, digits, underscores or hyphens.
Message: The IKE policy <ike_policy_id> could not be found.
You referenced an IKE policy that does not exist. Please review your request to ensure that you specified the proper IKE policy ID. Try again in a few minutes. If this problem persists, contact support.
Message: The instance cannot be deleted in the current status.
You cannot delete an instance when it is in deleting, pending, starting, stopping, or restarting status. The instance must be in running or stopped status. If the status does not change, contact support.
Message: The instance cannot be created because the hostname is not valid.
The instance hostname must meet the following requirements:
- The hostname must contain only alphanumeric characters and dashes
- Uppercase characters are not allowed
- Leading and trailing dashes are not allowed
- Leading numbers are not allowed
- Consecutive dashes are not allowed
- Maximum length is 15 characters for Windows
- Maximum length is 40 characters for other operating systems
Message: The instance cannot be created because the specified network interface port speed is not valid.
The network interface port speed must be 100 or 1000 Mbps.
Message: The same instance name already exists.
If this problem persists, contact support.
Message: The instance cannot be created because the number of volume attachments would exceed the quota.
The VPC quotas per resource are specified on the Quotas{: new_window} page.
Message: The Windows instance cannot be created because the request contains multiple keys.
Windows instances only support one key.
Message: Insufficient space for subnet in address prefix.
The subnet cannot be created because the number of addresses requested cannot be allocated. Please try again using a smaller address count or a larger CIDR.
Message: An internal error occurred.
An unexpected error occurred. This problem may be temporary. Try the request again in a few minutes. If this error persists, contact support.
Message: None
An unexpected error occurred. This problem may be temporary. Try the request again in a few minutes. If this error persists, contact support.
Message: Please contact your administrator.
An unexpected error occurred. This problem may be temporary. Try the request again in a few minutes. If this error persists, contact support.
Message: Bad ID format. Ensure format is correct.
Make sure that the ID you provided does not contain any malformed data.
You may get this error message if you provide a malformed start query when making a pagination request. For example,
GET /v1/network_acls?start=23fbba08-ceb3-4cbe-a951-84ff20a06069?version=2019-01-01&generation=1 contains two ?s. Fix the query and try again.
Message: The requested route does not exist.
The requested route on the API URL you provided does not exist. Verify that the URL you specified to call the API endpoint is correct.
Message: A field provided in the request is not valid.
For example, to update the network ACL used by a subnet use the PATCH /v1/subnets/{subnet_id}?version=2019-01-01&generation=1 -d '{ "network_acl":{ "id": “{network_acl_id}” } }’ API.
The following request would be invalid because “networkacl” is not a valid field, PATCH /v1/subnets/{subnet_id}?version=2019-01-01&generation=1 -d '{ "networkacl":{ "id": “{network_acl_id}” } }’
Refer to the API documentation{: new_window} for acceptable values.
Message: An action was requested on a resource which is not supported at the current status of the resource.
- A reboot operation may already be in progress for the instance. Refer to actions allowed depending on the status of the instance.
- While the status of the instance is
pending, you cannot perform the following actions:
- delete the instance
- attach a volume to the instance
- detach a volume from the instance
- update the instance
Try your action again later. If the status of the resource does not change, contact support.
Message: The version parameter is invalid, it must be of the form YYYY-MM-DD.
The version must comply with the format YYYY-MM-DD. For single-digit months or dates, such as January 1st, the version should look like 2019-01-01. The version parameter must be present in the URL. The date given in the version parameter must be later than 2019-01-01 but before the current date.
Message: The version value cannot be set at a future date nor before 2019-01-01.
The date given in the version parameter must be later than 2019-01-01 but before the current date.
Message: Please check whether the resources you are requesting are in the same zone.
You may see this message attempting to attach a public gateway in zone-1 to a subnet in zone-2.
Message: The IPsec policy cannot be created because your account has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view current IPsec policies, use the GET /ipsec_policies API.
Equivalent CLI command: ibmcloud is ipsec-policies
Message: The name <ipsec_policy_name> is in use already by IPsec policy <ipsec_policy_id>.
Provide a different IPsec policy name. Try again in a few minutes. If this problem persists, contact support.
Message: The IPsec policy <ipsec_policy_id> is in use by one or more connections.
An IPsec policy cannot be deleted if it is in use by one or more connections.
To see which connections are using the IPsec policy, use the GET /ipsec_policies/<ipsec_policy_id>/connections API.
Equivalent CLI command: ibmcloud is ipsec-policy-connections IPSEC_POLICY_ID
Message: The name <ipsec_policy_name> is not a valid IPsec policy name.
A valid IPsec policy name starts with a letter, followed by letters, digits, underscores or hyphens.
Message: The IPsec policy <ipsec_policy_id> could not be found.
You referenced an IPsec policy that does not exist. Please review your request and specify a valid IPsec policy ID. If you are sure the policy exists, contact support.
Message: The same key content already exists.
If this problem persists, contact support.
Message: The same key name already exists.
If this problem persists, contact support.
Message: The key cannot be created because the name is not valid.
The key name must meet the following requirements:
- it must begin with alphabetical character, [A-Za-z]
- it must contain only alphanumeric characters, dashes or underscores, [-A-Za-z0-9_]
- the length must not exceed 65 characters
Message: The key cannot be created because the type is not valid.
The only supported key type is rsa.
Message: The key cannot be created because the public key value is not valid.
The public key provided in the request is not valid. Check the value or regenerate the public key and try again.
In Linux operating systems, you can run the following command to valid the public key ssh-keygen -l -v -f <key_file>.
Message: Certificate instance with CRN <listener_certificate_crn> cannot be found or no permission to access the certificate instance.
Please provide an existing certificate instance CRN or ask your account administrator to grant you access permissions to the provided certificate instance.
Message: Port <listener_port> is used by another listener instance. Please choose a different port.
Choose a different port.
Message: CRN of certificate instance for the HTTPS listener is invalid.
Provide a valid certificate instance CRN.
Message: Listener connection limit <listener_connection_limit> in invalid.
Provide a valid connection limit. THe connection limit must be an integer between 1 and 15000.
Message: Listener port <listener_port> is invalid.
Choose a different port.
Message: Listener protocol <listener_protocol> is invalid.
Provide a valid listener protocol. Acceptable values for listener protocol are http, https, and tcp.
Message: CRN of the certificate instance for the https listener is missing.
The CRN of the certificate instance is a required field.
Message: Listener port is missing.
Listener port is a required field.
Message: Listener protocol is missing.
Listener protocol is a required field. Please provide the listener protocol in your request. The acceptable values are http, https and tcp.
Message: The listener with ID <listener_id> cannot be found.
Please provide an existing listener ID.
Message: Listener cannot be created. Quota of listeners for the load balancer resource has reached the maximum limit.
The quotas per resource are specified in Quotas and limits for VPC{: new_window}.
Message: Listener protocol(<listener_protocol>) and pool protocol(<pool_protocol>) are in conflict.
A listener with https or http protocol can only be associated with a pool with http protocol. Similarly, a tcp listener can only be associated with a tcp pool.
Message: Listener port <listener_port> is one of the reserved ports. The port range of 56500 to 56520 is reserved for management purposes. Choose a different port.
Please choose a different port.
Message: The load balancer with ID <load_balancer_id> cannot be deleted because its status is one of these:
- UPDATE_PENDING
- CREATE_PENDING
- DELETE_PENDING
- MAINTENANCE_PENDING
Please delete the load balancer when it is in ACTIVE status.
Message: Name <load_balancer_name> is used by another load balancer instance. Please choose a different name.
Provide a different name for the load balancer instance. The load balancer name should be unique within the VPC and the account.
Your Load Balancer for VPC will not conflict with your Cloud Load Balancer, because DNS domain names are different for these services, and the name of the Load Balancer for VPC is not included in the DNS name. {: note}
Message: The subnet with ID(s) <subnet_id> has insufficient available IPv4 addresses.
In your request, provide a valid subnet with available IPv4 addresses, in which you wish to create the load balancer.
Message: Load balancer description <load_balancer_description> is not valid.
A load balancer description cannot exceed 255 characters.
Message: Value of is_public <load_balancer_is_public> is not valid.
The value of the load balancer parameter is_public must be either true or false.
Message: Name <load_balancer_name> is invalid.
Names may not be empty. A valid load balancer name starts with a letter, followed by letters, digits, or underscores. The length of the name may not exceed 40 characters.
Message: The subnet with ID <subnet_id> is not valid. Make sure to use an existing subnet with 'available' status.
Please provide valid subnets that are in available status when entering your request to create a load balancer.
Message: 'is_public' field is missing.
The field is is_public is required. Provide a value for the is_public field.
Message: Load balancer name is missing.
The load balancer name is a required field. Provide a name for the load balancer.
Message: Load balancer subnets is missing.
The field subnets is required. In your request to create a load balancer, provide information about the subnets in which you wish to create the load balancer.
Message: Subnet ID is missing.
The Subnet ID is a required field. Provide a subnet ID with your command.
Message: The load balancer with ID <load_balancer_id> cannot be found.
Provide the ID of an existing load balancer.
Message: Load balancer cannot be created. Quota of load balancer instances under your account has reached maximum limit.
Delete an existing load balancer, or contact support to increase the load balancer quota on your account.
The quotas per resource are specified in Quotas and limits for VPC{: new_window}.
Message: The subnet with ID <subnet_id> cannot be found.
In your request, you must provide IDs of existing subnets in which you wish to create the load balancer.
Message: There is nothing to update the load balancer with ID <load_balancer_id>.
No information was given for updating a load balancer instance with the ID you specified.
Message: The load balancer with ID <load_balancer_id> cannot be updated because its status is one of these:
- UPDATE_PENDING
- CREATE_PENDING
- DELETE_PENDING
- MAINTENANCE_PENDING
Please update the load balancer when it is in ACTIVE status.
Message: Member with address <member_address> and port <member_port> already exists in the pool.
Provide a unique member address and port combination in your request.
Message: The specified member IP address <member_ip> is invalid.
In your request, provide a valid IPv4 CIDR address for the member.
Message: The specified member port <member_port> is invalid.
Provide a valid port number. A valid port number is in the range from 1 to 65535.
Message: The specified member weight <member_weight> is invalid.
Provide a valid member weight. The value must be an integer between 0 and 100.
Message: Member with IP address <member_IP> does not belong to any subnets in the Region and VPC of the load balancer.
In your request, provide the address of a member that belongs to a subnet in same the Region and VPC as the load balancer.
Message: Member address is missing.
Member address is a required field. Provide a value for member address.
Message: Member port is missing.
Member port is a required field. Provide a value for member port.
Message: Member with ID <member_id> cannot be found.
Provide an existing member ID.
Message: Member cannot be created. Quota of member instances under the pool has reached maximum limit.
The quotas per resource are specified in Quotas and limits for VPC{: new_window}.
Message: None
For further instructions to fix this problem, refer to the API documentation{: new_window}. If this problem persists, contact support.
Message: The version parameter is required, and it must be of the form YYYY-MM-DD.
A version parameter is required for all API requests. The version must comply with the format YYYY-MM-DD. For single-digit months or dates, such as January 1st, the version should look like 2019-01-01. The date given in the version parameter must be later than 2019-01-01 but before the current date. Check out these API examples for how to provide the version parameter.
Message: CIDR conflicts with existing Address Prefix in VPC.
You might see this message if you provided a network CIDR that conflicts with an existing network CIDR in the same IP space.
To find the existing CIDRs in Address Prefixes for the VPC, run the API command GET /v1/vpcs/<vpc-id>/address_prefixes and look at the cidr values of the response. Check the value of cidr to make sure that the CIDR you've provided is not in use by other Address Prefixes.
If you are using the CLI, run the command ibmcloud is vpc-addrs <vpc-id> and check the value of CIDR Block for conflicts.
To find the existing CIDRs in subnets, run the API command GET /v1/subnets to list all the subnets for the VPC. Then, run the API command GET /v1/subnets/<subnet-id> for each subnet in the VPC and check the value of ipv4_cidr_block in the response. Check the value of ipv4_cidr_block to make sure that the CIDR you've provided is not in use by other Address Prefixes.
If you are using the CLI, run the command ibmcloud is subnets to list all the subnets for the VPC. Then, run the command ibmcloud is subnet <subnet-id> for each subnet in the VPC, and check for conflicts with the value of IPv4 CIDR in the CLI output.
Message: The request is not authorized.
You may see this error is if your IAM token is missing or expired. For instructions on how to generate a token, refer to Creating a VPC using the REST APIs. If the token is not expired, make sure the account you are using is authorized to use this function and you have the correct permissions.
If you have correct authorization but you are still getting this error, contact support.
Message: Please check whether the resource you are requesting exists.
You referenced a resource that does not exist or one to which you do not have access. Please review your request to ensure that you specified the proper IDs and references.
Refer to the API documentation{: new_window} for additional help. If this problem persists, contact support.
Message: None
The method is not implemented. Check your request to make sure you are calling a valid API{: new_window}. Contact support if you expect this API to be implemented.
Message: The provided CIDR does not fit in any of the address prefixes in the provided zone.
This error occurs if a user is trying to create a subnet with a CIDR that does not fall into any address prefixes for the given zone.
Run GET /vpcs/{vpc_id}/address_prefixes to get the list of address prefixes for the VPC. If using the CLI, you can run ibmcloud is vpc-address-prefixes to list all address prefixes for your VPC. Look at the cidr and zone values of the response and make sure the subnet's cidr is a subset of the cidr of the address prefix for the zone you are trying to create it.
Message: The request would exceed the quota for a resource type.
The quotas per resource are specified in Quotas and limits for VPC{: new_window}.
Message: None
Your instance must be running before you can retrieve the password. Try again in a few minutes. If this problem persists, contact support.
Message: Pool cannot be deleted because it is still associated with one or more listeners.
Ensure the pool is disassociated from any listeners and try again.
Message: Pool name <pool_name> is already used by another pool. Choose a different name.
Choose a different pool name.
Message: Name <pool_name> is invalid.
Provide a valid pool name. A valid load balancer name starts with a letter followed by letters, digits, hyphens. The length of the name may not exceed 40 characters.
Message: Pool session persistence value is not valid.
Provide a valid session persistence value. Acceptable value is SOURCE_IP.
Message: Load balancing algorithm is missing.
Load balancing algorithm is a required field. Provide the load balancing algorithm in your request. The acceptable values are round_robin, weighted_round_robin, and least_connections.
Message: Pool health monitor is missing.
Pool health monitor is a required field.
Message: Pool members are missing.
Provide pool members.
Message: Pool name is missing.
Pool name is a required field.
Message: Pool protocol is missing.
Pool protocol is a required field. Provide the pool protocol in your request. The acceptable values are http and tcp.
Message: The pool with ID <pool_id> cannot be found.
Provide an existing pool ID.
Message: Pool cannot be created. Quota of pools for the load balancer resource has reached maximum limit.
The quotas per resource are specified in Quotas and limits for VPC{: new_window}.
Message: Cannot delete a public gateway when it is in use.
The public gateway currently is attached to one or more subnets. You must detach the public gateway from all subnets before you can delete it.
To see which subnet is using the public gateway, use the GET /v1/subnets?version=2019-01-01&generation=1 API. Equivalent CLI command: ibmcloud is subnets. To detach the public gateway from the subnet, use the API command DELETE /v1/subnets/{subnet_id}/public_gateway?version=2019-01-01&generation=1 or the CLI command ibmcloud is subnet-public-gateway-detach.
Message: Too many requests within a short time.
This error message is returned if too many requests are received within a specified time interval. Wait a while and try again.
Message: The interface cannot be attached or detached until the instance appears in Active state.
The instance must be active before its network interfaces can be attached to a security group. Use GET /v1/instances/{id}?version=2019-01-01&generation=1 or ibmcloud is instance to check on the status of the instance. Once the status is running, please try again. If this problem persists, contact support.
Message: The interface is already attached to the security group.
The interface is already attached to the security group. Use GET /v1/security_groups/{id}/network_interfaces?version=2019-01-01&generation=1 or ibmcloud is security-group-network-interfaces to view attached interfaces.
If this problem persists, contact support.
Message: The security group already exists.
Security group names must be unique within a VPC. A security group with that name already exists in the targeted VPC. Use GET /v1/security_groups?version=2019-01-01&generation=1 or ibmcloud is security-groups to view current security groups.
For further instructions to fix this problem, refer to the API documentation or the Using Security Groups document{: new_window}.
If this problem persists, contact support.
Message: Cannot delete the security group while interfaces are attached.
Detach all interfaces before deleting the security group. Use DELETE /v1/security_groups/{id}/network_interfaces/{id}?version=2019-01-01&generation=1 or ibmcloud is security-group-network-interface-remove to detach an interface.
For further instructions to fix this problem, refer to the API documentation or the Using Security Groups document{: new_window}.
If this problem persists, contact support.
Message: Exceeded limit of interfaces per security group.
Attaching another interface to the security group would exceed the limit of interfaces per security group. The quotas per resource are specified in Quotas and limits for VPC{: new_window}. Evaluate your strategy and consider creating another security group with similar rules.
For further instructions to fix this problem, refer to the API documentation or the Using Security Groups document{: new_window}.
If this problem persists, contact support.
Message: The default security group cannot be removed when it is the only security group attached.
A network interface must be attached to at least one security group. It will be attached to the VPC's default security group if one is not specified. Attach the interface to a different security group, then try again to detach it from the default security group. For information on the default security group, refer to the Using Security Groups document{: new_window}.
If this problem persists, contact support.
Message: Exceeded security group limit.
You have attempted to create a new security group, but you are currently at your account quota. The quotas per resource are specified in Quotas and limits for VPC{: new_window}. Evaluate your strategy for assigning instances to security groups. It is often possible to reduce the overall number of security groups by assigning multiple instances to the same security group. This strategy will reduce the number of security groups, and drop you below your account quota. In rare cases, generally for large organizations, there is a need for expanding the quota. In this case, please contact support to inquire if this is possible.
Message: The interface cannot be attached because it is not active.
Network interfaces must be active before attaching to security groups. Use GET /v1/instances/{id}/network_interfaces/{id}?version=2019-01-01&generation=1 or ibmcloud is instance-network-interface to view the status of an interface. Once the status is 'available', please try again. If this problem persists, contact support.
Message: The interface is not attached.
The interface is not attached to the security group. Use GET /v1/security_groups/{id}/network_interfaces?version=2019-01-01&generation=1 or ibmcloud is security-group-network-interfaces to view attached interfaces.
For further instructions to fix this problem, refer to the API documentation or the Using Security Groups document{: new_window}.
If this problem persists, contact support.
Message: The interface and security group are in different VPCs.
To attach a network interface to a security group, the instance must be in the same VPC as the security group. Use GET /v1/security_groups/{id}?version=2019-01-01&generation=1 or ibmcloud is security-group to view the security groups details and VPC. Use GET /v1/instances/{id}?version=2019-01-01&generation=1 or ibmcloud is instance to view the instance details and VPC.
Message: Cannot delete the security group while it has pending instance orders.
If an instance was created with security group(s) specified on the network interfaces, the instance and network interfaces must be active before the security group can be deleted. Use GET /v1/security_groups/{id}/network_interfaces?version=2019-01-01&generation=1 or ibmcloud is security-group-network-interfaces to view attached network interfaces and their status. Once the status of the interfaces is 'available', please try again. If this problem persists, contact support.
Message: TCP/UDP max port cannot be less than min port.
The maximum port value cannot be less than the minimum port value. Specify a maximum port value that is larger than the minimum port value.
Message: Port range must be unset, or both a minimum and maximum port must be set for 'tcp' and 'udp'.
Rules with a 'tcp' or 'udp' protocol may have an unset port range (to apply the rule to all traffic), or they may specify a port range. To restrict traffic to a single port, set both the minimum and maximum port to the port value. For example, the following command would create a rule to allow SSH on port 22: ibmcloud is security-group-rule-add <id> inbound tcp --port-min 22 --port-max 22.
For further information on security group rule configurations, refer to the API documentation.
Message: A port range was specified with a protocol of 'icmp'. A port range is only valid for a protocol of 'tcp' or 'udp'.
Rules with an 'icmp' protocol have a type and code. Rules with 'tcp' or 'udp' protocols have a port range. For further information on security group rule configurations, refer to the API documentation.
Message: The remote group is not in the same VPC as this security group.
Security group rules may refer to a remote security group, allowing traffic between attached interfaces of the two groups. Remote security groups must be in the same VPC. Use GET /v1/security_groups?2019-01-01 or ibmcloud is security-groups to view current security groups and their VPCs.
For further instructions to fix this problem, refer to the Using Security Groups document{: new_window}.
Message: Cannot delete the security group while remoting rules are attached.
The security group contains one or more rules referencing a remote security group. Use GET /v1/security_groups/{id}/rules?version=2019-01-01&generation=1 or ibmcloud is security-group-rules to view the rules. The 'remote' field will specify any remote security groups. Try again after deleting or editing the remoting rule.
For further instructions to fix this problem, refer to the API documentation or the Using Security Groups document{: new_window}.
Message: Exceeded limit of remoting rules per security group.
Adding another rule refering to a remote security group would exceed the limit of remoting rules per security group. The quotas per resource are specified in Quotas and limits for VPC{: new_window}.
Message: Exceeded limit of rules per security group.
Adding a rule would exceed the limit of rules per security group. The quotas per resource are specified in Quotas and limits for VPC{: new_window}. Evaluate your strategy and consider creating another security group.
Message: Exceeded limit of security groups per interface.
Attaching this interface to another security group would exceed the limit of security groups per interface. The quotas per resource are specified in Quotas and limits for VPC{: new_window}. Evaluate your strategy and consider adding rules to an existing security group.
Message: An 'icmp' type/code was given, but the requested protocol was not 'icmp'. Set the protocol to 'icmp' or specify a port range.
Only rules with an 'icmp' protocol have a type and code. Rules with 'tcp' or 'udp' protocols have a port range. For further information on security group rule configurations, refer to the API documentation.
Message: Cannot delete the default security group for a VPC.
The default security group cannot be deleted. For information on the default security group, refer to the guide on Updating the default security group.
Message: None
For further instructions to fix this problem, refer to the API documentation{: new_window}. If this problem persists, contact support.
Message: CIDR conflicts with existing Subnet in VPC.
Run the GET /subnets API to retrieve all subnets in VPC. Check the value of ipv4_cidr_block to make sure that the CIDR you have provided is not in use by other subnets.
If using the CLI, you can run ibmcloud is subnets and look at "Subnet CIDR" value for conflicts.
Refer to the API documentation{: new_window} for additional help. If this problem persists, contact support.
Message: Cannot delete the subnet until it is empty. Delete any resources in the subnet and retry.
There was a request to delete a subnet, but the subnet still has resources in it. Subnets may have instances, VPNs, load balancers, or public gateways in them. You must delete your resources in the subnet before you can delete the subnet.
In some situations, this error can occur even when the console shows 0 VSIs and 0 load balancers. Deletion is asynchronous, and it may take a few minutes for the internal status to change. Try your subnet deletion again in a few minutes.
If this problem persists, contact support.
Message: Cannot delete the subnet while it is attached to a public gateway. Detach the public gateway and retry.
There was a request to delete a subnet, but the subnet still has a public gateway attached to it. You must delete or detach the public gateway before you can delete the subnet.
If using the CLI, you can run ibmcloud is public-gateways to list the public gateways and ibmcloud is subnet-public-gateway-detach to detach a public gateway from a subnet.
If this problem persists, contact support.
Message: Cannot delete the subnet while it contains IP addresses. Please delete any server instance associated with the IP address and retry.
There was a request to delete a subnet, but the subnet still contains IP addresses. You must delete the server instance associated with the IP address before you can delete the subnet.
If using the CLI, you can run ibmcloud is instances to list the server instances. Look at the "Address" value to determine its IP Address and "Status" to determine its status. Run ibmcloud is instance-delete to delete a server instance that doesn't already have a status of "deleting".
In some situations, this error can occur even when the console shows 0 VSIs. Deletion is asynchronous, and it may take a few minutes for the internal status to change. Try your subnet deletion again in a few minutes.
If this problem persists, contact support.
Message: Cannot delete the subnet while it contains a load balancer. Delete the load balancer and retry.
There was a request to delete a subnet, but the subnet still contains a load balancer. You must delete the load balancer before you can delete the subnet.
If using the CLI, you can run ibmcloud is load-balancers to list the load balancers. Look at the "Subnets" value to determine its subnet, and "Status" to determine its status. Run ibmcloud is load-balancer-delete to delete a load balancer that doesn't already have a status of "deleting".
In some situations, this error can occur even when the console shows 0 load balancers. Deletion is asynchronous, and it may take a few minutes for the internal status to change. Try your subnet deletion again in a few minutes.
If this problem persists, contact support.
Message: Cannot delete the subnet while it contains a VPN gateway. Delete the VPN gateway and retry.
There was a request to delete a subnet, but the subnet still has a VPN gateway attached to it. You must delete the VPN gateway before you can delete the subnet.
If using the CLI, you can run ibmcloud is vpn-gateways to list the VPN gateways. Look at the "Subnets" value to determine its subnet and "Status" to determine its status. Run ibmcloud is vpn-gateway-delete to delete a VPN gateway that doesn't already have a status of "deleting".
In some situations, this error can occur even when the console shows 0 VPN gateways. Deletion is asynchronous, and it may take a few minutes for the internal status to change. Try your subnet deletion again in a few minutes.
If this problem persists, contact support.
Message: The subnet <subnet_id> is in an invalid state for the requested operation.
The subnet must be in available status before you can operate it. Try again in a few minutes. If this problem persists, contact support.
Message: The target already has floating IP attached.
There was a request to attach a floating IP address to a server’s network interface, but the network interface already has a floating IP attached to it.
To find the floating IP address currently attached to a network interface, run the API command GET /v1/floating_ips?version=2019-01-01&generation=1 and look for the network interface ID in the target.id field.
If you are using the CLI, run the command ibmcloud is floating-ips and look at the Target value. Be aware that the CLI truncates the network interface ID at the first dash (“-“) character. For example, a server’s primary network interface with an ID of abdfcb29-b3c5-4e4a-b7a0-cf0300154699 appears as primary(abdfcb29-.) in the CLI output.
Message: The service token was expired or invalid.
For further instructions to fix this problem, refer to the API documentation{: new_window}. If this problem persists, contact support.
Message: The service token was empty or did not exist in the request.
Recreate a token and try again.
Message: The value supplied was not a valid option.
One of the fields supplied has a value that must come from an enumeration of possible values.
For Network ACL rules, you may specify a direction:
direction* string
Whether the traffic to be matched is inbound or outbound
Enum:
[ inbound, outbound ]
For example, the following value would be invalid because northbound is not a valid option in the enumeration [ inbound, outbound ].
{
"direction":"northbound"
}Refer to the API documentation{: new_window} or the CLI reference{: new_window} for acceptable values.
Message: The JSON provided did not match the expected structure.
To fix this problem, be sure the content of your request is valid JSON and that your request conforms to the API documentation{: new_window}.
Message: The value is not a valid CIDR.
The value must be a valid internal CIDR block with a 0 host part.
Certain IP address ranges are reserved. More information about reserved IP ranges is available in our overview of Using your VPC with Regions and Subnets{: new_window}.
Message: The value is not a valid IPv4 CIDR.
Must be a IPv4 internal CIDR block with a 0 host part.
Certain IP address ranges are reserved. More information about reserved IP ranges is available in our overview of Using your VPC with Regions and Subnets{: new_window}.
Message: The value is not a valid IPv6 CIDR.
Currently, IPv6 is not supported. Please use an IPv4 address.
Message: The value is not a valid address.
Must be a valid IP address.
A list of individually reserved IP addresses is given in the Regions and Subnets document.
Message: The value is not a valid IPv4 address.
Provide a valid IPv4 address.
Message: The value is not a valid IPv6 address.
Give a valid IPv6 address. Currently, IPv6 is not supported; use an IPv4 address.
Message: The value type does not match the field type.
To fix this problem, be sure the content of your request conforms to the API documentation{: new_window} for the endpoint you are calling.
Message: A value provided for a parameter is larger than allowed.
Provide a smaller value that meets the maximum as given by the specification{: new_window}.
Message: A value provided for a parameter is smaller than allowed.
You may get this error if you try to create a subnet with total_ipv4_address_count less than 8.
Provide a larger value that meets the minimum as given by the specification{: new_window}.
Message: The field supplied must be null.
Be sure the value is null. Refer to the API documentation{: new_window}.
Here is an invalid example:
{
"name": null
}Message: The value must match one of the subschemas.
Make sure your request conforms to the API documentation{: new_window}.
Message: The discriminator field forbids this substructure.
For example, if you specify
{
protocol: icmp
port_min: 5
port_max: 100
}
The protocol is icmp, and port_min is a tcp field, so you'll get an error.
- validation_discriminator_required for missing
icmprules - validation_discriminator_forbidden for
tcpfields withicmpspecified
Make sure your request conforms to the API documentation{: new_window}. If this problem persists, contact support.
Message: None
Make sure your request conforms to the API documentation{: new_window}. If this problem persists, contact support.
Message: The value is not a valid name.
Make sure your request conforms to the API documentation{: new_window}. If this problem persists, contact support.
Message: The value is not a valid HREF.
Make sure your request conforms to the API documentation{: new_window}. If this problem persists, contact support.
Message: None
Make sure your request conforms to the API documentation{: new_window}. If this problem persists, contact support.
Message: Missing a required field.
Make sure your request conforms to the API documentation{: new_window}. If this problem persists, contact support.
Message: The field supplied must be unique.
You might have specified a name that is already in use. Please try a different value.
Make sure your request conforms to the API documentation{: new_window}. If this problem persists, contact support.
Message: The volume attachment cannot be deleted.
This operation is not allowed. The boot volume's volume attachment cannot be deleted because the boot volume is required by the instance.
Message: The volume attachment could not be updated because the request is invalid.
The volume attachment could not be updated for either of these reasons:
- The boot volume's volume attachment cannot be renamed
- The boot volume's volume attachment
delete_volume_on_instance_deletefield cannot be set totrue
Message: The maximum volume capacity allowed is 2000 GB.
The volume capacity you specified exceeds the maximum volume capacity. Specify a value between 10 and 2000 GB. See the IBM Cloud Block Storage for VPC documentation for accepted capacity ranges for a Custom profile.
Message: The required volume capacity value is missing in the request.
When you create a volume, you must specify a volume capacity based on this profile definition. For more information, see the IBM Cloud Block Storage for VPC documentation.
Message: The volume capacity should be greater than zero.
When creating a volume, the capacity value specified in the request must be a positive number between 10 GB and 2000 GB. See the IBM Cloud Block Storage for VPC documentation for supported volume capacity values.
Message: The volume encryption key specified in the request does not belong to current user's account.
The Key Protect root key CRN does not match your IAM authorization account ID. Specify a different Key Protect root key CRN for your IAM account. See the Key Protect documentation for more information.
Message: The volume encryption key specified in the request cannot be used for the current environment.
The volume encryption key that you specified in the request cannot be used in the current environment. Provide a root key CRN applicable to your environment.
Message: The volume encryption key CRN specified in the request is not valid.
The Key Protect CRN you provided is not valid. Obtain the CRN of the root key in the Cloud Identity and Access Management service. For more information, see the IBM Cloud Block Storage for VPC documentation.
Message: The volume encryption key specified in the request is not active.
Activate the exising key or provide a new key. If you cannot activate your own key, contact your system administrator or customer support.
Message: You are not authorized to access the provided volume encryption key.
Provide another encryption key for which you have access, or contact your system administrator to obtain access to the current key.
The volume encryption key feature is not supported.
A volume could not be created using your encryption key. This version supports volumes with provider-managed encryption only. To use your own encryption key, use a version of Block Storage for VPC that supports customer-managed encryption. Contact customer support for more information.
Message: The volume ID specified in the request parameter is not valid.
The volume ID you specified is not in the correct format. Verify that you correctly entered the volume ID and try again. If you're not sure of the volume ID, specify ibmcloud is volumes in the CLI or GET volumes in the API and search the list of volumes.
Message: The volume ID is missing in the request parameter.
You must provide the volume ID in the request parameter when getting a specific volume.
Message: The volume IOPS should be greater than zero.
When creating a volume, the IOPS value specified in the request must be a positive number. See the IBM Cloud Block Storage for VPC documentation for supported IOPS values.
Message: The volume name specified in the request already exists.
Specify a unique volume name.
Message: A volume with the specified ID is not found.
Verify that the volume ID you entered is correct and try again. For a list of volumes, specify ibmcloud is volumes in the CLI or GET volumes in the API.
Message: The requested operation is not supported in this release.
Contact customer support for more information.
Message: The volume profile specified in the request is not valid for the provided capacity and/or IOPS.
The volume capacity and/or IOPS value that you specified in the request is not allowed by the volume profile. See the IBM Cloud Block Storage for VPC documentation for valid minimum and maximum capacity and IOPS values for a Custom profile.
Message: The volume profile specified in the request cannot accept custom IOPS.
Your volume profile does not accept a Custom IOPS value. You might have specified a Tiered IOPS profile, which does not require that you specify an IOPS value. If you want to provide a specific IOPS value, use the Custom IOPS profile.
Message: The required volume profile name is missing in the request.
The volume profile name is missing in the request body when creating a volume or in the request parameter when getting a volume. Provide a volume profile name in your request and try again. If you don't know the volume profile name, specify ibmcloud is volume-profiles in the CLI or use GET $rias_endpoint/v1/volume/profiles/?version=YYYY-MM-DD in the API request and search the list.
Message: A volume profile with the specified name is not found.
A volume profile with that name could not be found. Verify that you provided the correct volume profile name. If you don't know the volume profile name, specify ibmcloud is volume-profiles in the CLI or use GET $rias_endpoint/v1/volume/profiles/?version=YYYY-MM-DD in the API request and search the list.
Message: The volume quota has been reached.
You are out of quota for the current account. Try deleting some volumes or contact customer support to increase your quota. See the documentation for information about quotas for the Virtual Private Cloud infrastructure.
Message: The resource group ID specified in the request is not valid.
The resource group ID that you specified in the request is not valid. Verify the correct resource group ID. From the CLI, use the ibmcloud is volume VOLUME_ID command. The resulting information will include the resource group and resource group ID. See the IBM Cloud CLI for VPC Reference for more information.
Message: The current action is not authorized on the specified resource group.
You are not authorized to list or create volumes in the specified resource group. Use a different resource group for which you have permission or request permission from your administrator for list and create privileges on the resource group.
Message: A resource group with the specified ID could not be found.
The resource group ID could not be found because you might have entered it incorrectly or it does not exist. Verify the correct resource group ID. From the CLI, use the ibmcloud is volume VOLUME_ID command. The resulting information will include the resource group and resource group ID. See the IBM Cloud CLI for VPC Reference for more information.
Message: A volume with the ID specified as the page start parameter is not found.
The volume ID that you specified in the start parameter of the list volume call could not be found. Verify that the volume ID is correct and whether you have access to the volume.
Message: The volume with the specified ID is not available.
The volume is not in an Available state; it's status might be in a Pending state. Wait for volume to become available and try again. If the volume is being deleted, use a different volume. To check the volume's status, specify ibmcloud is volume VOLUME_ID in the CLI or use GET $rias_endpoint/v1/volumes/$volume_id?version=YYYY-MM-DD in the API request.
Message: The volume is still attached to an instance.
You cannot delete a volume that is still attached to a VSI. If you set automatic deletion for the volume, wait for the VSI to be deleted and volume will be detached and deleted. If you did not set automatic deletion, detach the volume manually.
Message: Invalid volume template provided.
You provided an invalid volume template for creating a volume. See the Regional Infrastructure Service API Reference{: new_window} to verify that you are providing the correct parameters in the request body.
Message: The volume update request is not valid.
The update request body property that you specified is not valid. See the Regional Infrastructure Service API Reference{: new_window} for information and correct API request syntax.
Message: The VPC cannot be deleted because it is not empty.
All resources in the VPC must be deleted before the VPC can be deleted. A VPC contains instances, subnets, public gateways, load balancers and VPN gateways, and some of these resources contain resources as well. Refer to How to Delete a VPC documentation for details.
If this problem persists, contact support.
Message: The resources are in different VPCs.
The resources must be in the same VPC. For example, if you are attempting to attach a public gateway to a subnet, the public gateway must be in the same VPC as the subnet.
To determine which VPC contains the public gateway, run the GET /public_gateways/{id} command and look at the "vpc" value. The equivalent CLI command is ibmcloud is public-gateway <id>.
Message: The cidr_type CIDR blocks have duplicates: <cidrs>.
There are duplicate CIDR blocks provided when creating the connection. Ensure the CIDR blocks are unique.
For further instructions to fix this problem, refer to the API documentation{: new_window}. If this problem persists, contact support.
Message: A CIDR block could not be added to the VPN connection <vpn_connection_id>.
Provide a valid CIDR that meets the requirements given by the specification.
For further instructions to fix this problem, refer to the API documentation{: new_window}. If this problem persists, contact support.
Message: A CIDR block could not be deleted from the VPN connection <vpn_connection_id>.
Provide a valid CIDR that exists on the connection. A connection must have at least one local and peer CIDR.
To view the connection's CIDR blocks, use the GET /vpn_gateways/<vpn_gateway_id>/connections/<vpn_connection_id> API and check the local_cidrs and peer_cidrs fields.
Equivalent CLI command: ibmcloud is vpn-gateway-connection VPN_GATEWAY_ID CONNECTION_ID
Message: The CIDR block was not found in the VPN connection <vpn_connection_id>.
Provide a valid CIDR that is in the connection.
To view the connection's CIDR blocks, use the GET /vpn_gateways/<vpn_gateway_id>/connections/<vpn_connection_id> API and check the local_cidrs and peer_cidrs fields.
Equivalent CLI command: ibmcloud is vpn-gateway-connection VPN_GATEWAY_ID CONNECTION_ID
Message: The CIDR block <cidr_block> does not represent a valid address.
The value must be a valid internal CIDR with no host bits set.
To view the connection's CIDR blocks, use the GET /vpn_gateways/<vpn_gateway_id>/connections/<vpn_connection_id> API and check the local_cidrs and peer_cidrs fields.
Equivalent CLI command: ibmcloud is vpn-gateway-connection VPN_GATEWAY_ID CONNECTION_ID
Message: The CIDR block <cidr_block_1> overlaps with <cidr_block_2>. Two peer CIDR blocks cannot overlap on the same VPC and two local CIDR blocks cannot overlap on the same connection.
Provide a valid CIDR that meets the requirements given by the specification.
To view the connection's CIDR blocks, use the GET /vpn_gateways/<vpn_gateway_id>/connections/<vpn_connection_id> API and check the local_cidrs and peer_cidrs fields.
Equivalent CLI command: ibmcloud is vpn-gateway-connection VPN_GATEWAY_ID CONNECTION_ID
Message: The name <vpn_connection_name> is already in use by VPN connection <vpn_connection_id>.
Provide a different connection name. Try again in a few minutes. If this problem persists, contact support.
Message: The name <vpn_connection_name> is not a valid VPN connection name.
A valid connection name starts with a letter, followed by letters, digits, underscores, or hyphens.
Message: The pre-shared key (PSK) <psk> is not in the valid format.
A valid PSK should only contain 6 to 128 characters which are letters, digits, -,+,&,!,@,#,$,%,^,*,(,),,,.,:,_.
Message: At least one local CIDR block is required when creating a VPN connection.
Provide a valid local CIDR that meets the requirements given by the specification.
For further instructions to fix this problem, refer to the API documentation{: new_window}.
Message: Local CIDR blocks across VPN connections for the VPN gateway <vpn_gateway_id> has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view the current local CIDR blocks across VPN connections, use the GET /vpn_gateways/<vpn_gateway_id>/connections API and check the local_cidrs field for each connection.
Equivalent CLI command: ibmcloud is vpn-gateway-connections VPN_GATEWAY_ID
Message: Local CIDR blocks for the VPN connection has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view the current local CIDR blocks for a VPN connection, use the GET /vpn_gateways/<vpn_gateway_id>/connections/<vpn_connection_id> API and check the local_cidrs field.
Equivalent CLI command: ibmcloud is vpn-gateway-connection VPN_GATEWAY_ID CONNECTION_ID
Message: The VPN connection <vpn_connection_id> could not be found.
Check whether the connection ID is correct. Try again in a few minutes. If this problem persists, contact support.
Message: At least one peer CIDR block is required when creating a VPN connection.
Provide a valid peer CIDR that meets the requirements given by the specification.
For further instructions to fix this problem, refer to the API documentation{: new_window}.
Message: Peer CIDR blocks across VPN connections for the VPN gateway <vpn_gateway_id> has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view the current peer CIDR blocks across VPN connections, use the GET /vpn_gateways/<vpn_gateway_id>/connections API and check the peer_cidrs field for each connection.
Equivalent CLI command: ibmcloud is vpn-gateway-connections VPN_GATEWAY_ID
Message: Peer CIDR blocks for the VPN connection has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view the current peer CIDR blocks for a VPN connection, use the GET /vpn_gateways/<vpn_gateway_id>/connections/<vpn_connection_id> API and check the peer_cidrs field.
Equivalent CLI command: ibmcloud is vpn-gateway-connection VPN_GATEWAY_ID CONNECTION_ID
Message: The VPN connection cannot be created because the VPN gateway <vpn_gateway_id> has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view the current VPN connections for a VPN gateway, use the GET /vpn_gateways/<vpn_gateway_id>/connections API.
Equivalent CLI command: ibmcloud is vpn-gateway-connections VPN_GATEWAY_ID
Message: Failed to add a static route for the peer CIDR block <peer_cidr>.
Try again in a few minutes. If this problem persists, contact support.
Message: Failed to remove a static route for the peer CIDR block <peer_cidr>.
Try again in a few minutes. If this problem persists, contact support.
Message: CIDR blocks cannot be changed when updating a connection. Please use the correct API when creating or deleting CIDR blocks.
Provide a valid request value that meets the requirements given by the specification.
For further instructions to fix this problem, refer to the API documentation{: new_window}.
Message: The name <vpn_gateway_name> is already in use by VPN gateway <vpn_gateway_id>.
Provide a different VPN gateway name. Try again in a few minutes. If this problem persists, contact support.
Message: The VPN gateway could not be initialized.
Try again in a few minutes. If this problem persists, contact support.
Message: The name <vpn_gateway_name> is not a valid VPN gateway name.
A valid VPN gateway name starts with a letter, followed by letters, digits, underscores, or hyphens.
Message: The VPN gateway <vpn_gateway_id> is in an invalid state for the requested operation.
VPN Gateway must be in available status before you can operate it. Try again in a few minutes. If this problem persists, contact support.
Message: Unable to create an IP address for the VPN gateway.
Try again in a few minutes. If this problem persists, contact support.
Message: The VPN gateway <vpn_gateway_id> could not be found.
Check whether the VPN gateway ID is correct. Try again in a few minutes. If this problem persists, contact support.
Message: Could not find the subnet <subnet_id> for the given VPN gateway.
You've referenced a subnet that does not exist. Please review your request to ensure that you specified the proper subnet ID. Try again in a few minutes. If this problem persists, contact support.
Message: The VPN gateway could not be created due to subnet status.
Provide a subnet that is in available status. Try again in a few minutes. If this problem persists, contact support.
Message: The VPN Gateway cannot be created because your account and/or the region has reached the quota.
The quotas per resource are specified on the Quotas{: new_window} page.
To view the current VPN gateways, use the GET /vpn_gateways API.
Equivalent CLI command: ibmcloud is vpn-gateways
Message: The resources must belong to the same zone.
- When you attach a volume, make sure the volume and the instance are in the same zone.
- When you associate a floating IP, make sure the floating IP and the subnet are in the same zone.