I am trying to set up a new Postgres destination b...
# replication-ask-ai
j
I am trying to set up a new Postgres destination but getting error "Configuration check failed Could not connect with provided configuration. Error: HikariPool-1 - Connection is not available, request timed out after 30000ms (total=0, active=0, idle=0, waiting=0)". What should i do?
k
The
HikariPool-1 - Connection is not available, request timed out
error is a connectivity issue — Airbyte is unable to reach your Postgres destination. Here are the main things to check: 1. Verify Network Accessibility / Firewall Rules The most common cause is that the Airbyte instance cannot reach the database server over the network. Check that: • The IP address of your Airbyte instance is whitelisted on the Postgres server's firewall or security group. • The correct port (default
5432
) is open and accessible from the Airbyte host. [connection timeout forum] 2. Check Host and Port Confirm that the hostname and port you entered are correct and that the Postgres server is actually accepting TCP/IP connections. [failed to connect forum] 3. Verify Database Credentials Ensure the username, password, host, port, and database name are all correct. [troubleshooting guide] 4. Check Postgres Configuration Make sure your Postgres instance is configured to accept remote connections. This may involve: • Adjusting
pg_hba.conf
to allow connections from the Airbyte host. • Ensuring
listen_addresses
in
postgresql.conf
is set correctly (e.g.,
*
or the specific IP). [troubleshooting guide] 5. SSH Tunnel (if applicable) If your database is behind a VPN or firewall, consider using an SSH tunnel. The Postgres destination connector supports SSH Key Authentication or Password Authentication tunneling. [Postgres destination docs] 6. Connection Timeout Setting The Postgres destination connector supports a
connectTimeout
parameter (defaults to 60 seconds). You can adjust this via JDBC URL Params if needed, but note that the timeout error itself is typically a symptom of a network/firewall issue rather than the timeout being too short. [Postgres destination docs] 7. Test Connectivity Independently Try connecting to your Postgres instance from the Airbyte host using a tool like
psql
to confirm basic connectivity before troubleshooting within Airbyte. [MSSQL timeout forum] In most reported cases, this error is resolved by correctly whitelisting the Airbyte IP and ensuring the database port is open. [connection timeout forum] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.