This page shows you how to resolve common network configuration issues in AlloyDB for PostgreSQL.
NETWORK_NOT_PEERED
This error occurs when you haven't created a Virtual Private Cloud (VPC) peering with Service Networking.
To resolve this error, set up peering between Service Networking and the specified Virtual Private Cloud. For more information, see Enable private services access.
NETWORK_PEERING_DELETED
This error occurs when the Virtual Private Cloud peering that was present earlier is now deleted.
To resolve this issue, set up peering between Service Networking and the specified Virtual Private Cloud. For more information, see Increase private services access address space.
NETWORK_NOT_FOUND
This error occurs when the network with the name that was specified during cluster creation isn't found.
To resolve this issue, verify that the specified Virtual Private Cloud network is correct.
RANGES_EXHAUSTED
This error occurs when Virtual Private Cloud peering doesn't have enough IP range space available in the IP reservation that is assigned to the Virtual Private Cloud peering.
To resolve this issue, increase the private services access address space. For more information, see Increase private services access address space.
To provide sufficient address space for AlloyDB, we recommend that you use a prefix length of 16 or less, with a minimum size of /24.
SERVICE_NETWORKING_NOT_ENABLED
This error occurs when the Service Networking API isn't enabled in your Google Cloud project.
To resolve this issue, enable the required APIs.
NETWORK_NOT_IN_CONSUMERS_PROJECT
This error occurs when the network specified during cluster creation is not in your Google Cloud project.
To resolve this issue, verify that the specified Virtual Private Cloud network is correct.
NETWORK_NOT_IN_CONSUMERS_HOST_PROJECT
This error occurs when the Shared VPC network specified during cluster creation isn't in your host project.
To resolve this issue, verify that the specified Virtual Private Cloud network is correct. For more information, see Shared VPC.
HOST_PROJECT_NOT_FOUND
This error occurs when the Shared VPC host project is not found.
To resolve this issue, verify that the specified Virtual Private Cloud network is correct. For more information, see Shared VPC.
CONSUMER_PROJECT_NOT_SERVICE_PROJECT
This error occurs when the specified Shared VPC isn't attached to the AlloyDB project.
To resolve this issue, verify that the specified Virtual Private Cloud network is correct. For more information, see Shared VPC.