If you’re having trouble connecting to your external PostgreSQL database from Airbyte, but you’re able to connect normally from outside, it could be due to a few reasons: 1. Network Access: Ensure that your Airbyte instance has network access to your PostgreSQL database. If they’re not on the same network, you might need to adjust your firewall rules or VPC settings to allow Airbyte to connect to your database. 2. Database Credentials: Double-check the database credentials you’ve entered in the .env file. Make sure the DATABASE_USER, DATABASE_PASSWORD, DATABASE_HOST, DATABASE_PORT, and DATABASE_DB are correct. 3. Database URL: Ensure that the DATABASE_URL in the .env file is correctly formatted. It should look something like this: postgresql://<user>:<password>@<host>:<port>/<database> 4. Database Configuration: Your PostgreSQL database should be configured to accept connections from your Airbyte instance. This might involve editing the pg_hba.conf file to add a rule for your Airbyte instance. 5. Airbyte Server Logs: Check the Airbyte server logs for any error messages that might give you more information about the issue. You can view the logs by running docker-compose logs -f airbyte-server in the Airbyte directory. If you’re still having trouble after checking these things, you might want to try temporarily installing psql in one of the Airbyte containers and trying to connect to the database. This can help you determine whether the issue is with Airbyte or with the database connection itself. Sources: - Forum Post: Failed to connect to external postgres DB > Answers Part 6 - Deploy Airbyte on Azure (Cloud Shell) - Deploy Airbyte on Oracle Cloud - Deploy Airbyte on GCP (Compute Engine)