https://linen.dev logo
Join Slack
Powered by
Hi everyone :wave: - I'm just joining in here afte...
# announcements
z
Hi everyone 👋 - I'm just joining in here after using singer.io. I was able to successfuly set up a locally hosted postgres target using singer, but am running into an error on Airbyte 
Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
I was wondering if anyone knew why this may be? I'm new to using Docker (and development in general) so my knowledge of what it's doing is limited and I thought my problem may be related to it.
j
Hi Zachary
Let me make sure I’m understanding correctly: you’re running a local postgres instance outside of Airbyte
And then you’re trying to spin up Airbyte and it’s running into this problem?
Or are you able to launch Airbyte and then you’re receiving this error when trying to sync data?
z
Hey @Jared Rhizor (Airbyte) - Thanks for your help. I'm able to launch airbyte and then receiving this error when trying to connect to the destination
j
How are you running hte local hosted postgres target?
Is it launched from pg_ctl, docker, minikube?
z
I have the Postgres app installed and running
Does that answer your question?
j
how did you install the postgres app?
Just to check, are you able to access your local postgres instance outside of Airbyte?
z
Yes, and I'm able to use it as a target with singer
j
Are you running Airbyte with docker-compose?
z
image.png
I'm a huge noob so don't know how to understand your question but I am running Docker Desktop
j
No worries. This means it’s running on docker-compose using docker desktop
👍 1
If you try 127.0.0.1 instead of localhost, does it make a difference?
z
Let me give it a shot...hold on
It requires me to enter a pw which I don't believe exists for the db. I just entered 'password' and then get the same connection error 
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.
Hold on...I may have tried to add it as a source rather than a destination. I'm retrying as a destination.
Ok, I can confirm I'm getting the same error as above after using 127.0.0.1 instead of localhost
j
can you set the password for the db?
I’m not sure we support empty passwords
z
As a destination, pw was not required
j
Actually we allow empty passwords for destinations but not sources. That’s inconsistent, I’ll make a ticket to make sure we fix it.
z
Yeah, let me try adding a pw
j
If you prefer, we could do a screenshare over Zoom.
z
Hi Jared - I added a pw and am still getting the same error which doesn't seem to be related to authentication
If you're available, zoom would be great
j
I’ll send you a link directly in a minute
👍 1
tu
For posterity: turns out that this was a case of needing 
host.docker.internal
to access a local Postgres instance. I’m going to add this to the Postgres source and destination docs.
✅ 3
h
Hi @Jared Rhizor (Airbyte) - can you please point me to updated docs for postgres source?
j
The overall up to date postgres docs are at https://docs.airbyte.io/integrations/sources/postgres but it felt more appropriate to put the connection issue in the FAQ since it applies to all DBs, not just postgres
h
Thank you Jared!
👍 1
2 Views
Open in Slack
PreviousNext
Powered by