Open ejstembler opened 1 year ago
I was able to get it to work after using the local machine's I.P. address. Both in cloud-sql-proxy
via the --address
flag, and by using the I.P. has the host in the web ui. Thanks to Sean Zicari on the Slack channel for that suggestion!
In any case, most people will not hard-code their machine's I.P. when using cloud-sql-proxy
. The default is to use localhost
. Perhaps this issue should remain open to better support the defaults which would be localhost
, or 0.0.0.0
, or 127.0.0.1
?
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.
Environment
Current Behavior
I’m running Airbyte locally on macOS (13.2.1 (22D68)) on
localhost:8000
. In the web UI I’m attempting to create a Postgres connection. I have Google Cloud SQL proxy running locally onlocalhost:5432
. However, testing the connection fails:I’ve tried specifying
127.0.0.1
and0.0.0.0
instead of localhost, I’ve also tried running Google Cloud SQL proxy on a different port than5432
. Still doesn’t work.Incidentally, I can successfully connect to Google Cloud SQL Proxy via other means: DBVisualizer, JetBrains DataGrip, Ruby scripts, Python Script, etc…
Expected Behavior
Expected successful connection to local Google Cloud SQL Proxy.
Logs
Steps to Reproduce
cloud-sql-proxy
local. Verify connection is working.From Local Deployment:
References