organization · inferred from evidence
GoogleCloudPlatform
The GitHub organization maintaining the cloud-sql-proxy repository.
- Cloud SQL Proxy v2: "failed to connect to instance: Dial error: failed to dial ... i/o timeout"
The reporter resolved this by switching the Cloud SQL instance to a private IP and running the proxy with the --private-ip flag (they also switched GKE to Cloud DNS at the same time, so they could not isolate which change fixed it). The wor
- Cloud SQL Proxy: "couldn't connect ... dial tcp ...:3307: getsockopt: connection timed out"
The proxy intentionally dials the Cloud SQL instance on port 3307 (local clients still use 3306; 3307 isolates proxy traffic on the instance side), so your firewall/VPC must allow egress from the proxy host to the instance IP on port 3307.
- Cloud SQL Proxy: "Error during createEphemeral ... Error 403: The client is not authorized to make this...
This is a known IAM propagation quirk, not a proxy bug: re-grant the role to force it to take effect. Remove the Cloud SQL Client role from the failing service account in IAM & Admin > IAM (uncheck it and Save), verify the account disappear