@kapa.ai i set up a new postgres source in airbyte V1, with the same credentials that i used in version 0.68, when setting up the source i get this error: Configuration check failed Message: HikariPool-1 - Connection is not available, request timed out after 10001ms (total=0, active=0, idle=0, waiting=0)

2024-10-17 13:24:30 INFO i.a.w.l.p.s.m.Stage(apply):39 - APPLY Stage: CLAIM — (workloadId = decd338e-5647-4c0b-adf4-da0e75f5a750_4e237dae-0990-4a01-adb5-8ba6dbeda633_0_check) — (dataplaneId = local)
2024-10-17 13:24:42 INFO i.a.c.i.LineGobbler(voidCall):166 - 
2024-10-17 13:24:42 INFO i.a.c.i.LineGobbler(voidCall):166 - ----- START CHECK -----
2024-10-17 13:24:42 INFO i.a.c.i.LineGobbler(voidCall):166 - 
2024-10-17 13:24:53 INFO i.a.c.ConnectorWatcher(processConnectorOutput):114 - Connector exited, processing output
2024-10-17 13:24:53 INFO i.a.c.ConnectorWatcher(getConnectorOutputStream):151 - Output file jobOutput.json found
2024-10-17 13:24:53 INFO i.a.c.ConnectorWatcher(processConnectorOutput):117 - Connector exited with exit code 0
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(create):189 - Reading messages from protocol version 0.2.0
2024-10-17 13:24:53 WARN i.a.m.l.MetricClientFactory(getMetricClient):43 - MetricClient has not been initialized. Must call MetricClientFactory.CreateMetricClient before using MetricClient. Using a dummy client for now. Ignore this if Airbyte is configured to not publish any metrics.
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - INFO main i.a.i.s.p.PostgresSource(main):698 starting source: class io.airbyte.integrations.source.postgres.PostgresSource
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - INFO main i.a.c.i.b.IntegrationCliParser$Companion(parseOptions):144 integration args: {check=null, config=/config/connectionConfiguration.json}
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - INFO main i.a.c.i.b.IntegrationRunner(runInternal):130 Running integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedSource
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - INFO main i.a.c.i.b.IntegrationRunner(runInternal):131 Command: CHECK
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - INFO main i.a.c.i.b.IntegrationRunner(runInternal):132 Integration config: IntegrationConfig{command=CHECK, configPath='/config/connectionConfiguration.json', catalogPath='null', statePath='null'}
2024-10-17 13:24:53 WARN i.a.w.i.VersionedAirbyteStreamFactory(internalLog):305 - WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword groups - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2024-10-17 13:24:53 WARN i.a.w.i.VersionedAirbyteStreamFactory(internalLog):305 - WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2024-10-17 13:24:53 WARN i.a.w.i.VersionedAirbyteStreamFactory(internalLog):305 - WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword group - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2024-10-17 13:24:53 WARN i.a.w.i.VersionedAirbyteStreamFactory(internalLog):305 - WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2024-10-17 13:24:53 WARN i.a.w.i.VersionedAirbyteStreamFactory(internalLog):305 - WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword always_show - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2024-10-17 13:24:53 WARN i.a.w.i.VersionedAirbyteStreamFactory(internalLog):305 - WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword display_type - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - INFO main i.a.c.i.b.s.SshTunnel$Companion(getInstance):423 Starting connection with method: NO_TUNNEL
2024-10-17 13:24:53 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - INFO main i.a.i.s.p.PostgresUtils(isCdc):70 using CDC: false

The error message you're seeing,

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

, typically indicates that Airbyte is unable to establish a connection to your PostgreSQL database. This could be due to a variety of reasons such as incorrect credentials, network issues, or the database server being unresponsive. Here are a few things you can check: 1. Credentials: Ensure that the username, password, and other connection details provided are correct. 2. Network Connectivity: Check if there are any network issues that might be preventing Airbyte from reaching your PostgreSQL server. This could be firewall rules, security groups, or other network configurations. 3. Database Server Status: Ensure that your PostgreSQL server is up and running without any issues. 4. Version Compatibility: You mentioned that you're upgrading from Airbyte version 0.68 to version 1. There might be some compatibility issues with the new version. Make sure that your PostgreSQL version is compatible with the Airbyte version you're using. If you've checked all of the above and you're still facing issues, it would be helpful to provide more detailed logs. The logs you've provided seem to indicate that the connection is timing out, but it doesn't provide much information beyond that. For more detailed help, consider posting this issue on the [Airbyte Github](https://github.com/airbytehq/airbyte/issues) or [Airbyte's discussion forum](https://discuss.airbyte.io/). Be sure to include as much detail as possible, including the exact error message and any relevant logs. Sources: - [Github Issue 33821](https://github.com/airbytehq/airbyte/issues/33821) - [Forum Post 1622](https://discuss.airbyte.io/t/1622) - [Forum Post 1640](https://discuss.airbyte.io/t/1640) - [Github Issue 45456](https://github.com/airbytehq/airbyte/issues/45456) - [Forum Post 1902](https://discuss.airbyte.io/t/1902)

@kapa.ai im running an older version of airbyte concurrently, on this version a source with the same credentials works fine, so credentials and connectivity seems correct

A message from kapa.ai

If the same credentials are working fine on an older version of Airbyte, it's possible that the issue might be related to changes or updates in the newer version of Airbyte or the specific connector you're using. Here are a few additional steps you can take: 1. Check for Updates: Make sure that both your Airbyte instance and the specific connector you're using (in this case, the PostgreSQL connector) are updated to the latest version. Sometimes, bugs or issues are fixed in newer versions. 2. Compare Configurations: Compare the source configuration between the two versions of Airbyte. Ensure that all the settings are identical. 3. Check for Known Issues: Look through the [Airbyte Github issues](https://github.com/airbytehq/airbyte/issues) and [Airbyte's discussion forum](https://discuss.airbyte.io/) to see if anyone else has reported a similar problem. It's possible that this is a known issue and a solution or workaround has already been found. 4. Report the Issue: If you're still unable to resolve the issue, consider reporting it to the Airbyte team. Provide as much detail as possible, including the exact error message, the versions of Airbyte and the connector you're using, and any relevant logs. This will help the team diagnose and fix the issue. Sources: - [Github Issue 33821](https://github.com/airbytehq/airbyte/issues/33821) - [Forum Post 1622](https://discuss.airbyte.io/t/1622) - [Forum Post 1640](https://discuss.airbyte.io/t/1640) - [Github Issue 45456](https://github.com/airbytehq/airbyte/issues/45456) - [Forum Post 1902](https://discuss.airbyte.io/t/1902)

@kapa.ai i just downgraded the postgres version to the same version i have in my older airbyte version, but still get the same error

A message from kapa.ai

If downgrading the PostgreSQL version to match the one in your older Airbyte version didn't resolve the issue, it's possible that the problem lies elsewhere. Here are a few more things you can try: 1. Check Airbyte Version: Ensure that the Airbyte version you're using is compatible with the PostgreSQL version. You might want to consider downgrading Airbyte to the version that's working with your older setup. 2. Check Logs: Look at the logs for more detailed error messages. This might give you more insight into what's going wrong. 3. Check Configuration: Double-check the configuration of your source in Airbyte. Make sure all the settings are correct and match those in your older setup. 4. Report the Issue: If you're still unable to resolve the issue, consider reporting it to the Airbyte team. Provide as much detail as possible, including the exact error message, the versions of Airbyte and the connector you're using, and any relevant logs. This will help the team diagnose and fix the issue. Remember, when reporting the issue, to include as much information as possible to help the Airbyte team diagnose the problem. This includes the exact error message, the versions of Airbyte and the connector you're using, and any relevant logs. Sources: - [Github Issue 33821](https://github.com/airbytehq/airbyte/issues/33821) - [Forum Post 1622](https://discuss.airbyte.io/t/1622) - [Forum Post 1640](https://discuss.airbyte.io/t/1640) - [Github Issue 45456](https://github.com/airbytehq/airbyte/issues/45456) - [Forum Post 1902](https://discuss.airbyte.io/t/1902)