@kapa.ai when setting up AWS Redshift destination using managed Airbyte version, I got an error "failed to save RedShift due to the following error: could not connect with provided ssh configuration. Error: getSQLState(...) must not be null". How do I fix this

The knowledge sources show this exact error (

"Could not connect with provided SSH configuration. Error: getSQLState(...) must not be null"

) as an open GitHub issue for the Redshift destination connector (version 3.5.3) when configuring a new destination, and there is no documented workaround or fix yet. [Redshift SSH issue] Because of that, I can’t reliably tell you how to fix it from the available information. Specifically: • The error appears even though the user selected “No tunnel” in the UI, but the logs show

SshWrappedDestination

being used, indicating a bug in how SSH configuration is handled. [Redshift SSH issue] • There is a comment from another user confirming the same issue prevents them from setting up Redshift as a destination, and no resolution is documented yet. [Redshift SSH issue] Given the limits of the sources, the only concrete guidance I can offer is: 1. Check connector version The issue is reported for

destination-redshift

3.5.3. If your managed Airbyte instance allows it, try using a different Redshift destination version (older or newer) and re‑test. The sources don’t confirm that this resolves it, but version changes have fixed Redshift issues in the past (e.g., another bug was fixed by upgrading to 0.3.31). [Postgres→Redshift error] 2. Temporarily avoid SSH tunneling If you currently have any SSH tunnel configuration set, try configuring Redshift without SSH (direct network access) and see if the destination can be saved. However, the issue report suggests the bug may occur even when “No tunnel” is selected, so this may not help. [Redshift SSH issue] 3. Contact Airbyte Cloud / managed support Since you’re on a managed version, the most practical next step is to open a support ticket or reference this GitHub issue ID (

airbytehq/airbyte#60926

) so the team can confirm whether: ◦ a fix has been deployed to your managed environment, or ◦ a specific connector version or configuration is recommended as a workaround. I’m sorry I can’t provide a concrete configuration change that is known to fix this; the current knowledge sources don’t include a confirmed resolution for this specific SSH-related Redshift destination error. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.