IssueTracker

Hello,

Thank you for reaching out.

I'll be happy to help with your issue, but I need some extra information to move forward.

1. Please provide the steps you've followed to get the issue, including the workarounds you've tried.
2. If you are following the documentation, please provide the link.
3. This is full error output?
4. I can see that you are using a custom network - main. Could you confirm that Serverless VPC access does not overlap any CIDRs in your main VPC?

I am looking forward to your answer.

Kind Regards

Hi,

1. It's as simple as:

   • Cloud Console => VPC Network => Serverless VPC Access
   • Create connector
     • Pick any region (e.g. europe-west4)
     • Name => make same as region (e.g. europe-west4)
     • Subnet => Custom IP range
       • IP range => whatever /28 private net you like (e.g. 10.8.0.0/28, just like UI suggests)
     • Show scaling settings
       • Minimum instances => 2
       • Maximum instances => 3
       • Instance type => keep at e2-micro
   • Click on "Create"
   • Wait
   • Observe an error reported by console:

     Unknown error. Original error message: An internal error occurred: Failed to create a VPC Access connector. Please delete the connector manually.

2. https://cloud.google.com/vpc/docs/configure-serverless-vpc-access#create-connector

3. Yes, this is a full error output.

4. I don't have any subnetworks in that VPC - so, yes, Serverless VPC CIDR does not overlap with any VPC's subnet CIDRs.

Thank you.

Kind regards, Anton

Hello,

Thank you for additional information.

I've tried to replicate this scenario but in my test environment, VPC connector was created successfully.

I've created a new custom VPC network with ip: 10.0.0.0/28. Then I've created a connector in that network with a custom IP Range: 10.8.0.0/28.

Please check my screens.

Is there any specific configuration in your VPC? Is it shared? It's auto or custom? Do you have proper permissions? Before you could create Serverless VPC access or you have issues since beginning? You don't have any billing issues?

I am looking forward to your answer.

Kind Regards

Hello,

Thank you for your response. Here are my answers to your inquiries:

Is there any specific configuration in your VPC? Is it shared? It's auto or custom?

No, nothing specific. It's a freshly created VPC, not shared, not automatic, no subnets.

Do you have proper permissions?

Yes, I have owner role on the project.

Before you could create Serverless VPC access or you have issues since beginning?

No, I could not create any Serverless VPC Connectors since the beginning of this GCP project.

You don't have any billing issues?

Not that I am aware of. However, I did not yet pay any bills - this is a freshly started project, just about a week ago. My trial period expired couple of years ago but the credit card is attached (I have a gsuite subscription paid monthly). Total cloud costs are less that EUR 5 so far - so, I think I am good.

Kind regards,
Anton

Hello,

Thank you for additional information.

I have created a new project with the new VPC main to replicate this issue. I've created many Serverless VPC connectors and couldn't replicate your issue (using default network, and new main network). Please check the attachment.

Could you confirm if you didn't disable Compute Engine Default Service Account? Also, could you check if you didn't hit any Compute Engine Quota? You can check it following this documentation.

I am looking forward to your answer.

Kind Regards

Hello

I'm closing this case as I haven't heard from you for a while.

Feel free to create a new one if you want to move forward.

Kind regards