@kapa.ai, i am creating connection between postgres source and destination, but i am getting error on schema discovery Error:

Internal message: io.airbyte.commons.exceptions.ConnectionErrorException: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 10001ms (total=0, active=0, idle=0, waiting=0)
Failure type: system_error

PostgreSQL Connection Timeout During Schema Discovery The error

HikariPool-1 - Connection is not available, request timed out after 10001ms

indicates that Airbyte cannot establish a connection to your PostgreSQL database within the timeout window. Here are the most common causes and fixes: 1. Network / Firewall Issues • Verify that the Airbyte instance can reach your PostgreSQL host and port (default: 5432) over the network. • Check firewalls, security groups, or VPN rules that might be blocking the connection. [Connection Timeout VPN] 2. Verify Connection Credentials Double-check that the host, port, database name, username, and password are all correct. A wrong hostname or port will cause the connection to hang until timeout. [Postgres Connection Error] 3. PostgreSQL Server Configuration Ensure your PostgreSQL server is configured to accept TCP/IP connections from the Airbyte host: • Check

postgresql.conf

→

listen_addresses

is set correctly. • Check

pg_hba.conf

to allow connections from the Airbyte IP. [DB Config Tips] 4. Schema Scope (if connection succeeds but discovery fails) If the connection test passes but schema discovery times out, try limiting the source to a specific schema (e.g.,

public

) instead of discovering all schemas. A large number of schemas/tables can cause discovery to time out. [Schema Discovery Issue] 5. Schema Discovery Timeout (Enterprise/Self-hosted) If you have hundreds of tables, you can increase Airbyte's timeout limit in `values.yaml`:

server:
  httpIdleTimeout: 20m
  extraEnv:
    - name: READ_TIMEOUT
      value: 30m

[Scaling Airbyte] 6. Known Connector Fix (Transient Error Classification) The

system_error

classification for connection timeouts is a known issue. A fix has been submitted to classify

Connect timed out

and similar errors as transient errors (enabling automatic retries) in source-postgres version

3.8.2

. If you're on an older connector version, consider upgrading. [Postgres Transient Fix] Quick checklist: • Can you

telnet <postgres-host> 5432

from the Airbyte host? • Are credentials correct? • Is the DB accepting remote TCP connections? • Are you connecting through a VPN or PgBouncer? 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.