If an error occurs when an API is called, error information is returned. This section describes the error information for VPN APIs (excluding native OpenStack APIs).
{
"code": "VPN.0001",
"message": "invalid request:xxx"
}
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided for the following error codes.
Status Code |
Error Code |
Error Information |
Handling Measure |
|---|---|---|---|
400 |
VPN.0001 |
invalid request:xxx |
Contact technical support. |
500 |
VPN.0002 |
server error: xxx |
Contact technical support. |
403 |
VPN.0003 |
Authentication failed: xxx |
Obtain the required permissions. |
404 |
VPN.0004 |
resource not found |
Check whether the resource ID is correct or whether the resource exists under the tenant. |
400 |
VPN.0030 |
The system is busy, please try later. |
Try again later. |
400 |
VPN.0031 |
Repeated operation. |
Try again later. |
Status Code |
Error Code |
Error Information |
Handling Measure |
|---|---|---|---|
500 |
VPN.0005 |
Service authentication failure |
Grant the permission for calling APIs. |
500 |
VPN.0006 |
IAM service unavailable |
Contact technical support. |
403 |
VPN.0007 |
is not authorized to perform |
Grant the permission for calling APIs. |
425 |
VPN.0009 |
Connection %s is deleting. |
Try again later. |
401 |
VPN.0010 |
Token authentication failed: %s |
Use a correct IAM token. |
400 |
VPN.0012 |
IP address %s is occupied |
Enter an IP address that is not in use. |
400 |
VPN.0013 |
Unsupported attribute: %s |
Enter a proper field. |
504 |
VPN.0014 |
The system is busy, please try again later |
Try again later. |
400 |
VPN.0015 |
The tag policy not allow the specified value for the following tag key: %s |
Modify the tag content to comply with the tag policy or modify the tag policy. |
409 |
VPN.0016 |
VPN gateway is not ready, please try again later |
Try again later. |
409 |
VPN.0017 |
logic instance is not ready, please try again later |
Try again later. |
400 |
VPN.0018 |
ER feature is disabled |
Delete the parameters related to the association between the VPN and the enterprise router, and try again. |
400 |
VPN.0101 |
Invalid EIP bandwidth size: %s |
Enter a proper EIP bandwidth. |
400 |
VPN.0102 |
EIP %s has invalid bandwidth status: %s |
Use an available EIP. |
400 |
VPN.0103 |
EIP %s has invalid status: %s |
Use an available EIP. |
400 |
VPN.0104 |
%s is not in subnet: %s |
Use an available IP address. |
400 |
VPN.0105 |
Flavor %s cannot update to specification %s with network type %s |
Select a proper specification. |
400 |
VPN.0107 |
Private IPs must be different with each other |
Use an available IP address. |
400 |
VPN.0108 |
Invalid IP format, %s |
Use an available IP address. |
400 |
VPN.0109 |
access_private_ip_1 and access_private_ip_2 must be both filled or both left empty |
Set both access_private_ip_1 and access_private_ip_2, or leave both of them empty. |
400 |
VPN.0110 |
%s is a system reserved address and cannot be allocated |
Use an available IP address. |
400 |
VPN.0111 |
Private IP %s is occupied |
Use an available IP address. |
400 |
VPN.0112 |
EIP %s has been bound to an instance. |
Use an available EIP. |
400 |
VPN.0203 |
Invalid IP address. |
Use an available IP address. |
400 |
VPN.0204 |
Class D(multicast address), class E(reserved address), and loopback address(starting with 127) are not supported. |
Use an available IP address. |
400 |
VPN.0218 |
VPN Connection: update VPC routing table err : %s |
Use an available IP address. |
400 |
VPN.0219 |
VPN Connection: update VPC routing table err : %s |
Use an available IP address. |
400 |
VPN.0220 |
VPN Connection: update VPC routing table err : %s |
Delete unnecessary routes from the route table, or increase the route quota. |
400 |
VPN.0285 |
Subnet %s only has %s IP available, but %s is required |
Release IP addresses or expand the IP address range. |
400 |
VPN.0304 |
Query connection log is only supported for newer VPN gateway. |
Check the version of the gateway to be queried. |
400 |
VPN.0305 |
Query connection log does not support the connection of the policy-template type. |
Use the correct connection type. |
400 |
VPN.0306 |
The connection is being updated, please try again later. |
Try again later. |
400 |
VPN.0381 |
VPN connection %s already has connection monitor |
Do not create a connection monitor that already exists. |
429 |
VPN.0429 |
Too Many Request, Please try again later |
Try again later. |
400 |
VPN.0506 |
The gateway is being created, please try again later. |
Try again later. |
400 |
VPN.0507 |
The gateway is being updated, please try again later. |
Try again later. |
400 |
VPN.0508 |
The gateway is being deleted. |
Try again later. |
404 |
VPN.0509 |
The gateway does not exist. |
Check whether the gateway ID is correct. |
400 |
VPN.0516 |
Non-fixed IP not supported in post-paid situation |
Use an available IP address. |
400 |
VPN.0517 |
The connection group of the target flavor %s does not match the current one: %s |
Enter a proper gateway specification. |
400 |
VPN.0518 |
The target flavor %s does not support modification: %s |
Enter a proper gateway specification. |
400 |
VPN.0800 |
Invalid ngfw vpn gateway: %s |
Check whether the gateway ID is correct. |
400 |
VPN.0801 |
Invalid ngfw vpn connection: %s |
Check whether the connection parameters are correct. |
400 |
VPN.0802 |
Invalid migration eip: %s |
Check whether the EIP parameters are correctly set. |
400 |
VPN.0803 |
Invalid migration quota: %s |
Release resources or increase the quota. |