Dear Google Cloud Community and Support Engineers,
I am experiencing a critical and persistent failure when trying to create a Serverless VPC Access Connector (cloud-run-connector) in the europe-central2 region. The operation consistently fails with an “Internal Error” (code: 13), which is blocking the deployment of Cloud Functions. I have performed exhaustive troubleshooting and eliminated all standard causes. I believe this points to a platform-level internal failure.
Failure Details:
Project ID:[Available upon request]
Region: europe-central2
Last Failed Operation ID (Please check internal logs): operations/76112da8-1a2b-4ea3-b35f-62be2336e340
Exhaustive Troubleshooting Summary (Actions Taken):
1. IAM Permissions Eliminated: All Service Accounts have the required Editor/Admin roles.
2. Quota Eliminated: Compute Engine Quotas are sufficient (0% usage).
3. Network Isolation: The connector fails in both the default network AND a newly created, clean Custom VPC (`vpc-for-connector-final`).
4. Firewall Guaranteed: High-priority (1000), ALLOW ALL Egress and ALLOW ALL Internal Ingress rules were created to eliminate all possible traffic blocks (e.g., the standard SMTP Port 25 restriction). Conclusion: This is confirmed to be an internal platform issue preventing the provisioning of the connector’s underlying VMs. Has anyone encountered this persistent `code: 13` internal error in `europe-central2`?
For Google Engineers: If you require the Project ID to look up the internal failure logs, please advise how I can share this sensitive information securely (e.g., via a Private Message).