cloud-sql-proxy: TLS handshake failing on Windows with 2.13.0

Bug Description

After upgrading from 2.12.0 to 2.13.0, we are getting TLS handshake failed: EOF error with the Windows executable (x64).

Example code (or command)

cloud-sql-proxy-2.13.0 --auto-iam-authn --private-ip  --impersonate-service-account "redacted@redacted.iam.gserviceaccount.com" "redacted:europe-west1:redacted?port=15434" --run-connection-test --debug-logs

Stacktrace

TLS handshake failed: EOF
Connection info refresh operation started
Connection test failed
 proxy server error: Dial error: handshake failed (connection name = "redacted"): EOF
The proxy has encountered a terminal error: Dial error: handshake failed (connection name = "redacted"): EOF


### Steps to reproduce?

1. Use a similar command with 2.12.0 (or older) - works well.
2. Use 2.13.0 - crashes on the error.


### Environment

1. OS type and version: Windows 10 Enterprise
2. Cloud SQL Proxy version (`./cloud-sql-proxy --version`): cloud-sql-proxy version 2.13.0+windows.amd64
3. Proxy invocation command (for example, `./cloud-sql-proxy --port 5432 INSTANCE_CONNECTION_NAME`): cloud-sql-proxy-2.13.0 --auto-iam-authn --private-ip  --impersonate-service-account "redacted@redacted.iam.gserviceaccount.com" "redacted:europe-west1:redacted?port=15434" --run-connection-test --debug-logs


### Additional Details

_No response_

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 20 (7 by maintainers)

Most upvoted comments

Good catch, I can confirm that set GODEBUG=tlskyber=0 fixed the usage on Windows.

@augi I tested and had no issue with the v2.13.0 x64 Windows Proxy build…

Ran the following command:

cloud-sql-proxy.exe my-project:us-central1:my-instance?port=5432 --run-connection-test

And got the following expected output:

2024/09/08 09:58:56 Authorizing with Application Default Credentials
2024/09/08 09:58:57 [my-project:us-central1:my-instance] Listening on 127.0.0.1:5432
2024/09/08 09:58:57 The proxy has started successfully and is ready for new connections!
2024/09/08 09:58:57 Connection test started
2024/09/08 09:58:57 Connection test passed

This makes me think something has maybe changed in your environment that is unexpectedly causing the new proxy version to fail?

All our latest release changed was bumping to Go 1.23, so I will double-check that nothing with Go’s TLS library on Windows changed in the new Go version.

No. Without this parameter, the proxy starts, but fails on the same errors when trying to establish the first connection.