- Is this your first time deploying Airbyte?: Yes
- OS Version / Instance: Windows
- Memory / Disk: 5Gb
- Deployment: Docker
- Airbyte Version: 0.40.18 as received from
git clone https://github.com/airbytehq/airbyte.git
- Source name/version: self hosted (localhost) Psql 14.1
- Destination name/version: Doesn’t applies for this question
- Step: The issue is happening during setting up the connection
- Description: I have setted up a self hosted airbyte on my windows 11 laptop using an ubunt WSL2 as described here Local Deployment | Airbyte Documentation
And I have also a running psql database on my pc with some tables. I wanted to connect my self hosted airbyte (accessed via https://localhost:8000 on my browser) to that psql, but it says it can’t connect. I’ve attached an image of the parameters I am setting. On the left hand of the image is airbyte’s UI and on the right my psql database credentials as seen on pgadmin. Also, if I try to connect ot my psql via command (cmd) it works with those credentials, I just run
psql -h localhost -U postgres and then asks me the password and it’s fine. I am also sure the password I gave airbyte is fine too.
Why can’t I connect? Here’s the image
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.
The Community Assistance Team
Hello Eugenio, it’s been a while without an update from us. Are you still having problems or did you find a solution?