Google cloud sql connection, host database_url

Hi!

I would like to use google cloud sql separate instance so we can have backups and not have any problems if the instance dies or something.

But I’m having trouble with the settings I need to put in the .env file

Am able to get Airbyte deployed on google cloud compute instance using the default settings - loading a local postgres on that instance.

We would be willing to get some help at an hourly rate if anyone is interested!? I’m far from an expert on this.

I have tried editing the .env file on the live instance

I’ve also tried to deploy from my own github with the .env file already edited.

that does work. it loads and logs in the basic http auth using the values in the .env but it just sticks on server loading in the GUI

I think the variables I’m putting in the .env for cloud sql are wrong.

specifically my guess is the jdbc:postgresql:/// line but again I am new to this one.

I’ve tried most of the combos I can find on stackoverflow

  • Is this your first time deploying Airbyte?: yes
  • OS Version / Instance: debian i think? the gcp deploy instructions default
  • Memory / Disk: gcp standard n
  • Deployment: docker
  • Airbyte Version: current

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

Hello Dillon Doyle, it’s been a while without an update from us. Are you still having problems or did you find a solution?

I have not found a solution! I did schedule a call with airbyte to see if can pay for support. Any freelance people too feel free to reach out dillon (at) 4degre.es