0

So I have been using the cloud_sql_proxy for a while now for a local development environment and never had any issues (over a year). I tried to connect today, and it authenticates fine. Yet, connecting to the local port gives a connectex error:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

  • I authenticate with a service account at a location specified in my environmental variables. I connect with the command cloud_sql_proxy -instances="XXXXX.XXXXX.XXXXX"=tcp:5432
  • Windows 10
  • The Cloud SQL instance works fine and communicates (over a similar proxy) with the production server.
  • I tried connecting with Django, get connectex error.
  • I tried to ping the local network, get connectex error.
  • I tried adding a firewall rule that allows all outbound traffic to port 3307

Any ideas what could've broken my proxy?

Niels Uitterdijk
  • 713
  • 9
  • 27
  • Why the port 3307?? In addition, can you try to download the latest version of cloud sql proxy? Finally, is your database still have a public IP? – guillaume blaquiere Aug 19 '21 at 07:32
  • The proxy itself uses port 3307 to connect to the server side proxy https://cloud.google.com/sql/docs/postgres/sql-proxy?hl=en. Have the latest version. It worked on my home network so I believe it's a firewall in my work's router. – Niels Uitterdijk Aug 19 '21 at 07:41

1 Answers1

1

If the connection to the Cloud SQL proxy times out, it means the connection to the proxy itself didn't work. That means either the proxy is not listening, or that something it blocking the connection.

I would suggest looking in the proxy logs to see if it reports any start up errors.

kurtisvg
  • 3,412
  • 1
  • 8
  • 24