service · inferred from evidence
Cloud SQL
A managed database service mentioned as the target of proxy connections.
- Cloud SQL Proxy v2: "failed to connect to instance: Dial error: failed to dial ... i/o timeout"
After upgrading the Cloud SQL Auth Proxy from v1 to v2 (2.2.0) as a GKE sidecar, the proxy logged many "failed to connect to instance: Dial error: failed to dial (connection name = ...): dial tcp ...:3307: i/o timeout" errors across multipl
- Cloud SQL Proxy: "couldn't connect ... dial tcp ...:3307: getsockopt: connection timed out"
Connecting to a Cloud SQL MySQL instance through the proxy from a GCE VM hung forever, and the proxy log showed: couldn't connect to INSTANCE: dial tcp IP:3307: getsockopt: connection timed out. The VM's service account had the Cloud SQL Cl
- Cloud SQL Proxy: "Error during createEphemeral ... Error 403: The client is not authorized to make this...
The Cloud SQL proxy failed at startup with: couldn't connect to "PROJECT:REGION:INSTANCE": ensure that the account has access ... Error during createEphemeral for PROJECT:REGION:INSTANCE: googleapi: Error 403: The client is not authorized t