Troubleshoot common issues

Available in Classic and VPC

You might run into the following problems when using VPC. Find out causes and possible solutions.

VPC creation error

No VPCs are created.
I can't add VPC from sub accounts.

Cause

You have exceeded the number of VPCs you can create.

Solution

• Make sure that you have not created more than 3 VPCs.
  • The maximum number of VPCs can be created in a region is 3.
  • A main account and a sub account share the same resources. It is impossible to create 3 VPCs each on the main and sub accounts. So please check the number of VPCs created per region.
• If you need to separate your VPCs in detail, use Subnet.

VPC deletion error

VPCs are not deleted.
When deleting a VPC, I received the message "It cannot be deleted because not all Endpoints were returned."

Cause

You can't delete a VPC if resources exist below the VPC.

Solution

You must return or delete all resources related to the VPC you are deleting.

• Delete all resources in the Server, Network Interface, Cloud functions, Load Balancer, Auto Scaling, and NAT Gateway related to the VPC you want to delete.
• Delete the Route Table related to the VPC.
• Delete the Subnet related to the VPC.
• The Network Interface assigned to the server eth0 cannot be returned and deleted. You must first return the server to delete the Network Interface assigned to server eth0.

Unable to change VPC and Subnet name

I can’t change the VPC name.
I can't change the Subnet name.

Cause

You cannot change VPC and Subnet names you have already created.

Solution

If you need to change the VPC name, delete and recreate the VPC.
If you need to change the Subnet name, delete and recreate the Subnet.

Error message: "Subnet CIDR cannot be duplicated within a VPC"

When creating Subnet, I received the message "Subnet CIDRs cannot be duplicated within a VPC." and the Subnet is not created.

Cause

You cannot create duplicate or overlapping scopes of different Subnets within a VPC.

Solution

Make sure to set it so there are no duplicate CIDRs.
The following are examples of specifying Subnet range within a VPC:

• VPC 1: 10.0.0.0/16
  • Subnet 1: 10.0.1.0/24
  • Subnet 2: 10.0.2.0/24
  • Subnet 3: 10.0.3.0/24
• VPC 2: 10.1.0.0/16
  • Subnet 1: 10.1.0.0/24
  • Subnet 2: 10.1.2.0/24
  • Subnet 3: 10.1.3.0/24

VPC Peering error

An error occurs during the VPC Peering setup.

Cause

VPC Peering rules are not configured in the routing table.
ACL settings are not applied correctly.

Solution

Add the VPC Peering rules to the VPC's Route Table. NACL is Stateless and operates on a complete acceptance basis. Therefore, consider both inbound and outbound rules to ensure that request response packets are not blocked.