- *Is this your first time deploying Airbyte*: Yes...
# troubleshooting
j
Is this your first time deploying Airbyte: Yes • OS Version / Instance: Windows • Memory / Disk: 32Gb / 457GB • Deployment: Docker • Airbyte Version: 0.35.65-alpha • Source name/version: Postgres (version unknown) • Destination name/version: N/A • Step: Setting new source • Description: I am trying to set up a new Source in Airbyte that connects to a Google Cloud SQL Postgres database and am getting variations of this error when I try to save the connection
Could not connect with provided configuration. Error: Cannot create PoolableConnectionFactory
On the
<http://localhost:8000/workspaces/{{workspace_id}}/source/new-source>
page I am getting these errors for these Host & Port combinations 1. Host =
localhost
, Port = `5432`:
Could not connect with provided configuration. Error: Cannot create PoolableConnectionFactory (Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.)
2. Host =
127.0.0.1
, Port = `5432`:
Could not connect with provided configuration. Error: Cannot create PoolableConnectionFactory (Connection to 127.0.0.1:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.)
3. Host = public ip address from
<https://console.cloud.google.com/sql/instances/{{instance_name}}/overview?project={{project_name}}>
, Port = `5432`:
Could not connect with provided configuration. Error: Cannot create PoolableConnectionFactory (The connection attempt failed.)
the attached file are the logs from #2 above
I still get the error even when I run these commands from a terminal •
cloud_sql_proxy -instances={{project_name}}:us-central1:{{instance_name}}=tcp:5432
docker run -d -p 127.0.0.1:5432:5432 <http://gcr.io/cloudsql-docker/gce-proxy:1.30.0|gcr.io/cloudsql-docker/gce-proxy:1.30.0> /cloud_sql_proxy -instances={{project_name}}:us-central1:{{instance_name}}=tcp:0.0.0.0:5432
I could try running cloud_sql_proxy from the airbyte docker container but I don't know which one to run the command against, as I see multiple for airbyte and ^ exits out after returning me a 64 character alphanumeric string
these are the other settings in case those last 3 selections are relevant to the error
Ok this may be an issue with my Google Cloud credentials. When I remove the
-d
portion of the command I now see this error from cloud_sql_proxy
2022/04/12 23:39:07 google: could not find default credentials. See <https://developers.google.com/accounts/docs/application-default-credentials> for more information.
I'm working through resolving that