I upgraded my redshift connector (airbyte cloud) to 4.0.0 and it immediately broke. error: Configuration check failed Could not connect with provided configuration. Error: Database connection check failed: HikariPool-1 - Connection is not available, request timed out after 120001ms (total=0, active=0, idle=0, waiting=0) State code: 99999; Error code: 0

The knowledge sources don't contain specific information about this exact error with version 4.0.0 of the Redshift destination connector, but based on what's available, here's what to check: Connection Timeout After Upgrading to 4.0.0 The

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

error means Airbyte cannot reach your Redshift cluster at all. This is a network/connectivity issue, not a bug introduced by 4.0.0 itself. Things to verify: 1. Allow Airbyte Cloud IP addresses — Ensure the Airbyte Cloud IP addresses are whitelisted in your Redshift cluster's security group and network policy. [Redshift Troubleshooting] 2. Port 5439 — Confirm that TCP port 5439 is explicitly open in your security group rules (not just "allow all traffic" — that has been known to not work in some cases). [Forum Post] 3. Private VPC — If your Redshift cluster is in a private VPC, you may need to configure an SSH Bastion Host or allow cross-VPC connections. [Redshift Troubleshooting] 4. Redshift Serverless hostname — If you're using Redshift Serverless, double-check that the endpoint hostname in your configuration is correct (the Serverless endpoint format differs from provisioned clusters). [Forum Post] Regarding the 4.0.0 upgrade itself: Version 4.0.0 is a full rewrite using the Direct-Load paradigm (removal of raw tables). If you interact with raw tables (

_airbyte_raw_*

) in downstream models, those will break. However, the connection timeout you're seeing is a pre-sync connectivity failure, not a data model issue. [Migration Guide] If connectivity was working before the upgrade and nothing else changed, I'd recommend: • Re-checking your security group rules • Temporarily rolling back to 3.5.4 to confirm the issue is upgrade-related • Reaching out to Airbyte support with your connector logs for further investigation 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

uhhhh well everything was fine and working, and then the moment I upgraded, the next sync failed. I did not make any changes to my AWS config

I'm sorry, but the knowledge sources do not contain enough information to give you a confident answer about this specific issue with version 4.0.0 on Airbyte Cloud. What I can tell you: • On Airbyte Cloud, connector rollbacks require contacting support — there is no self-serve UI to downgrade a connector version. [Support QA] • Version 4.0.0 is a full rewrite with significant architectural changes (Direct-Load, removal of raw tables, new JDBC driver version 2.2.7, AWS SDK v2). It's plausible that the new version has a connectivity regression. [Migration Guide] Given that: 1. Your endpoint is publicly accessible 2. Nothing changed on your AWS side 3. The failure happened immediately after the upgrade This strongly suggests a bug or incompatibility in 4.0.0 itself. I'd recommend reaching out to Airbyte Cloud support directly and asking them to: • Roll back your Redshift destination connector to 3.5.4 (the last stable version before 4.0.0) • Investigate whether 4.0.0 has a known regression You can contact Airbyte support at airbyte.com/contact-support or via the in-app chat on Airbyte Cloud. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.